> \addfontfeatures right now simply defines a new LaTeX font based on the
> active one, and appends the new feature, which is neither efficient nor
> robust (and works only with fontspec loaded fonts).
Quite interesting. Thanx.
Javier
--
Subscri
(Cross-posted, continues a thread started on TeX-Hyphen)
Arthur Reutenauer wrote:
> Since you'll be using XeTeX, you can take advantage of the fact that
> the two languages you'll be working with use disjoint character sets,
> and make the language switch automatic using XeTeX's inter-character
2013/9/12 Philip Taylor :
> (Cross-posted, continues a thread started on TeX-Hyphen)
>
> Arthur Reutenauer wrote:
>
>> Since you'll be using XeTeX, you can take advantage of the fact that
>> the two languages you'll be working with use disjoint character sets,
>> and make the language switch auto
On Thu, Sep 12, 2013 at 07:20:30PM -0400, Mike Maxwell wrote:
> In general, word breaking in scripts that don't indicate word
> boundaries is a partly unsolved research problem in computational
> linguistics--and from what I've heard, native speakers often
> disagree. (If you think that's odd, you
On Thu, Sep 12, 2013 at 09:17:57PM +0100, Philip Taylor wrote:
> Just to follow up on a thread started on the "TeX-Hyphen" list,
> where does one learn exactly what \XeTeXlinebreaklocale does ?
> TeXdoc XeTeX tells me :
>
> > \XeTeXlinebreaklocale ‹Locale ID›
> > Defines how to break lines for mul
Just to follow up on a thread started on the "TeX-Hyphen" list,
where does one learn exactly what \XeTeXlinebreaklocale does ?
TeXdoc XeTeX tells me :
> \XeTeXlinebreaklocale ‹Locale ID›
> Defines how to break lines for multilingual text.
but having read that, I am no wiser than I was before,
exc
On 9/12/2013 6:17 PM, Khaled Hosny wrote:
Some writing systems do not use spaces to separate words, so TeX’s
normal line breaking algorithm will fail. \XeTeXlinebreaklocale
instructs XeTeX to break the lines based on the rule of those writing
systems.
‹Locale ID› should be the ISO code of the la
