-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So to sum this up:
* RTF lexing rules (especially regarding control word delimiters etc)
should be used for the rest of the .conf file line after About=.
* RTF groups are not allowed.
* RTF control symbols are not allowed.
* Of RTF control words, only
Worth noting in passing that jsword currently let's the frontend handle
these including the unicode characters marked using rtf notation.
Chris
On 18 May 2014 18:03, "DM Smith" wrote:
> Only a subset is allowed in the conf. The following page gives details.
> SwordWeb and JSword assume that the
Only a subset is allowed in the conf. The following page gives details.
SwordWeb and JSword assume that the field is RTF even if plain text. \oar looks
like a typo for \par.
http://www.crosswire.org/wiki/DevTools:conf_Files
> On May 18, 2014, at 11:10 AM, Jaak Ristioja wrote:
>
> -BEGIN
I believe there is a standard class in the engine that does an RTF to HTML
conversion on arbitrary text. You should be able to pass these entries
through that converter to get out reasonable text.
--Greg
On May 18, 2014 10:12 AM, "Jaak Ristioja" wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Has
