The real problem is that I'm finding new bugs in usfm2osis.py faster than
anyone is actually putting in effort to fix them.
I just added a new issue in JIRA - the examples given are concise and
adequately described.
http://www.crosswire.org/tracker/browse/MODTOOLS-90
I'm not a Python programmer.
Chris,
Happy New Year!
Thanks for fixing the (missing final ") on Dec 31.
To catch up with the extra command line option (-l langcode) that Peter
added in SVN at CrossWire is an immediate need.
He was unaware of the move to GitHub when he made that improvement.
Regards,
David
--
View this
Today, I have been examining the locations and common causes for all the
validation errors in OSIS files generated by usfm2osis.py for Arfon Jones
beibl.net translation, for which we have a complete set of 66 SFM files.
A lot of progress has been made through careful detailed analysis.
There were
On 2014-12-31, 19:00 GMT, Matěj Cepl wrote:
> On 2014-12-31, 12:00 GMT, Barry Drake wrote:
>> I've been following the comments about usfm2osis.py. I agree
>> that more information on errors would help a lot. The current
>> error I'm getting is:
>> Validating XML...
>> XML Validation error: Elem
On 2014-12-31, 12:00 GMT, Barry Drake wrote:
> I've been following the comments about usfm2osis.py. I agree
> that more information on errors would help a lot. The current
> error I'm getting is:
> Validating XML...
> XML Validation error: Element
> '{http://www.bibletechnologies.net/2003/OSIS
On 31/12/14 14:03, David Haslam wrote:
As regards, OSIS Validation Error reporting, a lot depends on which XML tool
one is using. But I agree, it's often hard to locate exactly the place that
causes each
issue.
The example Barry gave with that extraordinary long regex pattern is
certainly not v
On 12/31/2014 07:00 AM, Barry Drake wrote:
> I think CHM is only of use in Microsoft Windows - am I right?
"Compiled HtMl". Yes, Windows. Buton Linux, xchm and chmsee are
useful. And we generate *.chm for Xiphos mostly on Linux.
___
sword-devel mailin
Further to the LANG patch Peter programmed, my activities yesterday unearthed
a typo error in usfm2osis.py
A closing quotation mark is missing for an attribute string.
This is the line in usfm2osis.py with the typo.
tType =
{'th':' role="label"', 'thr':' role="label" type="x-right"', 'tc':'',
't
On our wiki page, there's a link to the program called XML Copy Editor.
This is currently useless for XML validation using a remote schema location.
For an OSIS file that Notepad++ can parse and validate quite happily,
XML Copy Editor stops with the following error:
"FatalError at line 0, colum
On December 31, 2014 7:00:25 AM EST, Barry Drake wrote:
>On 31/12/14 09:20, David Haslam wrote:
> I think CHM is only of use in
> Microsoft Windows - am I right?
It is a windows native format, but there are Linux applications to read them.
That said, the pdf link you gave is probably more usefu
CHM is a Windows Help Format.
See https://en.wikipedia.org/wiki/Microsoft_Compiled_HTML_Help
FWIW, CHM files can be also read on some other systems, given a suitable
app.
e.g. On iOS devices with the app called CHM+ which I have installed in my
iPad Mini.
As regards, OSIS Validation Error report
On 31/12/14 09:20, David Haslam wrote:
For USFM see http://paratext.org/about/usfm
The PDF usfm spec is at:
http://paratext.org/system/files/usfmReference2_4.pdf I think CHM is
only of use in Microsoft Windows - am I right?
I've been following the comments about usfm2osis.py. I agree tha
Ryan,
For USFM see http://paratext.org/about/usfm
For OSIS see http://www.bibletechnologies.net/
Useful to download the PDF file for OSIS and the CHM file for USFM.
Also see the OSIS related pages in our developers' wiki.
http://crosswire.org/wiki/
David
--
View this message in context:
h
Cant give
On 30 Dec 2014 19:57, Ryan Hiebert wrote:
>
> I am a full-time Python developer, but I’m not very familiar with USFM or
> OSIS, so that’s where I’m lacking knowledge. I’ll read over the code on
> Github (I’ve already started), but I’m wondering if anyone has any pointers
> as far as g
I am a full-time Python developer, but I’m not very familiar with USFM or OSIS,
so that’s where I’m lacking knowledge. I’ll read over the code on Github (I’ve
already started), but I’m wondering if anyone has any pointers as far as good
references for learning about those two formats.
Ryan Hieb
Thanks Chris,
Peter would therefore need to merge his yesterday's patch for "-l LANGUAGE"
into the file now maintained on github,
bearing in mind that the latter was reduced to 80 cols back in April, so
line numbers would no longer match.
btw. I have updated the download link in our wiki page. Se
On 12/28/2014 12:06 PM, David Haslam wrote:
With Chris being otherwise engaged, there's a crying need for an accomplished
Python programmer
to pick up where he last left off on developing and debugging the OSIS
converter usfm2osis.py
There are several issues in the CrossWire tracker, should anyo
Hi Robert,
" (e.g., when \d is used as a paragraph type marker with verses
logically "inside" the \d marker which is not actually documented [nor
banned] in the USFM specification)"
This is the subject of a separate (ongoing) email discussion that I started
the other day.
Actual thread titl
> On Dec 29, 2014, at 2:28 PM, Robert Hunt wrote:
>
> On 30/12/14 06:29, Peter von Kaehne wrote:
>> It is very well written and neatly done and does its job with near
>> perfection. I would welcome contributions to it, as long as they are
>> equally well done.
> Just for your info: usfm2osis.py
On 30/12/14 08:47, Peter Von Kaehne wrote:
As it stands - and I guess apart from David and Chris I
am probably one of the most prolific users of this and the
last, Perl based script, the occasions where I ended up in a
cr
%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20ORDER%20BY%20priority%20DESC
Thanks!
Peter
Gesendet: Montag, 29. Dezember 2014 um 19:35 Uhr
Von: "Greg Hellings"
An: "SWORD Developers' Collaboration Forum"
Betreff: Re: [sword-devel] A call for Python program
If you provide undefined/invalid input then the behavior of a convenience
script being undefined should be no surprise. It is not the place of this
script to be a USFM verification tool.
--Greg
On Dec 29, 2014 2:28 PM, "Robert Hunt" wrote:
> On 30/12/14 06:29, Peter von Kaehne wrote:
>
> It is
On 30/12/14 06:29, Peter von Kaehne wrote:
It is very well written and neatly done and does its job with near
perfection. I would welcome contributions to it, as long as they are
equally well done.
Just for your info: usfm2osis.py basically treats each USFM book as
> Gesendet: Montag, 29. Dezember 2014 um 18:13 Uhr
> Von: "Peter Von Kaehne"
>
> > Gesendet: Montag, 29. Dezember 2014 um 17:29 Uhr
> > Von: "Peter von Kaehne"
>
> >
> > I think the first task should be to evaluate JIRA's list and close down
> > as "won't fix" or as otherwise invalid what sh
> Gesendet: Montag, 29. Dezember 2014 um 17:29 Uhr
> Von: "Peter von Kaehne"
>
> I think the first task should be to evaluate JIRA's list and close down
> as "won't fix" or as otherwise invalid what should not get done. Also
> sort feature requests from bugs. I have done now some of this.
Have
On Mon, 2014-12-29 at 11:43 -0500, DM Smith wrote:
> Python is a pretty easy language for a programmer to learn. I’ve read a book
> on how to program in it. There’s a nice tutorial on the python website. But
> I’ve not done any serious programming in python. Just maintenance and
> debugging.
I
On 29/12/14 16:43, DM Smith wrote:
Python is a pretty easy language for a programmer to learn. I’ve read a book on
how to program in it. There’s a nice tutorial on the python website. But I’ve
not done any serious programming in python. Just maintenance and debugging.
Thanks for pointing me tow
Python is a pretty easy language for a programmer to learn. I’ve read a book on
how to program in it. There’s a nice tutorial on the python website. But I’ve
not done any serious programming in python. Just maintenance and debugging.
The only thing I found bothersome was the strict use of indent
Barry,
The Perl script was not comprehensive in terms of USFM tag coverage.
No further work is expected for usfm2osis.pl
usfm2osis.pl is now deprecated.
The Python script really is the way forward, despite its issues. Please see
http://crosswire.org/wiki/Converting_SFM_Bibles_to_OSIS#usfm2osis
usfm2osis was originally written in perl. Chris re-wrote it in python. It has
progressed/diverged significantly since then.
In Him,
DM
> On Dec 29, 2014, at 11:14 AM, Barry Drake wrote:
>
> On 28/12/14 20:06, David Haslam wrote:
>> With Chris being otherwise engaged, there's a crying n
On 28/12/14 20:06, David Haslam wrote:
With Chris being otherwise engaged, there's a crying need for an accomplished
Python programmer to pick up where he last left off on developing and debugging
the OSIS
converter usfm2osis.py
Hi David . I'm very interested in this project. I looked at
With Chris being otherwise engaged, there's a crying need for an accomplished
Python programmer
to pick up where he last left off on developing and debugging the OSIS
converter usfm2osis.py
There are several issues in the CrossWire tracker, should anyone be
interested and motivated enough to volun
32 matches
Mail list logo
