Peter Rolf skribis:
> donno exactly in which version of the pdf language object compression
> was introduced (1.4-1.5?). you can try to set
I think cross reference streams are 1.5, because this issue arose for
me with fontforge, which needed conventional xref.
>
> \pdfminorversion 4 % default
Hans Hagen skribis:
> so, its not that frac itself is the problem dealing with in the engine,
> because if so, many features would be a problem, it's just that font
> makers stick to a couple of simple rules like:
>
> (1) replace all
>
> by
>
>
> (1) replace all
>
Barry Schwartz skribis:
> In practice what I see with my method is that discretionary hyphens
> always get an ActualText, and if the font is older and has names like
> "Asmall" or "ffl" (which I don't bother handling specially) then the
> substituted stuff ge
Hans Hagen skribis:
> > put an ActualText tag on anything that happens not to match what you
> > would get from the ToUnicode mapping.
>
> hm, if one knows the character (say c) then why not adapt the tounicode
> vector
The same glyph could correspond to different Unicode in the
source. This is
Arthur Reutenauer skribis:
> He means "ActualText tags" :-) See the PDF spec section 14.9.4, page 623.
> It's a more generic way to support searching than ToUnicode vectors: you just
> specify the actual string of underlying Unicode characters. The PDF spec uses
> hyphenated "ck" in German as
Please tell me this isn't in a FAQ. :) Is there support for ActualText
tags so that searching and extraction will work with OpenType fonts
and Unicode? If so, do discretionary hyphens get treated as 00AD
instead of 002D?
_
Hans Hagen skribis:
> but even then, if a font is not clear about issues, then one can get
> unwanted side effects (the frac feature for instance is often quite
> bugged and can only be applied selectively)
Yeah, I think trying to be fancy with contextual substitutions is a
bit like getting dru
Hans Hagen skribis:
> Barry Schwartz wrote:
>
> > If base mode uses the traditional TeX mechanism for ligatures, I don't
> > see any way the font can be blamed.
Ant does the same thing, I believe, using the OT tables and heuristics
to run the TeX processor. That's
Derek CORDEIRO skribis:
> On Fri, Sep 18, 2009 at 11:24 PM, Hans Hagen wrote:
>
> > Derek CORDEIRO wrote:
> >
> > That does not work for me at all. The following does work with generating
> >> the same ThOMAS
> >>
> >
> > can you try ..
> >
> > \definefontfeature[smallcaps][smallcaps][liga=no]
Hans Hagen skribis:
> Barry Schwartz wrote:
> > Hans Hagen skribis:
> >> could it be a bug in the font? i.e. a Th ligature showing up in
> >> smallcaps? if so, then simplefonts should disable ligatures in smallcaps
> >
> > I'm looking at AGaramondPr
Hans Hagen skribis:
> could it be a bug in the font? i.e. a Th ligature showing up in
> smallcaps? if so, then simplefonts should disable ligatures in smallcaps
I'm looking at AGaramondPro-Regular in fontforge and it has the lookup
for small caps well above the lookup for ligatures. The software
11 matches
Mail list logo
