The product is intended to be used (and is certainly tested) in an environment where the filer is accessed by many different language systems. Any limitations described here are limitations of the clients and protocols and are not limitations introduced by the filer.

The language setting is relevant in a cifs only environment since it controls how we generate 8.3 names, system, and domain names. For Win9x clients it will also be how we encode share names.

If setting the language is needed what impact does this have with multiple language clients, ie one kanji, one US English and maybe a laptop user from Korea?

In such a mixed, cifs-only environment I would set the language to "C", and use only ASCII strings for system and domain names. System and domain names are transmitted using the OEM character set selected by the language setting on the system volume. If you are using NT, then you are not restricted in the share names, but bear in mind that an English client installed with the normal fonts will not be able to display a Japanese share name correctly.

The filer supports non-ASCII system and domain names, but limitations on the clients effectively require that everyone agree on the language being used. For example if you use the name nihongo (in the correct Kanji) for your domain name, Japanese systems will correctly display the domain name. (We have such a domain in our development lab). English systems will see the name as a series of European characters since they cannot interpret the OEM character strings.

As long as you are using an NT backup program running on NT you should not have a problem. Win9x does not implement a full version of UNICODE so I would not expect it to work correctly there.

-----Original Message----- From: Alan R. White [mailto:arw@tipper.demon.co.uk] Sent: Monday, January 31, 2000 11:39 AM To: toasters@mathworks.com Cc: Andrew-M.Webster@db.com Subject: Re: Toasters in Compaq Racks and Unicode Files

Hi,

Sorry 'bout the bunch more questions below - I'd like to understand what this means in more detail if there's knowledgable folks out there.

Is unicode mode enabled automatically on the wafl fs? Is the language setting relevant in a CIFS only environment or is it only to allow translation between single-byte clients and wide charsets? If setting the language is needed what impact does this have with multiple language clients, ie one kanji, one US English and maybe a laptop user from Korea? Does it have any impact if the user consistently uses the same language/nt build on the client? How about backup/restore via CIFS - are we OK as long as the CIFS backup client understands unicode? Any idea on maximum filename lengths? The Win32 SDK says 32,000 unicode characters if prefixed with "\?" - anyone stress tested this?

Hope I get it with answers to all these questions - talk about opening pandoras box Andrew ;-)

TIA, Alan

----- Original Message ----- From: Joan Pearson jpearson@netapp.com To: Andrew-M.Webster@db.com Cc: toasters@mathworks.com Sent: Monday, January 31, 2000 5:11 PM Subject: Re: Toasters in Compaq Racks and Unicode Files

Hi, Some requests from NT do not supply Unicode file names, but instead use the PC character set. Setting the language indicates which PC character set is in use, so that it can be properly translated to Unicode.

The volume's language should be set as soon as possible after bringing up a 5.3 release.

Joan Pearson Network Appliance

At 10:47 PM 1/30/00 , you wrote:

...

Hi There,

Has anyone out there installed F 760es in Compaq racks? Any special

tips,

...

problems etc....

Also, can anyone relay any experiences (good or bad) with using

Non-English

...

files and directories for CIFS clients on Toasters.

And finally, the System. Admin Guide talks about setting a language of a volume with the "vol lang volume langcode" command. Does this having any affect for Unicode clients, ie NT?

Any help appreciated.

-- Andrew Webster Windows NT Consultant Sanno Move Project Deutsche Securities Ltd. - Tokyo Tel. +81-3-5408-4787 Fax. +81-3-5401-6998 Andrew-M.Webster@db.com