Subject: Japanese filename support? [REPOST]
From: Steve Frampton (frampton@j-com.co.jp)
Date: Thu Mar 23 2000 - 19:13:40 EST
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello:
Since nobody responded to this (aside from a couple of e-mails saying, "I
have experienced the same problem" or "It's a known issue"), I'd like to
ask again if any work is being done to handle alternate character sets
(such as Japanese), or if any workarounds exist.
On Sat, 18 Mar 2000, Steve Frampton wrote:
> I've set up a Linux-based file and print server for a rather large
> Japanese office. The Windows clients are using Samba, which has been
> configured with:
>
> client code page = 932
> codingsystem = EUC
>
> This maps the Microsoft JIS character encoding to a more Unix-friendly EUC
> format. The Japanese and English filenames appear properly whether viewed
> with Windows file manager, or from the Linux console with kterm or kon.
>
> I've also set up Netatalk so the Mac clients can have access to these same
> files. However, while they are able to access English file names, when
> they try to access the Japanese filenames, they get an error. In
> addition, the filenames as viewed from the Mac appear as gibberish.
>
> Just wondering if Netatalk had support for other character encoding
> schemes, and if so, what options would enable them.
- --------------< LINUX: The choice of a GNU generation. >--------------
Steve Frampton <frampton@j-com.co.jp> Japan Communications, Inc.
Software Developer/Systems Administrator http://www.j-com.co.jp/
GNU Privacy Guard ID: D055EBC5 (see http://www.gnupg.org for details)
GNU-PG Fingerprint: EEFB F03D 29B6 07E8 AF73 EF6A 9A72 F1F5 D055 EBC5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE42rM4mnLx9dBV68URApY0AJ9Dq97c8SET49V1jh8frbWNqfVLmwCeIWWf
IbLLUEjBc3lw6hyhOodSoC4=
=8KRz
-----END PGP SIGNATURE-----
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:30:17 EST