Le 16 février 2018 16:48:09 WAT, Vince LaRue <vinsulation...@gmail.com> a écrit : >Hi Michael, > >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 appear 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
No you have nothing to install if you want to use bbd. >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. > >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? > >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. > >One other thing: I have been looking into Sketch Engine >(https://the.sketchengine.co.uk/) for producing a back-of-the-Bible >print concordance, and they recommend the "brat" annotation tool >(http://brat.nlplab.org/). Is this something that could at all be >useful >with a Bible text, or configured to output data that would be useful? > >Thanks, > >Vince > >Michael H wrote: >> Hi Vince, >> >> There isn't really a good native OSIS editing system. However, there >> are excellent Bible editing software programs available with no cost. >> >> I suggest you seek an USFM editor instead. Bibledit, Paratext, >> Autographa Lite, Translation Studio are all excellent programs. (See >> the links). 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'. >> >> 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.) >> >> Paratext: https://pt8.paratext.org/ >> Bibledit: http://bibledit.org/ >> I think Bibledit imports OSIS, if you already have worked toward >> clean OSIS. >> Autographa: https://www.autographa.com/ >> Translation Studio: https://unfoldingword.org/ts/ >> >> About USFM: http://ubsicap.github.io/usfm/ >> About USX: https://ubsicap.github.io/usx/ >> >> USFM2OSIS : https://github.com/adyeths/u2o (Is this the current one?) >> >> >> On Thu, Feb 15, 2018 at 8:09 PM, Vince LaRue ><vinsulation...@gmail.com >> <mailto:vinsulation...@gmail.com>> wrote: >> >> 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. >> >> I'm also the tech guy for what used to be the Valera Bible >Society >> (Sociedad Bíblica Valera) before it was put on ice, and now the >> website, www.valera1865.org <http://www.valera1865.org/>, 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. >> >> 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. >> >> 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: >> >> <p>EL EVANGELIO DE NUESTRO SEÑOR JESU CRISTO SEGÚN</p> >> >> <h1 align="left" >SAN MATEO</h1> >> >> <p> CAPITULO 1</p> >> >> <p>1 Libro de la generación de Jesu Cristo, hijo de David, hijo >de >> Abraham.</p> >> >> <p>2 Abraham engendró a Isaac; e Isaac engendró a Jacob; y Jacob >> engendró a Júdas, y a sus hermanos;</p> >> >> <p>3 Y Júdas engendró de Tamar a Fares y a Zara; y Fares engendró >> a Esrom; y Esrom engendró a Aram;</p> >> >> Thank you again for your time, and I look forward to working with >> you all. >> >> In Christ, >> >> Vince LaRue >> >> _______________________________________________ >> sword-devel mailing list: sword-devel@crosswire.org >> <mailto:sword-devel@crosswire.org> >> http://www.crosswire.org/mailman/listinfo/sword-devel >> <http://www.crosswire.org/mailman/listinfo/sword-devel> >> Instructions to unsubscribe/change your settings at above page >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel@crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
