cupsaddsmb supports windows nt?

[Helge Blischke]

Michael Sweet wrote:
> 
> Christoph Litauer wrote:
> > ...
> > thanks for your response. I don't agree with your statement. I can use
> > the Adobe Postscript driver for NT, 2000 and XP without problems. But
> 
> Actually, the Adobe driver which works with NT is also a kernel mode
> driver, which is what we are moving away from.  The current Adobe
> driver for Windows 2000 and higher is, in fact, the one that comes
> with Windows, and that is the one we support.  You can still use the
> cupsaddsmb program from 1.1.20 and earlier to export the Adobe NT
> drivers, but you can't export both the NT and 2000 drivers on the
> same Samba server.
> 
> > cupsaddsmb doesn't support installing the adobe drivers any more. So I
> > have to write my own cupsaddsmb script - its not difficult at all, but I
> > would prefer an option to cupsaddsmb that lets the user decide which
> > drivers should be installed.
> 
> Given that the old drivers are buggy, generally unsafe to use on
> newer systems, and you can't export both NT and 2000 drivers on the
> same server (only an NT driver which happens to work on later
> versions of Windows), we have no plans or desire to implement such
> a feature.
> 
> You can probably combine the 1.1.20 and 1.1.21 versions of cupsaddsmb
> to get "the best of both worlds" for your configuration.
> 

Just a footnote to this thread:
The old NT4 kernel mode driver is the only one that (still) handles
Type1 fonts
that use glyph names outside the range of WinAnsi (or whatever Win XP,
2000, 2003
think are valid glyph names) correctly. The user mode driver tries to
substitute
these glyphs by "bullet", which usually isn't present in these fonts.
Thus only
..notdefs are printed (usually as white space).

As Adobe claims this driver be a joint effort of Adobe and Microsoft, I
think it is
remarkable that a lot of Type1 fonts sold by Adobe (e.g. the TimesTemCyr
family
and a lot of Pi fonts) are subject to this bug.

Thus, as long as it works, we will stick to the NT4 driver and, in the
long run,
look for a workaround that will transfer the EMF files to the spooler
and develop
a emftops filter for CUPS.

Helge


-- 
Helge Blischke
Softwareentwicklung
SRZ Berlin | Firmengruppe besscom
http://www.srz.de