On Wed, Nov 6, 2013 at 4:59 AM, Itai Shaked <itai.sha...@mail.huji.ac.il> wrote:
> I probably should have mentioned that using Culmus fonts gives rise to many
> other problems (some I know workarounds for, some I don't). As far as I can
> understand, many of the problems arise from the fact that while (at least
> some of) these fonts contain English (or basic ASCII) characters, the OTF
> info doesn't register that, so you get lot's of errors when trying to use
> English and Hebrew in the same document (which happens a lot!).
>
> The simplest workaround is adding something like this in the preamble:
>
> \newfontfamily{\englishfont}{Times New Roman}
>
> \newfontfamily{\englishfontt}{Nimbus Sans L}
>
> \newfontfamily{\englishfonttt}{Nimbus Mono L}
>
>
> (substitute for your favorite free/non-free English fonts)
>
> But I still get some weird fontspec/polyglossia errors when trying to set a
> font other then default. I don't know enough about XeTeX to quite figure out
> why is that so, though. Some of the problems, at least, seem to be solved by
> reversing the order of the language / font tags in the TeX code [i.e.
> \textsf{\textenglish{sans-serif text}} rather than the
> \textenglish{\textsf{not-working}} generated by LyX. I don't know whether
> this could create other problems, though]Thanks for the warning and the workaround. This is indeed useful information for me. > And while we're at it - maybe it would be beneficial to allow setting > different fonts for different languages in LyX's document settings, so that > such preamble lines are not necessary :) Sounds reasonable to me (but remember I know little about this stuff). You could open an enhancement request at http://www.lyx.org/trac Scott
