DM Smith wrote:
Kahunapule Michael Johnson wrote:
So... it sounds like I could simply convert USFM to OSIS with the
obvious conversions (like \p ... -> ...) plus
Remember to have the surround the entire paragraph.
Of course.
In various source I have seen the e
Kahunapule Michael Johnson wrote:
> So... it sounds like I could simply convert USFM to OSIS with the
> obvious conversions (like \p ... -> ...) plus
>
Remember to have the surround the entire paragraph.
In various source I have seen the equivalent of \p be nothing more than
a paragraph sepa
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
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
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
13 matches
Mail list logo
