G'day Karl,
On Fri, Oct 12, 2012 at 2:11 PM, Karl Kleinpaste k...@kleinpaste.orgwrote:
Is the foreign element passed through the engine? If so, do I need
to file bugs with front-ends to encourage support of foreign?
Having just looked, the string foreign does not appear in Sword's
source
foreign is the xml way of indicating a language other than the
language of the document. So you surround Hebrew text with foreign
xml:lang=heb. Judging from Ben's more recent email, even BPBible does
not support it. Regardless of the menthod, the effect is great.
I use Linux Libertine all the
On 10/12/2012 5:44 AM, Daniel Owens wrote:
foreign is the xml way of indicating a language other than the
language of the document. So you surround Hebrew text with foreign
xml:lang=heb.
A small sidenote, since you do encoding: heb is not a legal value for
xml:lang. This must be he or hbo if
On 10/12/2012 03:23 PM, Chris Little wrote:
On 10/12/2012 5:44 AM, Daniel Owens wrote:
foreign is the xml way of indicating a language other than the
language of the document. So you surround Hebrew text with foreign
xml:lang=heb.
A small sidenote, since you do encoding: heb is not a legal
Working on Abbott-Smith some things came together in my mind about
modules that mix languages. I have identified two problems.
First, modules that mix languages do not look good when fonts are chosen
per module rather than per language (regardless of the language of the
module). I go back and
I know nothing of foreign, but can only suppose that, if supported, it
must pass through the engine with an appropriate (HTML) indication.
As a general rule, I suggest either Free Serif or Linux Libertine, with
a slight preference for Free Serif. Both have good coverage across
every Latin
