<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
David poses an excellent question!<br>
<br>
Back in the days of the World English Bible in GBF, the first draft
of which was simply a massive global search-and-replace operation on
the American Standard Version of 1901, I substituted
"you<WTP>" for "ye" since I was loathe to lose the plurality
information. When displayed, I optionally marked the word in some
way. Eventually, I abandoned GBF in favor of USFM as the master
format, and with that change, the <WTP> markers went away,
with no substitution, due to absence of a standard marker for that
AND due to absence of an acceptable extension paradigm at that time.
By then, I hoped that contextual clues had been written in enough
for people to tell the difference. Granted, in some places, like
Matthew 16:19, you might have to look at the Greek or another
language to figure it out. Although it is too late for the bulk of
the WEB NT and OT, unless someone wants to go back and restore that
markup, the issue is back in the form of the <a
href="http://ebible.org/eng-lxx2012/">LXX2012</a> (the same kind
of update of the Brenton LXX) and the conversion of the Revised
Version Apocrypha to the <a href="http://ebible.org/web/">World
English Bible Apocrypha</a>, both of which are at the initial
automated word update stage. Currently, my substitution for "ye" is
"you^". That is using an explicit in-text symbol instead of markup,
which I think could be done better another way.<br>
<br>
USFM now has an extension paradigm that can work, with markers that
start with "\z". The trouble with using those is the same as the
trouble with using "x-" attributes or markers in OSIS: nobody else
knows what to do with them. However, within a single project, i. e.
Sword, it should not be a problem as long as we document it. I'm
thinking that I will translate "ye" as "\zplural you\zplural*" in my
local USFM, then use that to generate "<w
type="x-plural">you</w>" in OSIS for Sword import. For my
exported USFM, I could either strip out the extended markup or leave
it in. In this case, I'm not picky about the marker used, or even if
one is used, so there is no need for an "x-marker" attribute.
However, in cases where you are trying be consistent with the style
of a printed edition, or where language considerations make a
particular marker preferable, I think that supporting such an
attribute might be useful. That is a question best referred to the
translators and copyright owners.<br>
<br>
On 05/02/2012 01:05 AM, David Haslam wrote:
<blockquote cite="mid:1335956722001-4602900.post@n4.nabble.com"
type="cite">
<pre wrap="">There are several modern English translations that use 'you' for both
singular and plural second person pronouns.
The printed edition of the NASB springs to mind. The plural forms are all
marked with an asterisk.
Curiously enough, the word 'plural' is nowhere to be found in the OSIS
reference manual.
Perhaps this would imply that should anyone wish to make a module in which
the plural forms can be identified, then we'd need to use an attribute value
extension - one prefixed with "x-".
For example, the original OSIS XML file for the WEB translation (this was
not used for making the WEB module) did include such a method, i.e. by the
following markup.
you<w type="x-plural" />
Singular forms of 'you' were without the markup.
btw. The WEB translation is not one with detailed morphology markup other
than this. (i.e. No Strongs, etc)
Perhaps it would be a useful concept to take up further in the SWORD engine,
such that the plural forms could be toggled by GlobalOptionFilter=OSISMorph
?
As each such translation might require a different visible marker to
identify the plural form, then the syntax would need to include a marker
attribute.
</pre>
</blockquote>
<br>
</body>
</html>