Hi
Development repository of bidi package is changed to
http://puszcza.gnu.org.ua/projects/bidi/
(thanks to Karl Berry for suggesting http://puszcza.gnu.org.ua)
I expect all bug reported to go there.
Thanks
--
Subscriptions, Archive, and List in
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
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 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
Le 31/10/2011 19:47, Alessandro Ceschini a écrit :
Hi
My problem is kind of complicated:
1. After processing a XeLaTeX source file the yellow lines the
cross-reference between pdf and source file and vice versa is
completely broken.
2. This happens after I updated to Ubuntu 11.10, TexLive 201
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
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
I don't use Ubuntu, but if you have both TL2010 and 2011, I'd check
the directories that are in fontconfig (or run fc-cache -v and see
which directories it's looking in). It may be that fontspec is
complaining because it finds duplicate sets of fonts between the two
installations. Your PDFs would b
To Andy:
Hi
No, I only have TL2011 and nothing of the bundled version (2009) is
installed, and no, there's no duplicate of the font, actually this
happens with every font, it's a bit weird for every font to be
duplicated. The directories are the standard ones: \usr\share\fonts and
~\.fonts\
Hi Heiko, and Akira,
On 06/11/2011, at 3:55 AM, Heiko Oberdiek wrote:
> \special{%
> pdf:ann width 4bp height 2bp depth 2bp<<%
> /Type/Annot%
> /foo/ab#abc
> /Subtype/Link%
> /Border[0 0 1]%
> /C[0 0 1]% blue border
> /A<<%
Hmm, according to that ticket on the texwork site, someone else has
the same problem, so it doesn't seem to be something unique to your
set up. I'm surprised that it's SyncTeX that's the culprit, since the
project page hasn't been updated since 2008, unless it's moved.
Unfortunately, I can't help
11 matches
Mail list logo