> ? Not sure what you mean. The filters produce the EntryAttributes
> entries. There is no direct access. The filters are still involved in
> formatting the EntryAttributes entries the way your frontend requires
> them (or should, when they are actually written/complete).
I probably spoke up t
Heres the list. I had it on disk.
Joachim
> > would it not be better to wait with the entyattribute stuff until the
> > sword api is redesigned (2.x -- not talking of BibleCS)?
>
> No, the redesign will not alter the EntryAttributes concept or the
> 'meat' of any functionality in 1.5.x. The re
> would it not be better to wait with the entyattribute stuff until the sword
> api is redesigned (2.x -- not talking of BibleCS)?
No, the redesign will not alter the EntryAttributes concept or the
'meat' of any functionality in 1.5.x. The redesign will simply change
the programming interfac
> Regarding footnotes. We have a mechanism in place to allow footnotes to
> be separated out from the verses. Look for the frontends to begin using
> these once we finish all the filters for the different markups. Coming
> soon hopefully!
Troy,
would it not be better to wait with the entyattr
> When trying to convert the Thai text to a zipped format, there was a problem
> with the default LZSS format. It produced a set of files but it did not
> display properly (an empty display or a few strange characters). Second
> attempt using the Zip format with the command line option, it is poss
"me too"-- I tried this with the CEDICT modules and couldn't get LZSS
to work (with either book, chapter or verse). ZIP is useless, since
for this module, it will increase the size by a few 100 percent (!).
Greetings,
Christian
--
[EMAIL PROTECTED] - http://www.web42.com/crenz/ - http://www.
