<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="+1"><font face="Arial Unicode MS">That sounds like a big
task. Assuming the Thai is unicode, somehow you have to get the
documents into an xml file encoded in utf8. For the Bible obviously
USFM is the preferred option as an intermediate step because you can
use USFM editors like Bibedit, SIL FieldWorks, etc., to edit USFM more
or less in a user friendly way (You are probably familiar with these,
but if not search for them online). OSIS is good when you want to go to
SWORD, but it's not as easy to learn and work with. Bibledit offers the
option of exporting to a SWORD module, which is very attractive since
it gives you immediate feedback and a hopefully gratifying result. Once
your USFM files are really good, then you can use some other converter
to convert it to OSIS. <br>
<br>
I once took some RTF files of a Bible and did some search and replace
operations using the kind of markup you describe to convert it to USFM.
It was a bit laborious and not necessarily the best way to go about it,
but you have to start somewhere. For italics, bold, etc., Word seems to
work well. Use wildcards and search for the markup, adding USFM markers
when you replace things. This assumes that their markup is consistent,
though.</font></font><font size="+1"><font face="Arial Unicode MS"> In
my case it helped that there
were styles named after some older translation program whose name is
escaping me, so I used OpenOffice to go the rest of the way because you
can search and replace by style.</font></font><br>
<font size="+1"><font face="Arial Unicode MS"><br>
For the book you should consider using OpenOffice since you can open
Word files in it easily, save it as ODT, and export as XML. Basically
for a book you just need to distinguish Parts, Chapters, Sections, and
so on. Scripture references, tables, and a few other things may factor
in as well. The filter I worked on for OpenOffice (exporting to OSIS
for Genbooks) worked well with version 2.4, but I'm not sure about
version 3. I need to work on it sometime. You can find it at
<a class="moz-txt-link-freetext" href="http://sites.google.com/site/danielowensstuff/">http://sites.google.com/site/danielowensstuff/</a>. There are instructions
in English.<br>
<br>
</font></font>Daniel<br>
<br>
Adrian Korten wrote:
<blockquote cite="mid:49A75684.8070302@sil.org" type="cite">Good day,
<br>
<br>
By inline markup, I mean that it is bolded, centred, super-scripted,
etc. (Sorry, I'm not sure of the right terminology but may display
markup would have been a better term.) But no standard format markup. I
would either recommend that they markup with USFM or OSIS.
<br>
<br>
ak
<br>
<br>
<br>
----- Original Message -----
<br>
*From:* Daniel Owens <a class="moz-txt-link-rfc2396E" href="mailto:dhowens@pmbx.net"><dhowens@pmbx.net></a>
<br>
*To:* "SWORD Developers' Collaboration Forum"
<a class="moz-txt-link-rfc2396E" href="mailto:sword-devel@crosswire.org"><sword-devel@crosswire.org></a>
<br>
*Sent:* 02/26/2009 4:28:05 PM +0700
<br>
*Subject:* [sword-devel] OSIS editor
<br>
<br>
<br>
<blockquote type="cite">Adrian,
<br>
<br>
What does the inline markup look like? I mean, is it like standard
format markup (USFM, MDF, etc.), or am I way off the mark?
<br>
<br>
Daniel
<br>
<br>
Peter von Kaehne wrote:
<br>
<blockquote type="cite">Adrian Korten wrote:
<br>
<blockquote type="cite">Good day,
<br>
<br>
I'm advising a team of Thai people who would like to prepare a Bible
and book for import to Sword. They currently have both texts in Word
with in-line mark-up (no styles). I assume that they would need to save
as raw text and then start adding the markup. Could someone advise on a
good editor for this? Or a strategy for doing this? </blockquote>
<br>
There is a XSLT style sheet for OpenOffice Export to Genbook format.
This would be an easy way to create markup for the book at least.
<br>
<br>
Peter
<br>
<br>
_______________________________________________
<br>
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:sword-devel@crosswire.org"><mailto:sword-devel@crosswire.org></a>
<br>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
<br>
Instructions to unsubscribe/change your settings at above page
<br>
<br>
</blockquote>
------------------------------------------------------------------------
<br>
<br>
_______________________________________________
<br>
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
<br>
Instructions to unsubscribe/change your settings at above page
<br>
</blockquote>
<br>
_______________________________________________
<br>
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
<br>
Instructions to unsubscribe/change your settings at above page
<br>
<br>
</blockquote>
</body>
</html>