Re: [TCLCORE] canvas 'postscript' command

[Jan N. <jan...@gm...>]

2008/12/14 Alexandre Ferrieux <ale...@gm...>:
> Why ? The example given was FreeSans -> Freesans; so if we first
> retokenize "FreeSans" as "Free Sans" it does the job.

Currently, three things are done:
1) capitalize first character of each word
2) lowercase all other characters of each word
3) remove spaces

Operation 2) is the one causing trouble. I would suggest leaving out this,
just keeping things as equal as current as possible.
This means that
   "Foo Bar BooBoo tWiNkIe" -> "FooBarBoobooTwinkie"
will change to:
   "Foo Bar BooBoo tWiNkIe" -> "FooBarBooBooTWiNkIe"
That's still a valid Postscript name.

At the time, postscript was invent, truetype didn't exist any more.
Nowadays, ttf fonts can used by both screens and printers, so
any valid ttf font name which can also be a valid postscript font
name (== first character capital, containing no spaces) should
be unchanged. I don't know any problems that would create.

Anyway, it is useful to create a (Tktoolkit) bug report for this,
now that TrueType fonts are more common we can expect
such kind of question more often.

I know that comp.lang.tcl is more appropriate for this question,
but in this case it's really strange behavior. I would propose
removing lines 1703 and 1704 from tkFont.c, provided no-one
comes up with an example where this causes problems. And
even if it causes a problem in some situation, that can be
solved with the -fontmap option. Food for more thought.

Regards,
         Jan Nijtmans