a.bokovoy at sam-solutions.net
Mon Apr 21 07:11:00 GMT 2003
On Sun, Apr 20, 2003 at 11:58:19PM -0700, Andrew Morgan wrote:
> On Mon, 21 Apr 2003, Alexander Bokovoy wrote:
> > On Fri, Apr 18, 2003 at 12:16:51AM +0900, TAKAHASHI Motonobu wrote:
> > > On Thu, 17 Apr 2003, Malte Weber wrote:
> > > > My problem is locale-based, as I have moved the files formerly located
> > > > on one of the mac's on the netatalk server, the umlauts and special
> > > > characters are now in the ':AB'-hex-encoding used by netatalk, and I
> > > > have not yet managed to get those characters correctly displayed on the
> > > > windows clients. Could you tell me the settings you used for the
> > > > codepages etc. on netatalk & samba?
> > >
> > > Please use "coding system = CAP"
> > > This parameter is created mainly to manage Japanese filenames created
> > > by CAP or NetAtalk, but is probably useful for other codepages.
> > I have patches for Netatalk to support libiconv to the same degree as
> > Samba, if only somebody from Netatalk team would be interested to see them...
> > We have those patches for more than year now in production use, including
> > Japanese market.
> Have you posted a note about your patches to the netatalk-devel mailing
> list hosted at sourceforge? If you can't get the attention of another
> developer for apply your patches to CVS, I'll give you CVS access.
Probably we need to discuss patches first (I'm not subscribed to
netatalk-devel yet) because it makes changes only in translation component
while mangling part isn't updated yet. At best, it would probably be taken
from Samba to be fully compatible.
I'll return to the topic on netatalk-devel later this week, after updating
patches to current HEAD.
/ Alexander Bokovoy
Half Moon tonight. (At least it's better than no Moon at all.)
More information about the samba-technical