Re: [XeTeX] Basic CJK support in Polyglossia

2013-01-15 Thread Zdenek Wagner
2013/1/15 Hans Schmidt : > Am 14.01.2013 22:53, schrieb Jérôme Étévé: > >> Hi, >> >> There's a pretty good post here that describes a simple method to fallback >> to >> CJK fonts even when they're mixed with roman text. >> >> http://latex-my.blogspot.co.uk/2012/06/more-ways-to-typeset-cjk.html >> >

Re: [XeTeX] Basic CJK support in Polyglossia

2013-01-15 Thread Hans Schmidt
Am 14.01.2013 22:53, schrieb Jérôme Étévé: Hi, There's a pretty good post here that describes a simple method to fallback to CJK fonts even when they're mixed with roman text. http://latex-my.blogspot.co.uk/2012/06/more-ways-to-typeset-cjk.html Cheers, Jerome. Hello, Thanks for the help. A

Re: [XeTeX] redefining Unicode characters

2013-01-15 Thread Andy Lin
If you can't wait, the TECkit mapping will work regardless of your XeTeX version. On Tue, Jan 15, 2013 at 10:24 AM, Khaled Hosny wrote: > On Tue, Jan 15, 2013 at 09:13:12AM -0500, Mike Maxwell wrote: > > On 1/15/2013 12:58 AM, Khaled Hosny wrote: > > >BTW, next XeTeX (thanks the new HarfBuzz lay

Re: [XeTeX] redefining Unicode characters

2013-01-15 Thread Martin Schröder
2013/1/15 Khaled Hosny : > We don't usually make separate releases, so, unless you are welling to > build from git[1], the answer is yes. There's always tlcontrib. :-) Best Martin -- Subscriptions, Archive, and List information, etc.: http://

Re: [XeTeX] redefining Unicode characters

2013-01-15 Thread Khaled Hosny
On Tue, Jan 15, 2013 at 09:13:12AM -0500, Mike Maxwell wrote: > On 1/15/2013 12:58 AM, Khaled Hosny wrote: > >BTW, next XeTeX (thanks the new HarfBuzz layout engine), will try to > >position the accents using their bounding boxes if the font does not > >have a GPOS table, so it should produce bette

Re: [XeTeX] redefining Unicode characters

2013-01-15 Thread Mike Maxwell
On 1/15/2013 12:58 AM, Khaled Hosny wrote: BTW, next XeTeX (thanks the new HarfBuzz layout engine), will try to position the accents using their bounding boxes if the font does not have a GPOS table, so it should produce better results in this case (unless the font in question does have a GPOS ta