T.R | Title | User | Personal Name | Date | Lines |
---|
1624.1 | as has been said MANY times... | TOHOPE::VORE_S | Smile - Mickey's Watching! | Tue Oct 08 1996 13:13 | 12 |
1624.2 | ���xxx.txt in filename ok in V6.1 | EVTAI1::CASTELLO | UNIX and PCI Support | Tue Oct 08 1996 13:59 | 16 |
1624.3 | International chars starting to work... | AROS01::ISACSSON | Jan-Erik "ISAK" Isacsson | Wed Oct 09 1996 09:05 | 31 |
1624.4 | .1 is way out on thin ice | STKAI1::PTORLIND | | Wed Oct 09 1996 10:40 | 23 |
1624.5 | | TOHOPE::VORE_S | Smile - Mickey's Watching! | Wed Oct 09 1996 15:35 | 5 |
1624.6 | what's funny ??? | STKAI1::PTORLIND | | Wed Oct 09 1996 16:20 | 24 |
1624.7 | V6.2 | BULAN::peoto.soo.dec.com::stkai1::ptorlind | | Tue Oct 15 1996 06:14 | 17 |
1624.8 | It will be too late | EVTAI1::CASTELLO | UNIX and PCI Support | Tue Oct 15 1996 06:42 | 8 |
1624.9 | V6.1: locale= !???!!! in lanman.ini | EVTAI1::CASTELLO | UNIX and PCI Support | Tue Jan 28 1997 10:55 | 30 |
| Hello,
One of my collegue gave me a hint on International character.
On Unix environment variable LANG and other are used by open(),create(),...
system calls.
Since V6.1 In [ lmxserver] section of lanman.ini there is a non documented
and "secret" variable called "locale". (see srvconfig -p)
locale = en_US.437 (default value)
this variable seems to be used by setlocale() system call in Pathworks.
Setting this varable to fr_FRISO8859-1 save pb when we try to delete a intern.
filename or dirname with WIN95,WFWs,...for French customers.
The customer may now save his user profile on the server !!!!!
Wihtout it he could not delete a dirname with intern. char.
A QAR has also been reported for other language as Germain.
Setting this variable to de_DE.ISO8859-1 can also save the pb with with dirname
that can't be delete....
This rule can be apply for other country.
Hope this help.
Jean-Pierre
http://mosupc.evt.dec.com
|
1624.10 | Great tips wortk in swedish to | AROS01::ISACSSON | Jan-Erik "ISAK" Isacsson | Fri Jan 31 1997 05:25 | 9 |
| Seems that setting locale makes us able to delete files with international
characters. Still have problem rename files , can only rename to same number
on chars in filename. But still it works a lot better.
A tips to see what locale is used for different countries is the command
locale in Dunix. locale -a lists all available locales on the system.
Regards Isak / Nos support - Sweden
|
1624.11 | upper case work around | EVTAI1::CASTELLO | UNIX and PCI Support | Fri Jan 31 1997 13:22 | 37 |
| Hi,
Just to clarify a bit the upper/lower case workaround 1624.9
in lanman.ini the locale= parameter is used by:
lmx.srv,lmx.ctrl,lmx.dmn,lmx.repl
All of this process run setlocale() system call with in arg the locale= param.
to set LC_CTYPE.
LC_CTYPE Affects the behavior of character classification functions
character conversion functions, and regular expressions.
Filename and dirname received by lmx.srv are converted
to lower case char before creating the Unix name on disk.
It uses islower/isupper routines to do that.
Islower/isupper are impacted by the LC_CTYPE value that points to a character
table class.
If the character is unknown in the table selected the islower/isupper routines
return false code and the char is not converted and can't match with the real
character of the filename/dirname.
( That is also applied for file access right check.!! )
Another important thing is berfore processing the filename/dirname the namefile
is received and parsed by the SMB server.
The SMB server has the same problem with the I18N characters sent by WIN95.
But hopefuly the server does not break the operation. It just informs the system
that the SMB message is illegal.
see elfread -d system
So keep in mind that it is only a workaround untill the full 8bits support.
==========
Regards,
Jean-Pierre
|
1624.12 | update on I18N work-around | EVTAI1::CASTELLO | UNIX and PCI Support | Fri Apr 04 1997 05:18 | 64 |
| Limited International characters (I18N) in filenames and dirnames
support with PATHWORKS for Digital UNIX V6.1ECO1 and earlier.
Since PATHWORKS for Digital UNIX V6.1 there is a new parameter
locale=en_US.437 in lanman.ini file (default value).
This parameter is used by PATHWORKS for language variant in characters
routines like islower(), isupper()... asking UNIX operating
the use of ISO 8850 variant table.
Inside the lmx processes the UNIX system call setlocale() is
then used with the lanman.ini locale=xxx to set LC_TYPE.
LC_TYPE affects the behaviour of character classification functions and
character conversion function.To see what locale=xxxx UNIX variable is
available for different country just type locale -a under UNIX prompt.
What does PATHWORKS support ?
Officially locale=en_US.437 is the default and the only supported value
for PATHWORKS.
More support is under investigation and will be integrated in a next version.
What can we do temporary for no US customer ?
his unsupported solution has been provided by the French Support and tested
in some European customer environment.
The solution is only available for dirname and filename
and not for username, groupname,. . . .
Depending of the country set the lanman.ini locale=xxxx then restart
PATHWORKS for DIGITAL UNIX. i.e. locale=fr_FR.ISO8859-1 for French characters.
Then a PC with WIN95/WIN-NT can create a filename/dirname with international
characters.
Some PATHWORKS Unix command like net access can also be used with international
characters.
i.e. net access "C:\eec\castello\jpca��.txt" the two last char of the the
filename are with accent.
Prerequisit :
- the OSFEURLOC410 (Single-Byte European Locales (system administration) )
subset
must be installed.
- the minimum version of PATHWORKS is V6.1ECO1.
Known problem :
- a warning " An illegal SMB was received from PC_NAME " can be logged
in error log file. See elfread -d system command on PATHWORKS server.
Hopefuly the server does not break the operation.
- Du to a BUG in the UNIX - tr "[a-z]" "[A-Z]" - that command does not work
if the shell variable LANG is not set to C.
(it's the case in some European customer).
This bug breaks some PATHWORKS script and during installation or upgrade
procedure we can have error message regarding ASE configuration
even if you have not ASE installed.
Modify it the time of installation.
Tests :
This workaround is given as-is.
Again please note this is not officially supported and DIGITAL Equipment
Corporation assumes no responsability for any errors that may appear after
installation.
However some European customer are using it since several weeks without problem.
Jean-Pierre
http://mosupc.evt.dec.com
|