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 i
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
docu
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 macro
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 6,
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 mac
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
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 (
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 wrote:
> Since as far as I've seen no one has responded to you
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 there,