On 08/02/2012 02:59 PM, Chris Little wrote:
> On 08/02/2012 11:54 AM, Kahunapule Michael Johnson wrote:
>> On 08/01/2012 09:17 PM, Chris Little wrote:
>>> End tags like \fqa* make little difference. Without the relaxed processing,
>>> the only difference my script makes is to not delete these end
On 08/02/2012 03:33 AM, Peter von Kaehne wrote:
Von: Chris Little I want them to have to
make a conscious decision to go on using a USFM converter on
non-USFM docs.
Sounds good.
When do you think you are ready to share?
Today, I hope. I've got every tag from the USFM reference handled,
exce
On 08/02/2012 11:54 AM, Kahunapule Michael Johnson wrote:
On 08/01/2012 09:17 PM, Chris Little wrote:
End tags like \fqa* make little difference. Without the relaxed processing, the
only difference my script makes is to not delete these end tags.
Simply deleting \fqa* might not have the inten
On 08/01/2012 09:17 PM, Chris Little wrote:
> End tags like \fqa* make little difference. Without the relaxed processing,
> the only difference my script makes is to not delete these end tags.
Simply deleting \fqa* might not have the intended effect. For example,
\f + could also be translate
> Von: Chris Little
> I want them to have to make a
> conscious decision to go on using a USFM converter on non-USFM docs.
Sounds good.
When do you think you are ready to share?
Wrt xreffix.pl - the main annoyance here is references have a huge variety of
delimiters which is strongly locale
On 08/01/2012 12:09 PM, Kahunapule Michael Johnson wrote:
c) Add a command-line switch to usfm2osis.py so that it performs a
pre-processing step of making non-conformant tags/syntax into
conformant markup. (This would be the same as option b, but would
place everything in a single utility.)
It
On 08/01/2012 01:11 AM, David Haslam wrote:
Three poorly defined uses of USFM verse tags that we often encounter are as
follows:
Spanned verses (translators use a verse range), thus
\v 7-11 Text for these five verses
or (worse still, a naughty use of the comma delimiter)
\v 3,4 Text for two c
On 01/08/12 20:36, Kahunapule Michael Johnson wrote:
> One problem with converting from USFM to Bible study software modules
> is that USFM doesn't directly support machine-readable links for
> cross references in cross reference notes and footnotes, and the
> mechanism to determine vernacular abb
On 07/31/2012 10:11 PM, David Haslam wrote:
> Peter and I have collected a substantial body of real world USFM suites
> which you could probably use for testing your conversion script.
Note that there is a collection of real-world USFM projects at
ftp://eBible.org/pub/Scriptures/ in files named *
On 07/31/2012 04:16 PM, Chris Little wrote:
> My new usfm2osis.py script is progressing quite nicely. I've got it
> generating valid OSIS from one Bible that uses a very minimal set of USFM
> elements. At the moment, I'm working to make it process all tags present
> within the USFM versions of t
o: "SWORD Developers' Collaboration Forum"
Subject: [sword-devel] USFM conformance in usfm2osis.py
Date: Wed, Aug 1, 2012 3:16 am
My new usfm2osis.py script is progressing quite nicely. I've got it
generating valid OSIS from one Bible that uses a very minimal set of
USFM element
On 01/08/12 09:11, David Haslam wrote:
> There are some empirical aspects of USFM that are not specified in the *USFM
> User Reference*.
> They seemed to be defined /de facto/ by UBS Paratext.
I think we need to distinguish between accepted practice and simply poor
functionality in Paratext. Para
Hi Chris,
There are some empirical aspects of USFM that are not specified in the *USFM
User Reference*.
They seemed to be defined /de facto/ by UBS Paratext.
Note that the USFM standard specifies the syntax for verse tags as:
*\v_#*
and does not have an underscore after the #.
In fact, some whi
WORD Developers' Collaboration Forum"
Subject: [sword-devel] USFM conformance in usfm2osis.py
Date: Wed, Aug 1, 2012 3:16 am
My new usfm2osis.py script is progressing quite nicely. I've got it generating
valid OSIS from one Bible that uses a very minimal set of USFM elements. At the
My new usfm2osis.py script is progressing quite nicely. I've got it
generating valid OSIS from one Bible that uses a very minimal set of
USFM elements. At the moment, I'm working to make it process all tags
present within the USFM versions of the WEB and RV, and this has raised
an issue.
I've
15 matches
Mail list logo
