<div>Just a quick note to inform everyone that after working closely with Vince LaRue since mid-February on text development for the Spanish RV1865,<br></div><div>earlier today I have (on his behalf) submitted the module to CrossWire for release.<br></div><div><br></div><div>It's been a pleasure to get to know Vince and work with him.<br></div><div>In the course of this work, I've also learnt a lot about Spanish as a language.<br></div><div><br></div><div class="protonmail_signature_block"><div class="protonmail_signature_block-user"><div>Best regards,<br></div><div><br></div><div>David<br></div></div><div><br></div><div class="protonmail_signature_block-proton">Sent with <a href="https://protonmail.com" target="_blank">ProtonMail</a> Secure Email.<br></div></div><div><br></div><div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br></div><div> On 16 February 2018 3:48 PM, Vince LaRue <vinsulation117@gmail.com> wrote:<br></div><div> <br></div><blockquote class="protonmail_quote" type="cite"><div>Hi Michael,<br></div><div> <br></div><div> ParaTExt doesn't run on OSX, and I don't have the mental system
resources to muck about with Wine, or the money to get Crossover.
Autographa Lite doesn't seem to do anything; it opens and doesn't appear
to let me do anything (maybe I'm missing something; I'm not the
brightest bulb). translationStudio doesn't <i>appear</i> to allow rudimentary markup like italics, at
least not that I could figure out in the half an hour or so that I
wrestled with it. Bibleedit appears to require me to install a server
app, which I really don't want to do in order to convert an already
complete Bible in XML into another format. I was happy working in plain
text, but the sheer volume of the work would hinder making this
available quickly.<br></div><div> <br></div><div> Another question: if OSIS is no longer the best way to produce digital
texts (which is my only interest currently), then why is nothing said
about a different preferred method on the Crosswire wiki? The last
information I can find is the 2.1.1 OSIS schema from 2006, and it's
consistently referenced throughout the wiki. Is that not a reliable
source of information? <br></div><div> <br></div><div> Please pardon my incessant questions; I'm simply trying to figure out
the best way to make this Bible available electronically. The print
version is a parallel but separate endeavor, though I hope that the
digital prep process will produce a file that can be continually
annotated to eventually produce a reference Bible, both print and
digital. <br></div><div> <br></div><div> One other thing: I have been looking into Sketch Engine
(<a href="https://the.sketchengine.co.uk/" class="moz-txt-link-freetext">https://the.sketchengine.co.uk/</a>) for producing a back-of-the-Bible
print concordance, and they recommend the "brat" annotation tool
(<a href="http://brat.nlplab.org/" class="moz-txt-link-freetext">http://brat.nlplab.org/</a>). Is this something that could at all be useful
with a Bible text, or configured to output data that would be useful?<br></div><div> <br></div><div> Thanks,<br></div><div> <br></div><div> Vince<br></div><div> <br></div><div> <span>Michael H wrote:</span><br></div><div> <br></div><blockquote type="cite"><div dir="ltr"><div>Hi Vince, <br></div><div><br></div><div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">There
isn't really a good native OSIS editing system. However, there are
excellent Bible editing software programs available with no cost. <br></div></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><br></div><div>I
suggest you seek an USFM editor instead. Bibledit, Paratext, Autographa
Lite, Translation Studio are all excellent programs. (See the links). <span class="highlight" style="background-color:rgb(255, 255, 255)"><span class="colour" style="color:rgb(34, 34, 34)"><span class="font" style="font-family:arial,sans-serif"><span class="size" style="font-size:small">Each
of these programs has checking tools which will greatly improve your
ability to detect issues with your Bible text, and to correct the issues
you find. Once you have a clean USFM, conforming to OSIS is relatively
simple. I believe the preferred method these days is a python script
'u2o.py'. </span></span></span></span><br></div><div><br></div><div><span class="highlight" style="background-color:rgb(255, 255, 255)"><span class="colour" style="color:rgb(34, 34, 34)"><span class="font" style="font-family:arial,sans-serif"><span class="size" style="font-size:small">OSIS
is an output intended for computers. USFM is a tagging language that
is usable by humans and computers, which produces USX (An xml language
similar to OSIS, but designed this decade by the same groups that
produced OSIS in the early 2000's.)</span></span></span></span><br></div><div><br></div><div>Paratext: <a href="https://pt8.paratext.org/">https://pt8.paratext.org/</a><br></div><div>Bibledit: <a href="http://bibledit.org/">http://bibledit.org/</a><br></div><div>
I think Bibledit imports OSIS, if you already have worked toward
clean OSIS. <br></div><div>Autographa: <a href="https://www.autographa.com/">https://www.autographa.com/</a><br></div><div><div>Translation
Studio: <a href="https://unfoldingword.org/ts/">https://unfoldingword.org/ts/</a><br></div><div><br></div><div>About
USFM: <a href="http://ubsicap.github.io/usfm/">http://ubsicap.github.io/usfm/</a><br></div><div>About
USX: <a href="https://ubsicap.github.io/usx/">https://ubsicap.github.io/usx/</a><br></div></div><div><br></div><div>USFM2OSIS
: <a href="https://github.com/adyeths/u2o">https://github.com/adyeths/u2o</a> (Is this the current one?) <br></div><div><br></div></div><div class="gmail_extra"><div><br></div><div class="gmail_quote"><div>On Thu, Feb 15,
2018 at 8:09 PM, Vince LaRue <span dir="ltr"><<a target="_blank" href="mailto:vinsulation117@gmail.com">vinsulation117@gmail.com</a>></span> wrote:<br></div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex" class="gmail_quote"><div bgcolor="#FFFFFF"><div>Hello, and thank you for accepting my request to join the mailing list.
My name is Vince LaRue and I'm a missionary in Southern Chile. I use
Eloquent almost exclusively, despite the frequent crashes, and I'd like
to do whatever is in my limited (non-programmer) capacity to help the
SWORD project. <br></div><div> <br></div><div> I'm also the tech guy for what <i>used to
be</i> the Valera Bible Society (Sociedad Bíblica Valera) before it
was put on ice, and now the website, <a target="_blank" href="http://www.valera1865.org/">www.valera1865.org</a>,
which I run,
is a source for information about the RV1865. We've had the Bible itself
back in print for 17 years now, but the various digital versions have
been plagued with sundry typographical issues. I'm fixing that.<br></div><div> <br></div><div> We're basically done with a complete, verse-by-verse overhaul of the
text, and I have it in a cleaned-up verse-per-line format in basic HTML
(each verse enclosed in <p> tags) broken down into 23 text files. I
would like to produce a high-quality OSIS version that I can continue
to work on, adding various tags throughout the text, but the goal is to
get it ready for distribution immediately. <br></div><div> <br></div><div> What are the steps that I need to take to make this happen? Are there
utilities that can convert what I have to OSIS-compatible XML? Here's a
sample:<br></div><div> <br></div><div> <p>EL EVANGELIO DE NUESTRO SEÑOR JESU CRISTO SEGÚN</p><br></div><div> <br></div><div> <h1 align="left" >SAN MATEO</h1><br></div><div> <br></div><div> <p> CAPITULO 1</p><br></div><div> <br></div><div> <p>1 Libro de la generación de Jesu Cristo, hijo de David, hijo de
Abraham.</p><br></div><div> <br></div><div> <p>2 Abraham engendró a Isaac; e Isaac engendró a Jacob; y Jacob
engendró a Júdas, y a sus hermanos;</p><br></div><div> <br></div><div> <p>3 Y Júdas engendró de Tamar a Fares y a Zara; y Fares engendró a
Esrom; y Esrom engendró a Aram;</p><br></div><div> <br></div><div> Thank you again for your time, and I look forward to working with you
all.<br></div><div> <br></div><div> In Christ,<br></div><div> <br></div><div> Vince LaRue<br></div></div><div><br></div><div>______________________________<wbr>_________________<br></div><div> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br></div><div> <a target="_blank" rel="noreferrer" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/<wbr>mailman/listinfo/sword-devel</a><br></div><div> Instructions to unsubscribe/change your settings at above page<br></div></blockquote></div></div><pre wrap="">_______________________________________________
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" class="moz-txt-link-abbreviated">sword-devel@crosswire.org</a>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" class="moz-txt-link-freetext">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page<br></pre></blockquote></blockquote><div><br></div>