Re: [XeTeX] Trouble with the new Xetex

2011-11-06 Thread Peter Dyballa
Am 06.11.2011 um 02:15 schrieb Andrew Gollan: The Invalid glyph is actually the result of a \=V in one place, but the \=y is being printed as a spiral in the PDF if that is remove V with macron does not exist in Unicode (but U with macron does, so it looks bad, until you invent a good macro

Re: [XeTeX] Trouble with the new Xetex

2011-11-06 Thread Peter Baker
Cardo now has a very nice italic face. You'll also find y+macron in the DejaVu fonts. Oh, and if you look up the Medieval Unicode Font Initiative page, you'll find others listed, since all MUFI-compliant fonts are supposed to have that character. Peter S. Baker University of Virginia On Nov

Re: [XeTeX] Trouble with the new Xetex

2011-11-06 Thread Peter Dyballa
Am 06.11.2011 um 12:41 schrieb Andrew Gollan: It used to work. Yes! I too remember that I could typeset documents in Palatino Linotype with XeLaTeX. Actually I still can! Sorry, I'm a bit busy with other things today… But what I've found is that your use of composed characters with

Re: [XeTeX] Trouble with the new Xetex

2011-11-06 Thread Andrew Gollan
All this makes sense, except the regression. It used to work. The code that made it work has been either removed or broken. Is this not a bug? I don't want to have to restrict my choice of fonts when code exists/existed to seamlessly give me what I used to have. Surely this is regressing many

Re: [XeTeX] Trouble with the new Xetex

2011-11-06 Thread Heiko Oberdiek
On Sun, Nov 06, 2011 at 11:37:08AM +0100, Peter Dyballa wrote: Am 06.11.2011 um 02:15 schrieb Andrew Gollan: The Invalid glyph is actually the result of a \=V in one place, but the \=y is being printed as a spiral in the PDF if that is remove V with macron does not exist in Unicode

Re: [XeTeX] Trouble with the new Xetex

2011-08-14 Thread Ulrike Fischer
Am Sat, 13 Aug 2011 19:56:33 +0200 schrieb Mojca Miklavec: My guess is that it used to use the combining diacritic with the y, and now it only looks for the precomposed character. I'm not sure how you'd go about solving your problem though. I don't know the details, but I also think that

Re: [XeTeX] Trouble with the new Xetex

2011-08-13 Thread John McChesney-Young
Since as far as I've seen no one has responded to your question (and I have no idea of an answer myself), I thought I'd ask whether there's some feature of Palatino Linotype that makes it so appealing you don't want to switch to a font that includes the character? There are a lot of them out

Re: [XeTeX] Trouble with the new Xetex

2011-08-13 Thread Andy Lin
My guess is that it used to use the combining diacritic with the y, and now it only looks for the precomposed character. I'm not sure how you'd go about solving your problem though. On Sat, Aug 13, 2011 at 12:51, John McChesney-Young jmccyo...@gmail.com wrote: Since as far as I've seen no one

Re: [XeTeX] Trouble with the new Xetex

2011-08-13 Thread Mojca Miklavec
On Sat, Aug 13, 2011 at 19:33, Andy Lin wrote: My guess is that it used to use the combining diacritic with the y, and now it only looks for the precomposed character. I'm not sure how you'd go about solving your problem though. I don't know the details, but I also think that one package A

[XeTeX] Trouble with the new Xetex

2011-08-11 Thread Andrew Gollan
I am using the Palatino Linotype font which does not have a native ȳ glyph. I had been entering my ȳ letters as \=y which was working fine until I upgraded to TeXLive2011 (from 2009/2010 depending on machine). Now I get the error message: ** ERROR ** Invalid glyph index (gid 1329) Output file