Subject: Re: [netatalk-admins] CRLF
From: Gerry.Tomlinson (Gerry.Tomlinson@newcastle.ac.uk)
Date: Thu Jun 25 1998 - 04:47:08 EDT
>
> An experience that is worth sharing:
>
> When first installing netatalk, I had a long talk with myself deciding
> whether or not to activate eol-translation (-DCRLF in afpd Makefile). I
> found no convincing reason to choose one or the other. Both seemed to have
> advantages and disadvantages, but none definite. There is no real problem
> when you use a text editor that deals with different file system standards
> transparently, like BBEdit, and will not put "anonymous" binaries on the
> server to be used by a Mac.
> I decided to enable translation, because it was the default in the package.
>
> Now I have a definite reason why it should _not_ be enabled: pdf files.
> Adobe Acrobat pdf files have TEXT/CARO as file type and creator, and get
> translated. But the format doesn't allow that: opening valid pdf files from
> a netatalk server with eol-translation enabled shows blank documents.
> So I advise you to disable the eol-translation, and advise distributionists
> to change the default.
>
The type should not be TEXT. The Distiller produces pdf files with
type/creator PDF /CARO.
Gerry
--- Gerry.Tomlinson@newcastle.ac.uk Computing Officer Department of Computing Science, University of Newcastle, Tel: +44 191 222 8139 Newcastle upon Tyne, NE1 7RU, United Kingdom. Fax: +44 191 222 8232
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:32:50 EST