NOVELL FORUMS

#2 06-Oct-2005, 11:04 PM

Well I finally sorted it out.

I had to turn on UTF-8 encoding in the Novell Client. The setting was
on by default on the server, so I'd assume it has to be on also for this
to all work.

For the Novell Client (4.91 SP1):

The setting is Advanced Settings -> Use UTF-8 encoding and NCPs -> On

For the OES Server (SP1):

Yast -> System -> Choose Language -> {chosen language} -> Details ->
enable 'use UTF-8 encoding'

This requires a reboot of the client PC, and I'd advise restarting
eDirectory also (ndsd).

I initially found there was a codepage option that can be enabled in
/etc/opt/novell/ncpserv.conf called LOCAL_CODE_PAGE. The list of
available codepages can be seen on the OES box with 'iconv --list'

Some documentation I found indicated the default codepage for the system
is picked up if none is specified, but I could not find a way to
determine what it had picked up as the default. I set the
LOCAL_CODE_PAGE optoin to various values, but none had any visible
effect, so I can only conclude this side of it doesn't matter and the
two UTF-8 options above are the key.

Ryan

Ryan wrote:

<snip>

> I've created several NCP shares using Remote Manager which work and
> share out fine on XP Pro client PCs with the Novell client (4.91),
> however there is an issue with filenames:
>
> (1)
> Any file or directory name that has the characters [\d\d] anywhere in it
> (ie, two digits surrounded by square brackets) has that character
> grouping replaced with a square when viewed from a Windows client. This
> makes all such files inaccessible. Remote Manager and Linux console
> display and access the file fine.
>
> (2)
> Any file or directory name that has the characters [\d\d\d\d] anywhere
> in it (ie four digits surrounded by square brackets) has that character
> grouping replaced with a unicode character equal to the 4 digit number
> when viewed from Remote Manager or the Linux Console - but is still
> accessible, and is accessible and viewable fine from a Windows client.