[Textures] Textures 2.2.0b17

[Bruno Voisin]

Le 6 avr. 2011 à 00:20, Paolo Matteucci a écrit :

> perhaps more strikingly,
> the European Modern PS fonts, say, emr12 and emti12 (PS names EMR12
> and EMTI12, respectively) *both* have "TeX typewriter and Windows
> ANSI" as their "PS fontnames" (!), which to me just seems a
> consequence of having chosen "TeXnANSI" as their "encoding"… Any
> ideas?

Are you sure? This isn't what I'm getting. Typesetting testem.tex from the Y&Y TeX repository, which uses emr8/10, emmi8/10, cmsy10 and cmex10, here's what I'm getting with a TrueType version of the EM fonts:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Capture d??cran 2011-04-06 ? 07.46.43.png
Type: image/png
Size: 84285 bytes
Desc: not available
URL: <http://email.esm.psu.edu/pipermail/textures/attachments/20110406/1a917d3c/attachment.png>
-------------- next part --------------


and with a FFIL/LWFN version:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Capture d??cran 2011-04-06 ? 07.55.41.png
Type: image/png
Size: 86984 bytes
Desc: not available
URL: <http://email.esm.psu.edu/pipermail/textures/attachments/20110406/1a917d3c/attachment-0001.png>
-------------- next part --------------


(for CM it's a TrueType version prepared as per my preceding messages).

In both cases the TeX Metrics window yields

name		PS fontname		encoding

cmex10		PS CMEX10
cmsy10		PS CMSY10
emmi10		PS EMMI10
emmi8		PS EMMI8
emr10		EMR10			TeXnANSI
emr8		EMR10			TeXnANSI

so it seems that when there's an encoding the PS font name is used as is, and when there's no encoding it's prefixed by "PS ".

That said, there are still strange things happening: I've no idea why in the second screenshot cmsy10 is given "LCMSSI8" ATS family. Clearly, there are still bugs in the TeX Metrics window. I've no idea why they show up differently in your case.

A case also when I'm seeing incorrect PS fontnames is virtual fonts, like ec-hoefler-HoeflerText getting PS fontname "ECEncoding" in the screenshot below. (There should be no PS fontname for virtual fonts.)

Selecting the PostScript font column as above moves all the fonts used in the viewed pages of the current document to the top of the TeX Metrics window (it's an undocumented trick which I owe to Blue Sky tech support).

>> …there are mechanisms for arbitrary encodings
> 
> Which ones? EdMetrics? :-?

You can paste an encoding directly in the encoding column. To be on the safe side, erase beforehand all text before the opening bracket "[" of the encoding and after the closing bracket "]", together with any comment. Like this:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Capture d??cran 2011-04-06 ? 08.16.30.png
Type: image/png
Size: 415767 bytes
Desc: not available
URL: <http://email.esm.psu.edu/pipermail/textures/attachments/20110406/1a917d3c/attachment-0002.png>
-------------- next part --------------


I think that Textures can now use encodings with comments, but I've not tried.

What I'm curious about is whether 2.2.0b17 can accept encodings with underscores (like /f_f). 2.2.0b16 couldn't. This would allow getting the ff ligature with HoeflerText in GTA Mac Fonts, for example. Probably I should just try.

Bruno