[sword-devel] Method Name Normalization

2013-01-19 Thread Troy A. Griffitts
In anticipation of a new release, I have a large checkin I'm about to commit which will break everything for everyone compiling with -Werror. We've been normalizing method names toward a clean API interface at 2.0. SWORD started 20+ years ago when there was not standard naming conventions.

[sword-devel] XHTML Filterset

2013-01-19 Thread Troy A. Griffitts
I've done my part and changed one more tag. transChange has been upgraded from: i/i to: .transChangeSupplied { font-style: italic; } span class=transChangeSupplied/span More changes welcome. Nic, you mentioned doing similar work on your own copies of our filters. Any experience

Re: [sword-devel] XHTML Filterset

2013-01-19 Thread Greg Hellings
On Sat, Jan 19, 2013 at 10:28 AM, Troy A. Griffitts scr...@crosswire.orgwrote: I've done my part and changed one more tag. transChange has been upgraded from: i/i to: .transChangeSupplied { font-style: italic; } span class=transChangeSupplied/**span More changes welcome.

Re: [sword-devel] SFTP Support

2013-01-19 Thread Greg Hellings
On Tue, Jan 8, 2013 at 2:39 PM, Greg Hellings greg.helli...@gmail.comwrote: Thanks! I updated CMake as we talked about. The current SVN HEAD of Xiphos now has support for adding SFTP sources through its module manager. Shout-out to Karl (or whoever wrote that dialog) for making the code

Re: [sword-devel] XHTML Filterset

2013-01-19 Thread David Haslam
*Observation:* Not all writing systems support italics! e.g. How do or should we display transChange items for Chinese? c.f. An established method in printed texts is to use dotted underline. Is our XHTML filterset capable of addressing such requirements? If not, how might this be achieved?

Re: [sword-devel] XHTML Filterset

2013-01-19 Thread Peter von Kaehne
On Sat, 2013-01-19 at 10:52 -0600, Greg Hellings wrote: On Sat, Jan 19, 2013 at 10:28 AM, Troy A. Griffitts span class=transChangeSupplied/span BT outputs the following (found on lines 383ff of src/backend/filters/osistohtml.cpp): span class=transchangespan

Re: [sword-devel] Method Name Normalization

2013-01-19 Thread Peter von Kaehne
On Sat, 2013-01-19 at 17:13 +0100, Troy A. Griffitts wrote: Headings() has been renamed to setIntros(bool) and bool isIntros() Headings() -- used to turn on chapter, book, testament, and module introductions, has frequently been a point of confusion with the global option Headings -- used

Re: [sword-devel] Method Name Normalization

2013-01-19 Thread Greg Hellings
On Sat, Jan 19, 2013 at 12:31 PM, Peter von Kaehne ref...@gmx.net wrote: On Sat, 2013-01-19 at 17:13 +0100, Troy A. Griffitts wrote: Headings() has been renamed to setIntros(bool) and bool isIntros() Headings() -- used to turn on chapter, book, testament, and module introductions, has

Re: [sword-devel] Method Name Normalization

2013-01-19 Thread Troy A. Griffitts
Peter von Kaehne ref...@gmx.net wrote: On Sat, 2013-01-19 at 17:13 +0100, Troy A. Griffitts wrote: Headings() has been renamed to setIntros(bool) and bool isIntros() Headings() -- used to turn on chapter, book, testament, and module introductions, has frequently been a point of confusion

[sword-devel] Vertical whitespace

2013-01-19 Thread DM Smith
I've noticed that OSIS modules sometimes render with a lot of vertical whitespace (blank lines). I'd like for this to be sorted as part of the next release. I don't think it'd be too hard. I've been in the osishtmlhref filter to see if I could figure it out, but it is beyond me. So this is a

Re: [sword-devel] Method Name Normalization

2013-01-19 Thread Peter von Kaehne
On Sat, 2013-01-19 at 20:30 +0100, Troy A. Griffitts wrote: Peter von Kaehne ref...@gmx.net wrote: Does this mean that headings and intros are now formally separated? They always have been. They have never had anything to do with each other. On Xiphos these are the same. Turn on headings

[sword-devel] Pre-verse div and headings

2013-01-19 Thread DM Smith
This might be related to the other thread of name normalization that is discussing intros and headings. Prior to the pre-verse div, everything that was pre-verse was a title, aka heading. The purpose of the pre-verse div was to allow any kind of markup between verses. The net result is that