Home > Archive > Clipper > May 2005 > NDS NetLib functions and unicode (UNI*.*) files
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
NDS NetLib functions and unicode (UNI*.*) files
|
|
| E. Fridman 2005-05-13, 3:55 pm |
| Knowledge base for NetLib 6.5 notes that to use NDS functionality you
need to have unicode (UNI*.*) files in the path (see
http://www.netlib.com/regusr/n00068.htm).
I've noticed a big disparity between the number of unicode files in
SYS:\PUBLIC\NLS (about 500) and C:\WinNT\System32\NLS (about 50).
The Unicode Files Explained article I found at
http://www.dreamlan.com/ndsnotes.htm#unicode states that "typically
only four unicode files are needed at any one time. The names of two of
the files varies depending on the country code and codepage settings on
your workstation".
Does anybody know whether this is true for NetLib as well?
Also, did the unicode files themselves change between Windows and
Netware versions? If so, would it be reasonable to expect that this
legacy library is compatible with "old" unicode files only?
| |
| Eugene 2005-05-15, 8:55 pm |
| David,
Thank you very much for the reply.
NetLib is a "black box" to me. I do not know its internals. Since its
authors published a knowledgebase article about this requirement I
accept it
as such.
When we were investigating one of the problems in the field we've
discovered
that restoring the search drive mapping to the PUBLIC/NLS directory on
the
SYS volume has eliminated the malfunction. The PATH did include local
NLS
directory from Win'NT all the time.
Eugene
========================================
==============
"David Gersic" <dgersic_@_niu.edu> wrote in message
news:d5ubkt$g6t$1@usenet.cso.niu.edu...
> On 11 May 2005 12:38:15 -0700, E. Fridman <pm771.am@gmail.com> wrote:
you[color=darkred]
>
> This is likely to be correct. The start to any NDS aware program is
> to initialize the libraries, and the init call has to find the
Unicode
> stuff on the path.
>
>
two of[color=darkred]
settings on[color=darkred]
>
> The unicode files are mostly irrelevant. Yes, only the ones for the
> current language will be used, and unless you're actually *using*
> them, you'll never need them.
>
>
> --
> | David Gersic www.zaccaria-pinball.com
dgersic_@_niu.edu
| |
| Eugene 2005-05-18, 3:55 am |
| David,
Thank you very much for the reply.
NetLib is a "black box" to me. I do not know its internals. Since its
authors published a knowledgebase article about this requirement I
accept it
as such.
When we were investigating one of the problems in the field we've
discovered
that restoring the search drive mapping to the PUBLIC/NLS directory on
the
SYS volume has eliminated the malfunction. The PATH did include local
NLS
directory from Win'NT all the time.
Eugene
========================================
==============
"David Gersic" <dgersic_@_niu.edu> wrote in message
news:d5ubkt$g6t$1@usenet.cso.niu.edu...
> On 11 May 2005 12:38:15 -0700, E. Fridman <pm771.am@gmail.com> wrote:
you[color=darkred]
>
> This is likely to be correct. The start to any NDS aware program is
> to initialize the libraries, and the init call has to find the
Unicode
> stuff on the path.
>
>
two of[color=darkred]
settings on[color=darkred]
>
> The unicode files are mostly irrelevant. Yes, only the ones for the
> current language will be used, and unless you're actually *using*
> them, you'll never need them.
>
>
> --
> | David Gersic www.zaccaria-pinball.com
dgersic_@_niu.edu
|
|
|
|
|