thulester at gmail.com
Thu Nov 8 11:57:21 MST 2012
I don't remember who advised me to do module development in USFM then
convert to OSIS at the last step, but it was good advice (Dealing with USFM
for edits is far more manageable than OSIS).
I've started doing it that way ( I use to work directly in OSIS), so I
expect the need to convert from USFM to OSIS is likely pretty common.
On Thu, Nov 8, 2012 at 1:23 PM, Andrew Thule <thulester at gmail.com> wrote:
> .. and Bibleedit does a reasonably good job of converting USFM to OSIS as
> well ..
> On Thu, Nov 8, 2012 at 6:07 AM, Peter von Kaehne <refdoc at gmx.net> wrote:
>> > Von: Chris Burrell <chris at burrell.me.uk>
>> > Thanks for all the info. On the last point, I did mean read directly
>> > USFM. I don't know the format well-enough, but presumably if other
>> > software
>> > uses it, then maybe we could have a go at displaying the best we can...
>> I do not think this would be a good thing - other than for translators
>> who want to use some of our produce while working on the text. Instead of
>> sitting down once and fixing the text as we do right now you would end up
>> with endless niggles as USFM is really hard to debug completely - other
>> than by transforming it and uncovering problems that way.
>> But for translators, it might be useful - only both Paratext and more so
>> Bibledit do have a working set up where they can export their modules into
>> a rough and ready module and use on Xiphos, Bibletime etc.
>> So, all in all I am not sure if this is a useful direction to go to.
>> sword-devel mailing list: sword-devel at crosswire.org
>> Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sword-devel