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 all
On Sat, 2013-01-19 at 20:30 +0100, Troy A. Griffitts wrote:
>
> Peter von Kaehne 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 and intro
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 s
Peter von Kaehne 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 with t
On Sat, Jan 19, 2013 at 12:31 PM, Peter von Kaehne 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 frequent
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" --
On Sat, 2013-01-19 at 10:52 -0600, Greg Hellings wrote:
> On Sat, Jan 19, 2013 at 10:28 AM, Troy A. Griffitts
>
>
>
>
> BT outputs the following (found on lines 383ff of
> src/backend/filters/osistohtml.cpp):
> ..
>
I would second the BT change as slightly better than
*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?
Dav
On Tue, Jan 8, 2013 at 2:39 PM, Greg Hellings wrote:
> 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 there very straightforw
On Sat, Jan 19, 2013 at 10:28 AM, Troy A. Griffitts wrote:
> I've done my part and changed one more tag. transChange has been upgraded
> from:
>
>
> to:
>
> .transChangeSupplied {
> font-style: italic;
> }
>
>
>
> More changes welcome.
>
> Nic, you mentioned doing similar work on your own
I've done my part and changed one more tag. transChange has been
upgraded from:
to:
.transChangeSupplied {
font-style: italic;
}
More changes welcome.
Nic, you mentioned doing similar work on your own copies of our
filters. Any experience you'd like to share?
Bibletime, same. I
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. I
12 matches
Mail list logo