So... it sounds like I could simply convert USFM to OSIS with the
obvious conversions (like \p ... -> ...) plus
\qt ->
\qt* ->
\wj ->
\wj* ->
<< -> (unless at the beginning of a paragraph
with an unended quotation in progress, then
>> ->
< -> (unless at the beginning of a paragraph
with an
That's good. Searching through the WG list, the closest I could find was
an email that seemed to imply to me that we had dumped special markup
for OT passages entirely--in favor of a with an osisRef pointing to
somewhere in the OT.
I'm glad that didn't make it to any release. :)
Now I remembe
Thanks for the memory jogger, Chris. I think the debate in the WG was
the desire to use when alluding to OT passages, which I adamantly
opposed, as it would seem to imply a linguistic structure equivalent to:
And in Psalm 119 it says, "."
When in fact, the NT authors often only allude to
On Apr 30, 2007, at 6:57 PM, Chris Little wrote:
>
>
> Kahunapule Michael Johnson wrote:
>> The same
>> technique would be useful for translating the USFM \qt ...\qt* markup
>> (which is marked verse-by-verse to indicate OT quotes in the NT)
>> to > marker="" who="OT" sID="somethingunique">...>
Kahunapule Michael Johnson wrote:
> The same
> technique would be useful for translating the USFM \qt ...\qt* markup
> (which is marked verse-by-verse to indicate OT quotes in the NT) to marker="" who="OT" sID="somethingunique">... eID="somethingunique">. If you regard this as acceptable, then
Kahunapule Michael Johnson wrote:
> DM Smith wrote:
>> Kahunapule Michael Johnson wrote:
>>
>>> How does the Sword project handle display of OSIS text quotations when:
>>> 1. the or element is used without a marker attribute,
>>>
>>>
>> The speech element is not handled, except to proc
Chris Little wrote:
> I know XML allows for empty attribute values, but I'm not sure whether
> they are formally equivalent to no attribute at all.
>
No, actually there is nothing in XML that specifies such an equivalence.
It is the semantics of the particular application that determine that.
I
Chris Little wrote:
> DM Smith wrote:
>
4) Use milestoned version of the element and close the element by
changing the publisher's material, adding an ellipsis.
Lit saying, >>>
> The ...
>
>>> The added ellipsis would be bad, but if marker="" is not
DM Smith wrote:
Kahunapule Michael Johnson wrote:
How does the Sword project handle display of OSIS text quotations when:
1. the or element is used without a marker attribute,
The speech element is not handled, except to process its content. It is
as if the element
DM Smith wrote:
>>> 4) Use milestoned version of the element and close the element by
>>> changing the publisher's material, adding an ellipsis.
>>> Lit saying, >>> The ...
>> The added ellipsis would be bad, but if marker="" is not equivalent to
>> no marker attribute, then that would be a
Karl Kleinpaste wrote:
> One thing I have to observe is that even your mail message here came
> across claiming a character set of "windows-1252". There is also
> -1251 and possibly a couple others. These are very nonstandard,
> Microsoft-only encodings where \221 thru \227 (in particular) have
>
Kahunapule Michael Johnson wrote:
> How does the Sword project handle display of OSIS text quotations when:
> 1. the or element is used without a marker attribute,
>
The speech element is not handled, except to process its content. It is
as if the element were not in the text at all. I think
One thing I have to observe is that even your mail message here came
across claiming a character set of "windows-1252". There is also
-1251 and possibly a couple others. These are very nonstandard,
Microsoft-only encodings where \221 thru \227 (in particular) have
quotation/apostrophe/ellipsis ma
How does the Sword project handle display of OSIS text quotations when:
1. the or element is used without a marker attribute,
2. the or element is used with a marker attribute,
3. no or elements appear, or
4. quotation punctuation (“, ‘, ’, ”, «, », —, newline, etc.) appears
outside of or e
DM Smith wrote:
> In XML any attribute can have an empty value (btw, there is a unicode
> close quote above) and Sword/JSword handle it properly.
>
> But you have given me the idea to use an empty marker attribute for
> the eID milestone as in:
> The
>
That should work. :-) Of course, just n
On 4/29/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
> Hi,
>
> The accented Greek New Testament text is available from
> http://morphgnt.org/projects/ccat-morphgnt
> This is in word per line format, with morphology.
> (It is not a SWORD module.)
Check this mailing list's archive for a scri
On Apr 30, 2007, at 2:10 AM, Troy A. Griffitts wrote:
> DM, if you really intend below to say 'reiterates', and if I remember
> correctly, the intended OSIS tagging would be to use
> (which
> I'm not sure if SWORD supports yet) instead of , but from your
> example, I don't think "Lit." usually
On Apr 30, 2007, at 2:24 AM, Chris Little wrote:
>
>
> DM Smith wrote:
>> What is the proper way to markup a note that reiterates only a part
>> of a verse and that part is the start of a quotation which use in
>> the verse?
>>
>> Example:
>> The note is: (where {} indicate italics)
>> Lit {sayin
Chris Little wrote:
>> Lit saying,“The
>
> I think this would be my choice. Quote marks are perfectly valid in
> OSIS, you're just supposed to mark actual quotations with . Since
> this isn't an actual quotation, it seems valid to just use the mark itself.
Actually, I've reconsidered and a
Troy A. Griffitts wrote:
> The other benefit of using the basic SWORD API when processing XML is
> that we might find bugs when using it for processing the input (which, I
> believe DM might have found with his 3 tag example, though I always
> thought > had to be escaped to > Can someone chec
20 matches
Mail list logo
