Am Freitag, den 18.07.2014, 21:00 + schrieb Karl Berry:
I hadn't realized that the ligatures only failed with non-fully-embedded
PDF's. Such PDF's are inherently defective; it's been a long time since
Adobe recommended anything but full embedding (not that I think we must
kowtow to
On Mon, 21 Jul 2014, Fabian Greffrath wrote:
especially in the academic field. It would be a shame if the FOSS stack
could not render them correctly because of some technical details. And
in this specific case the ad-hoc fix would be a trivial fix in the font
files.
Until the next font
Am Donnerstag, den 17.07.2014, 20:57 -0400 schrieb James Cloos:
A patch has at least been proposed for poppler to treat glyph names like
/f_i as equivilent to names like /fi, at least for the f-ligs found in
the standard pdf font encodings for the base14 fonts.
I am still convinced (and as
On 7/18/2014 1:35 PM, Fabian Greffrath wrote:
Am Donnerstag, den 17.07.2014, 20:57 -0400 schrieb James Cloos:
A patch has at least been proposed for poppler to treat glyph names like
/f_i as equivilent to names like /fi, at least for the f-ligs found in
the standard pdf font encodings for the
HH == Hans Hagen pra...@wxs.nl writes:
HH if dropping in otf files for type 1 ones is considered a valid
HH solution, then poppler should do more checking anyway for the few f
HH related ligatures (which makes me wonder why the otf file is used as
HH drop-in)
Poppler asks fontconfig for a font
as far as I understand it seems that at least Karl Berry agrees in
that regard)
I hadn't realized that the ligatures only failed with non-fully-embedded
PDF's. Such PDF's are inherently defective; it's been a long time since
Adobe recommended anything but full embedding (not that I think
HH == Hans Hagen pra...@wxs.nl writes:
HH As you mention in a previous mail, it's a bug in poppler (or maybe
HH some library it uses) that somehow used glyph names.
The bug shows up when the pdf file does not embed the font, forcing
viewers and renderers to find a substitute font.
A patch has
Hello again,
Am Mittwoch, den 02.07.2014, 16:32 +0200 schrieb Boguslaw Jackowski:
Having thought the matter over and having looked into TG Linux packages,
we would suggest to use, anyway, Type 1 TG as legacy fonts and to change
appropriately the content of packages -- and maybe names? ;-)
On 7/7/2014 10:08 AM, Fabian Greffrath wrote:
Isn't Times one of the fonts that are by definition of the PDF standard
explicitely not required to get embedded?
Those 7+bit times of a default minimal set of 15 fonts (these were
embedded in printers which at some point made sense due to
FWIW, I don't see how adding ff and the like to the OT fonts simply as
independent glyphs for rendering, not related to any OT or Unicode
ligature mechanism, could confuse anything.
I agree the real bug is in poppler (and/or Debian's choice of using
these OT fonts without sufficient testing), but
On 7/2/2014 4:32 PM, Boguslaw Jackowski wrote:
Hans:
I think even the type1 texgyre isn't by definition metric compatible.
Metric compatibility was one of the major targets of the TeX Gyre project.
Sure, definitely for the type1s, but also that for opentype we would not
be strict (one
Fabian:
they are not installed by default, that is. But once they are installed,
they take precedence.
OK, we took a shortcut. :-)
Incidentally, Debian/Ubuntu distribution ofers either tex-gyre or
fonts-texgyre packages, the former containing fonts in the Type 1
format, the latter -- fonts
Am Dienstag, den 01.07.2014, 08:08 +0900 schrieb Norbert Preining:
or adding another fake glyph fi/f_i,
Yes, please. This sounds like the best compromise: It retains backward
and forward compatibility, should be trivial to implement and should be
safe for future changes that poppler (or any
On 7/1/2014 1:40 PM, Fabian Greffrath wrote:
Am Dienstag, den 01.07.2014, 08:08 +0900 schrieb Norbert Preining:
or adding another fake glyph fi/f_i,
Yes, please. This sounds like the best compromise: It retains backward
and forward compatibility, should be trivial to implement and should be
On Tue, Jul 1, 2014 at 2:13 PM, Hans Hagen pra...@wxs.nl wrote:
The pdf file has then this mapping with fi being named f_i and not fi (why
should it) and also carries a tounicode which maps the 1 to unicode e and
2 to unicodes f followed by i. The reference to ff never ends up in the
subsetted
On 7/1/2014 6:12 PM, Ralf Stubner wrote:
On Tue, Jul 1, 2014 at 2:13 PM, Hans Hagen pra...@wxs.nl wrote:
The pdf file has then this mapping with fi being named f_i and not fi (why
should it) and also carries a tounicode which maps the 1 to unicode e and
2 to unicodes f followed by i. The
Hi Norbert,
Am Samstag, den 28.06.2014, 15:28 +0900 schrieb Norbert Preining:
Thanks, I forwarded this to the poppler group - I am not very
optimistic that they will do anything in this direction, but
we should try at least ;-)
whom do you mean with the poppler group? I couldn't find any
On Mon, 30 Jun 2014, Fabian Greffrath wrote:
whom do you mean with the poppler group? I couldn't find any message
I reassigned
https://bugs.freedesktop.org/show_bug.cgi?id=73291
to poppler (after some ping pong beteen fontcnfig and poppler)
and mentioned the AGL Specification.
Norbert
Am Montag, den 30.06.2014, 17:03 +0900 schrieb Norbert Preining:
I reassigned
https://bugs.freedesktop.org/show_bug.cgi?id=73291
to poppler (after some ping pong beteen fontcnfig and poppler)
and mentioned the AGL Specification.
Ah, I see. I have added the other bug to the See Also
Norbert:
here at Debian recently a problem surfaced with respect to the
OpenType TeX Gyre fonts.
The problem is that the ligatures are named
f_i
etc while display engines like poppler, as well as the orginal
PostScript fonts, use
fi
etc.
In Debian and Ubuntu, currently the TeX
On 6/30/2014 1:15 PM, Boguslaw Jackowski wrote:
Norbert:
here at Debian recently a problem surfaced with respect to the
OpenType TeX Gyre fonts.
The problem is that the ligatures are named
f_i
etc while display engines like poppler, as well as the orginal
PostScript fonts, use
fi
etc.
Dear friends,
Am Montag, den 30.06.2014, 13:15 +0200 schrieb Boguslaw Jackowski:
we are more than happy that the TeX Gyre collection
of fonts has been have been chosen as a default
font set in Debian distribution. And we are
they are not installed by default, that is. But once they are
revert to the old-style names in the OTF
Seems like there should be no need to revert. In principle, couldn't
the fi ligature glyph appear as both f_i and fi? In other words,
add a bunch more duplicate glyphs; nothing else need change, as I
understand it ... f + i would still lead to f_i,
On Mon, 30 Jun 2014, Hans Hagen wrote:
btw, If I grep my afm files for f_f and f_l I get lots of hits on
linotype fonts like palatino-nova, aldus-nova, palatinosans* so
there are type one fonts out there that use _ too.
Interestingly I cannot trigger the bug with xelatex and Palatino Sans,
for
On Mon, 30 Jun 2014, Karl Berry wrote:
revert to the old-style names in the OTF
Seems like there should be no need to revert. In principle, couldn't
Agreed, reverting is bad.
the fi ligature glyph appear as both f_i and fi? In other words,
That would be the safest option, indeed.
Dear Jacko,
thanks for your answer and time
The fonts in the OTF format, however, we considered new ones
(note, e.g., that they have Unicode tables and that they are equipped
with the OTF typografic features, both absent from the original
Adobe fonts) and, therefore, following Adobe's
On 7/1/2014 1:05 AM, Norbert Preining wrote:
On Mon, 30 Jun 2014, Hans Hagen wrote:
btw, If I grep my afm files for f_f and f_l I get lots of hits on
linotype fonts like palatino-nova, aldus-nova, palatinosans* so
there are type one fonts out there that use _ too.
Interestingly I cannot
On Fri, 27 Jun 2014, Karl Berry wrote:
See section 6 (or search for ligature) in
http://sourceforge.net/adobe/aglfn/wiki/AGL%20Specification
Thanks, I forwarded this to the poppler group - I am not very
optimistic that they will do anything in this direction, but
we should try at least ;-)
The problem is that the ligatures are named
f_i
Adobe wants it that way these days, as I understand it. (Personally I
think they were terribly wrong to try to change something so fundamental
but, surprisingly, they didn't ask me. :)
See section 6 (or search for ligature) in
Dear good friends from Poland,
here at Debian recently a problem surfaced with respect to the
OpenType TeX Gyre fonts.
The problem is that the ligatures are named
f_i
etc while display engines like poppler, as well as the orginal
PostScript fonts, use
fi
etc.
In Debian and
30 matches
Mail list logo
