At 02:04 PM 3/12/2003 +0100, you wrote:
It is clearer: the first bit gives the encoding and the latter bit is the name of the file containign the glyphs (uplr8a.pfb). OTOH since LaTeX already creates a lot of font-mess, I do agree that there is no need to add more to the trouble already there. I would like to see a few sym-links (does Windows have something like that?) to add a few names to the tree to make sure everything works as planned.
the tricky part is in slanted, extended and caps'd fonts, where there is no distinction between instances in psfnss, which is why context has more verbose names; also, most of the fonts we use here (in projects) are not free, not in the texmf tree, and i have no time (or spirit) to sort out how they should be reduced to 2+2+2+2 char names; so, this iw why the berry typescripts permit you to use the rare texmf-tree names, while additional fonts can follow the more verbose scheme (unless of course one sorts out the funny short name and names the fonts manually). Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------