[NTG-pdftex] Re: [tex-k] Dvips fix for font in EPSF improperly downloaded

...

...

...

...

"Karl" == Karl Berry writes:

I agree a warning may be appropriate whenever a font is included in its entirety.

May I suggest a modification: whenever a *proprietary* font (that is, one with the restrictive licensing) is included.

It's probably too hard to find out which font is proprietary.

It would be quite a lot of noise to generate a warning for every fully-included font, as most commonly-used fonts in the TeX world are free. Seems like any "real" warning regarding problematic fonts would quickly be lost in the swamp of resulting messages.

dvips already lists all fonts on STDOUT, isn't it sufficient to put an asterisk behind each font that had been loaded entirely and then issue a message like "*) Some Fonts had not been subsetted" at the end if at least one asterisk appears? The message is just an example. It should be understood by people who do not know what subsetting is. But English is not my native language, feel free to provide better suggestions. Hans, is this ok for you? Or is it still too crappy?

The only thing I can think of is some kind of additional map file option (ugggh) to generate the warning. Then when people (like Walter) generate TeX support for proprietary fonts, the pregenerated map files can specify the new option.

I don't see that there is any need to change the map files. Usually there is no need to download an entire font. The map files provided by TeX distributions are set up to do subsetting by default. My only concern is that people rely on this and do not notice that they violate against licenses because something happens in the background they are not aware of.

Further: any changes to map file syntax should be coordinated with pdftex and dvipdf[m][x], as another long-term goal should be to re-unify map files so that the same syntax can be used for all programs. It is a hassle for TeX Live and other distributions to have maintain the same information in three formats with only tiny differences.

Of course.

Also, I'm not sure if this is already included in the discussion, but any such warning should presumably apply when the font is fully downloaded at all, independent of whether that happens due to an .eps inclusion or simply using the font in the document.

Sounds quite straightforward: An asterisk for each font which is included entirely, independent of the map file entry.

At this time he was thinking about changing /FontName in the free URW fonts on CTAN

I sincerely hope Walter does not do that. Seems like it would have major backward-compatibility implications.

No, he didn't. It was an idea which came up during the conference dinner, but he changed his mind quite soon. I just metioned it to show that I'm not the only one who sees problems here. Karl, if anyone changes some font names, I suppose you are the first one who will notice this because he will ask you to update the fontname database you maintain. Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-4592165 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha@web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ----------------------------------------------------------------------------