Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-06-02 Thread Nic Carter
I agree with DM on the 3+ being condensed into 2 rule. That's what I currently try to do in PS & it works well (altho my version is a nasty hack & I'd love to remove that code). I also agree with titles being considered as 2 high, as it will naturally add extra vertical whitespace above and be

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-06-02 Thread Stephan
Hi, Old Testament THE FIRST BOOK OF MOSES CALLED GENESIS Introduction and Outline I think we should change this to different class names because I think a Testament or book header may have a different size than an introduction header. Let's make a basic header class and add a second for th

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-31 Thread DM Smith
Regarding your rule. I think it is generally good. But I'm wondering whether the rule should be that 3 or more are condensed to two (instead of 2+ into 1). I think regarding titles, most HTML renders them with extra vertical whitespace (half line above and below), so it'd be good to consider i

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-29 Thread Troy A. Griffitts
Just checked in another update for the whitespace issues. This checkin attempts to track vertical whitespace by counting block and output and mutes more than 2 contiguous vspace directives. e.g., This was changed in the osisReference output: to: Question: should directives be auto

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-21 Thread Troy A. Griffitts
Thanks for the feedback Peter. I'm not sure I understand what you mean. Could you give me a line in the OSISReference document which you feel is not rendered well. I just checked in an update which has preliminary support for tables, sub, and super. Here's the latest output: Old Testament T

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-20 Thread David Haslam
In USFM, this is the tag for major section *\ms * A related tag is *\mr* which (e.g.) is the range of Psalms in each major section. \c 1 \ms Գիրք 1 \mr (Սաղմոսներ 1–41) As it currently works, usfm2osis.py converts these as follows: Գիրք 1 (Սաղմոսներ 1–41) and so on. David -- View this messa

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-20 Thread Peter von Kaehne
On Sun, 2013-05-19 at 22:29 -0700, Troy A. Griffitts wrote: > OK, so here's my latest cut at the whitespace issue. From the > osisReference document here: > > http://crosswire.org/svn/sword/trunk/tests/testsuite/osisReference.xml > > ... we now get this output from the osisxhtml filter set when

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-19 Thread Troy A. Griffitts
OK, so here's my latest cut at the whitespace issue. From the osisReference document here: http://crosswire.org/svn/sword/trunk/tests/testsuite/osisReference.xml ... we now get this output from the osisxhtml filter set when rendering module top until Gen.1.2 (not the greatest output, but I be

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-17 Thread DM Smith
David, You've brought up 3 issues here. Two should be on separate threads. Regarding rendering of titles, an OSIS should be transformed into a , , ... element by the SWORD api when rendered to (x)html. If it is, then it will be rendered as a block element and not on the same line. If it does

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-17 Thread Pola Edward
As a module author, I totally agree with David, it was very hard to start and find a complete example to follow (Commentary) , Also had to test the module on many frontends to be sure that my work will be the same on all devices and OSs Making Complete tested examples, that covers all features a

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-17 Thread David Haslam
Hi Nic, No - I have not yet reached the stage of pushing the module I'm currently working on to either PocketSword or And Bible. Only tested it so far on Xiphos 3.1.5, xulsword 3.5 and Bible Desktop 1.6; all on Windows 7 x64. Yet all three front-end caused titles within chapters to be appended t

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-17 Thread Nic Carter
Have you tested those modules in PocketSword? Do they render their titles correctly? Sent from my phone, hence this email may be short... On 17/05/2013, at 21:41, David Haslam wrote: > But surely a related issue is that the titles in OSIS files generated by > usfm2osis.py don't even end up wi

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-17 Thread David Haslam
Vertical whitespace is one thing - I've certainly seen several modules in which the display has too much of it. But surely a related issue is that the titles in OSIS files generated by usfm2osis.py don't even end up with new line when the OSIS is converted to a module using osis2mod As Chris

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-09 Thread DM Smith
+1 I agree that OSIS uses divs in a different manner than HTML. IMHO, they should be ignored. We've outlined best practices regarding div in the wiki. They bound Bible, testament, book, chapter and section. Regarding the first four there is no reason to introduce any whitespace. Regarding sect

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-09 Thread Greg Hellings
On Thu, May 9, 2013 at 6:01 AM, Troy A. Griffitts wrote: > > > On 05/08/2013 12:31 PM, Troy A. Griffitts wrote: > > OK, so from this: > > > Old Testament > osisID="Gen" sID="gen2" type="book"/> THE FIRST BOOK OF MOSES CALLED >> GENESIS Introduction and >> Outline This is the Book of Genesis, t

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-09 Thread Peter von Kaehne
    > Von: "Troy A. Griffitts" > As a first run, I'm going to shoot for this below. Will this make > everyone happy regarding whitespace? Please ignore the poor table > output-- that another issue. > Old Testament > THE FIRST BOOK OF MOSES CALLED GENESIS > Introduction and Outline   I would

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-09 Thread Troy A. Griffitts
On 05/08/2013 12:31 PM, Troy A. Griffitts wrote: OK, so from this: Old Testament osisID="Gen" sID="gen2" type="book"/> THE FIRST BOOK OF MOSES CALLED GENESIS Introduction and Outline This is the Book of Genesis, the first book in the Bible. It may be outlined as follows: /> 1Creation of

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-08 Thread Nic Carter
Ok, I'm gonna top post and reply to various bits, sorry :) Is there any information that we need to keep in those divs that means we need to include either them or a placeholder for them? I just read that anchor tags don't exist in XHTML like they did in HTML 4.01, but you can have tags with

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-08 Thread Peter von Kaehne
On Wed, 2013-05-08 at 15:15 -0500, Greg Hellings wrote: > Off the cuff here, it seems the issue is the difference in semantics > of between OSIS - where it marks a structural division within a > text which can be of many different levels and layers and in XHTML > where it represents a box of bloc

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-08 Thread Troy A. Griffitts
Hi Greg, thanks for the ideas. Have a look at this thread: http://www.crosswire.org/pipermail/sword-devel/2005-April/022109.html But let's please keep this thread pragmatic to solving the problem holding up this release :) Any suggestions for WHAT the output should be? I wasn't thinking of

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

2013-05-08 Thread Greg Hellings
Off the cuff here, it seems the issue is the difference in semantics of between OSIS - where it marks a structural division within a text which can be of many different levels and layers and in XHTML where it represents a box of block-style layout which defaults to being the full width of its cont