[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#527863: marked as done (Linux Libertine 4.4.1 Bold ligature fi breaks XeTeX)

Your message dated Wed, 2 Sep 2009 01:12:58 +0200
with message-id <20090901231258.GA10317@aldebaran.xn--kwg.net>
and subject line Re: Bug#527863: Linux Libertine -- Works for me
has caused the Debian Bug report #527863,
regarding Linux Libertine 4.4.1 Bold ligature fi breaks XeTeX
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

527863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527863
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: ttf-linux-libertine
Version: 4.4.1-1

The ttf-linux-libertine package was recently upgraded from 4.1.8-1 to
4.4.1-1; something in the changes brought by this upgrade has broken
XeTeX's ability to use "fi" ligature in the bold version of the font.

A minimal example showing the problem is this:

vega david /tmp $ cat breakage0.tex
\font\thefont="Linux Libertine Bold"
\thefont fi

With Debian's current version of texlive-xetex (2007.dfsg.2-6), this
produces the following diagnostic (the warning part about the .map
file is irrelevant to the problem being discussed; the bad thing is
the bit about "Output file removed"):

vega david /tmp $ xetex breakage0   
This is XeTeXk, Version 3.141592-2.2-0.996-patch2 (Web2C 7.5.6)
 %&-line parsing enabled.
entering extended mode
(./breakage0.tex [1] )

** WARNING ** This .map file looks like a dvips format fontmap file.
** WARNING ** -- Current input buffer is: ASCII ASCII <ASCII.pfb
** WARNING ** -- Reading fontmap file stopped at: file="pdftex.map", line=6.

Output file removed.
Output written on breakage0.pdf (1 page).
Transcript written on breakage0.log.

(Indeed, no output file is produced.)  With a more recent version of
XeTeX than Debian's, the error is slightly more verbose, although
still unilluminating:

vega david /tmp $ xetex breakage0
This is XeTeXk, Version 3.1415926-2.2-0.999.2 (Web2C 7.5.7)
 %&-line parsing enabled.
entering extended mode
(./breakage0.tex [1]
** WARNING ** No Unicode mapping available: GID=2306, name=(none)
** WARNING ** Unable to read OpenType/TrueType Unicode cmap table.
** WARNING ** Failed to load ToUnicode CMap for font "LinLibertineB"
** ERROR ** Invalid glyph index (gid 2306)

Output file removed.
Error 256 (driver return code) generating output;
file breakage0.pdf may not be valid.
Transcript written on breakage0.log.

If "fo" (say) is used instead of "fi", or if "Linux Libertine" is used
instead of "Linux Libertine Bold", or if the font is downgraded to
4.4.1-1, then a correct output file is produced.

I lack the sufficient expertise to determine whether the problem lies
in the font or in XeTeX, but since XeTeX is one of the main targets
for use of the font, I'm reporting on ttf-linux-libertine so that the
maintainer can examine whether s/he can find anything remotely

I have been unable to find any difference in the bold "fi" ligature
between versions 4.1.8-1 and 4.4.1-1.  Nor do I know what "gid 2306"
is about (gid is "glyph ID", I suspect, but what is that number

     David A. Madore
   ( http://www.madore.org/~david/ )

--- End Message ---
--- Begin Message ---
Version: 4.4.1-3

On Tue, Sep 01, 2009 at 05:06:44PM +0200, Christoph Egger wrote:
> 	As you can see in the output below I can invoke xetex just fine
> and the pdf looks like it contains the intended output. Maybee there
> are other factors relevant here? Any idea what I need to do to
> reproduce the issue?

It seems that the bug was fixed between 4.4.1-1 and 4.4.1-3 (I can
really make it appear and disappear by downgrading and upgrading
between those two versions, presently in testing and sid).  Looking at
the changelog, I can't begin to guess which change might have fixed
the problem, but I guess all is for the best.

> 	Btw: please consider using reportbug for your next bug
> report. This appends lots of usefull information to bugreports like
> localesettings and the version of all packages linux libertine depends
> on.

Thanks, I'll try to remember that this program exists!

     David A. Madore
   ( http://www.madore.org/~david/ )

--- End Message ---

Reply to: