Re: [sword-devel] USFM conformance in usfm2osis.py

2012-08-02 Thread Kahunapule Michael Johnson
On 08/02/2012 02:59 PM, Chris Little wrote: > On 08/02/2012 11:54 AM, Kahunapule Michael Johnson wrote: >> On 08/01/2012 09:17 PM, Chris Little wrote: >>> End tags like \fqa* make little difference. Without the relaxed processing, >>> the only difference my script makes is to not delete these end

Re: [sword-devel] USFM conformance in usfm2osis.py

2012-08-02 Thread Chris Little
On 08/02/2012 03:33 AM, Peter von Kaehne wrote: Von: Chris Little I want them to have to make a conscious decision to go on using a USFM converter on non-USFM docs. Sounds good. When do you think you are ready to share? Today, I hope. I've got every tag from the USFM reference handled, exce

Re: [sword-devel] USFM conformance in usfm2osis.py

2012-08-02 Thread Chris Little
On 08/02/2012 11:54 AM, Kahunapule Michael Johnson wrote: On 08/01/2012 09:17 PM, Chris Little wrote: End tags like \fqa* make little difference. Without the relaxed processing, the only difference my script makes is to not delete these end tags. Simply deleting \fqa* might not have the inten

Re: [sword-devel] No errors. Valid OSIS. Not working. Looking for suggestions.

2012-08-02 Thread Andrew Thule
Yes, thank you for the suggestions all. Peter, your instincts are correct - it was a pathing problem. Cheers ~A On Thu, Aug 2, 2012 at 1:49 PM, DM Smith wrote: > Try creating a "raw" module and open the data files with a text editor to see > if they have what you expect. The -d 2 flag is usefu

Re: [sword-devel] USFM conformance in usfm2osis.py

2012-08-02 Thread Kahunapule Michael Johnson
On 08/01/2012 09:17 PM, Chris Little wrote: > End tags like \fqa* make little difference. Without the relaxed processing, > the only difference my script makes is to not delete these end tags. Simply deleting \fqa* might not have the intended effect. For example, \f + could also be translate

Re: [sword-devel] No errors. Valid OSIS. Not working. Looking for suggestions.

2012-08-02 Thread DM Smith
Try creating a "raw" module and open the data files with a text editor to see if they have what you expect. The -d 2 flag is useful in understanding the data file. I agree w/ Peter et al, it is almost always a conf or a file permission problem. In Him, DM On Aug 2, 2012, at 10:29 AM, An

Re: [sword-devel] No errors. Valid OSIS. Not working. Looking for suggestions.

2012-08-02 Thread Andrew Thule
I haven't had a chance to explore Peter's recommendations yet, but I know it isn't file permissions. I have a script that auto-magically corrects them as part of the same process that runs osis2mod. Both suggestions make me think the problem is below the client application, which is consistent wi

Re: [sword-devel] No errors. Valid OSIS. Not working. Looking for suggestions.

2012-08-02 Thread Brian J Dumont
... or maybe file permissions on the module or conf file? On 08/02/2012 12:35 PM, Peter von Kaehne wrote: Usually path or driver errors. Wrong path to module or mismatch between driver and conf entry re driver. Peter On 02/08/12 15:29, Andrew Thule wrote: I'm working on a 'commentary' for

Re: [sword-devel] No errors. Valid OSIS. Not working. Looking for suggestions.

2012-08-02 Thread Peter von Kaehne
Usually path or driver errors. Wrong path to module or mismatch between driver and conf entry re driver. Peter On 02/08/12 15:29, Andrew Thule wrote: > I'm working on a 'commentary' for the first time and having some trouble. > > I very much like the module OTPassages. Chris has given me an IMP

[sword-devel] No errors. Valid OSIS. Not working. Looking for suggestions.

2012-08-02 Thread Andrew Thule
I'm working on a 'commentary' for the first time and having some trouble. I very much like the module OTPassages. Chris has given me an IMP file of the module OTPassages (quoted in the NT) which I have converted to OSIS, xmllintetd and run through osis2mod all without problems. When I use osis2mo

Re: [sword-devel] SCRIPT: Covert Traditional Book Names to Short Sword Names

2012-08-02 Thread Peter von Kaehne
> Von: David Haslam > OSIS is an external standard, not merely internal to CrossWire. See > http://www.bibletechnologies.net/ That and Matthew Matthe Matth Matt Mat Ma M are all automatically deducted by the engine, but something like Pss for Psalms is not. The abbreviation section does th

Re: [sword-devel] USFM conformance in usfm2osis.py

2012-08-02 Thread Peter von Kaehne
> Von: Chris Little > I want them to have to make a > conscious decision to go on using a USFM converter on non-USFM docs. Sounds good. When do you think you are ready to share? Wrt xreffix.pl - the main annoyance here is references have a huge variety of delimiters which is strongly locale

Re: [sword-devel] SCRIPT: Covert Traditional Book Names to Short Sword Names

2012-08-02 Thread David Haslam
Dear Andrew, OSIS is an external standard, not merely internal to CrossWire. See http://www.bibletechnologies.net/ (Notwithstanding that some CrossWire volunteers were closely involved in its creation and updates.) Best regards, David -- View this message in context: http://sword-dev.350566.

Re: [sword-devel] USFM conformance in usfm2osis.py

2012-08-02 Thread Chris Little
On 08/01/2012 12:09 PM, Kahunapule Michael Johnson wrote: c) Add a command-line switch to usfm2osis.py so that it performs a pre-processing step of making non-conformant tags/syntax into conformant markup. (This would be the same as option b, but would place everything in a single utility.) It