Re: [TCLCORE] canvas 'postscript' command

[Jan N. <nij...@us...>]

At first sight, this sounds like a bug. I don't know if it is worth to
fix it, because there is a workaround, but it is useful to file
a bug report anyway. Then maybe more people can comment
on it, you can follow the eventual fix, and more people can
put comments there.

2008/12/13 T. Horsnell <ts...@mr...>:
> The FreeSans from the script has been changed to Freesans in the
> postscript file and Ghostscript cant then find the font.

The .c postscript command has an option -fontmap. According to
the manual (see below), Tk's guessing only works for well-known
fonts. Currently (at least since Tk 8.1), Tk capitalizes the first
character and changes all others to lowercase in this case. Your
problem might be a good excuse to change that behavior. Maybe
others can provide more ideas? Anyone else has an idea what's
the reason to change all other characters to lowercase? It's
easy to change that in the core, but I don't know what other
effects that would have.......

Regards,
            Jan Nijtmans

=================================================
-fontmap varName
VarName must be the name of an array variable that specifies a font
mapping to use in
the Postscript. Each element of varName must consist of a Tcl list
with two elements,
which are the name and point size of a Postscript font. When
outputting Postscript
commands for a particular font, Tk checks to see if varName contains
an element with
the same name as the font. If there is such an element, then the font
information
contained in that element is used in the Postscript. Otherwise Tk
attempts to guess
what Postscript font to use. Tk's guesses generally only work for
well-known fonts
such as Times and Helvetica and Courier, and only if the X font name
does not omit
any dashes up through the point size. For example,
-*-Courier-Bold-R-Normal--*-120-*
will work but *Courier-Bold-R-Normal*120* will not; Tk needs the
dashes to parse the font name).