Encoding of Scala Sans expert set

marcokuhlmann's picture

Hi all,

I am currently trying to make FF ScalaSans available for LaTeX. To do so, I need to know the encoding vectors of the various fonts. While all fonts with the standard glyph set have been encoded using Adobe StandardEncoding, the expert set is different. Therefore, I was trying to get the encoding vector that was used for the expert sets. I contacted FontFont about this, but they replied that I would have to reconstruct the encoding myself, as it differs among their fonts, and they do not have one single encoding vector available to send me.

Does anybody happen to have such an encoding table for FF ScalaSans? I have googled for this, but did not find anything.

Thanks a lot,

chanop's picture

Hi Marco,

I assume that you are using fontinstall for the task. If that's the way, then the easiest way to do is hacking afm files. My suggestion is to hack afm file such that it reflects the true name for each glyph in your font -- at the same location, of course.

For example, GalliardExpertCC-italic has glyph `ff' encoded at location 86 (`v' in 8r encoding); in this case, I would hack afm such that at position 86, it says `ff' instead of `v'.

Usually expert fonts contain less than 256 characters, therefore, you do not need to re-encode the font. You only need to tell TeX(fontinstall) to pull the right character from the right slot which is easy enough by hacking afm files.

You can always fire up a fonteditor and fix the encoding yourself.


marcokuhlmann's picture

Thanks, Stephen and Chanop, for your answers.

Stephen: I have in the meantime contacted Volker Rosenfelder, and it seems that he is able to help me. Thanks a lot!

Chanop: Yes, I am actually planning to use fontinst for this task. I expect no problem in writing the relevant MTS-files (or even, as you suggested, hacking the AFM files), as soon as I know what glyph lives where in ScalaSans Expert. Firing up a font editor to construct that encoding myself is, of course, always an option. I only thought that other people might already have that information, so that I would not have to redo it myself. After all, that's what font encodings are for. :-)


Stephen Coles's picture

FontShop should be able to help you out with any sort of
encoding information. If you contact Volker Rosenfelder via
email (see private message) I'm sure he can assist you.

Syndicate content Syndicate content