[Samba] Caracteres ñ á é ó ú en archive s names not are reading
José Gómez C.
escribo en español.. si hubiera alguien que entienda y pueda ayudarme.. le agradecería.
He migrado de la Ver. 2.x xxx a la version 3 y tengo el problema que en windows, no se puede leer los archivos que tienen en su nombre los caracteres ñ, á, é, í, ó, ú
Por lo que causa un grave problema... hay demasiados archivos con esas letras.
Hay alguna forma de solucionar el problema???
Jose Gómez C.
jgo...@maxuhle.edu.pe
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Ed Holden
We've migrated from Samba 2.x to version 3 and have a problem wherein
Windows clients can't see files that contain the characters ñ, á, é, í,
ó, or ú. This is a serious problem because we have a lot of files
containing these letters.
Is there any way to solve this?
José Gómez C. wrote:
> Dear friends:
>
> escribo en español.. si hubiera alguien que entienda y pueda ayudarme.. le agradecería.
>
> He migrado de la Ver. 2.x xxx a la version 3 y tengo el problema que en windows, no se puede leer los archivos que tienen en su nombre los caracteres ñ, á, é, í, ó, ú
> Por lo que causa un grave problema... hay demasiados archivos con esas letras.
>
> Hay alguna forma de solucionar el problema???
>
>
> Jose Gómez C.
> jgo...@maxuhle.edu.pe
>
>
Any information, including protected health information (PHI), transmitted
in this email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential and or
exempt from disclosure under applicable Federal or State law. Any review,
retransmission, dissemination or other use of or taking of any action in
reliance upon, protected health information (PHI) by persons or entities other
than the intended recipient is prohibited. If you received this email in error,
please contact the sender and delete the material from any computer.
Andrew Bartlett
> A translation, for anyone who knows the answer ...
>
>
> We've migrated from Samba 2.x to version 3 and have a problem wherein
> ó, or ú. This is a serious problem because we have a lot of files
>
> Is there any way to solve this?
This is the 'unix charset' problem. You have two options:
Convert the filenames on the server to UTF8
or
Set the unix charset to what your clients were using as their DOS
charset (for example, CP850).
If you can manage it, then converting the filenames is a much better
option - as UTF8 can represent all possible unicode values that can
occour in CIFS. Bad things happen when we cannot convert names :-(
But changing the 'unix charset' is easier.
Andrew Bartlett
--
Andrew Bartlett abar...@pcug.org.au
Manager, Authentication Subsystems, Samba Team abar...@samba.org
Student Network Administrator, Hawker College abar...@hawkerc.net
http://samba.org http://build.samba.org http://hawkerc.net
Romy Perez Moreno
dos charset = CP850
unix charset = ISO8859-1
and my users can read their files now. I'll wait for a couple of weeks and
then go back to UTF8. Mean while, they are warned not to use any rare
character in the file names.
romy
On 18 Nov 2003, Andrew Bartlett wrote:
> On Tue, 2003-11-18 at 07:26, Ed Holden wrote:
> > A translation, for anyone who knows the answer ...
> >
> >
> > We've migrated from Samba 2.x to version 3 and have a problem wherein
> > Windows clients can't see files that contain the characters ñ, á, é, í,
> > ó, or ú. This is a serious problem because we have a lot of files
> > containing these letters.
> >
> > Is there any way to solve this?
>
> This is the 'unix charset' problem. You have two options:
>
> Convert the filenames on the server to UTF8
>
> or
>
> Set the unix charset to what your clients were using as their DOS
> charset (for example, CP850).
>
> If you can manage it, then converting the filenames is a much better
> option - as UTF8 can represent all possible unicode values that can
> occour in CIFS. Bad things happen when we cannot convert names :-(
>
> But changing the 'unix charset' is easier.
>
> Andrew Bartlett
>
>
--
Ing. Romy Perez Moreno
e-mail: ro...@fenix.uam.mx, ro...@correo.azc.uam.mx
http://fenix.uam.mx/romy
tel: 5318 9067 / 5382-7157
Thiago Lima
I had the same problem some time ago and I changed the unix charset. How
to convert the filenames to the correct charset? And how to discover
what charset is beeing using in a file?
regards.
thiago.
> This is the 'unix charset' problem. You have two options:
>
> Convert the filenames on the server to UTF8
>
> or
>
> Set the unix charset to what your clients were using as their
> DOS charset (for example, CP850).
>
> If you can manage it, then converting the filenames is a much
> better option - as UTF8 can represent all possible unicode
> values that can occour in CIFS. Bad things happen when we
> cannot convert names :-(
--
Jeremy Allison
> A translation, for anyone who knows the answer ...
>
>
> We've migrated from Samba 2.x to version 3 and have a problem wherein
> Windows clients can't see files that contain the characters ñ, á, é, í,
> ó, or ú. This is a serious problem because we have a lot of files
> containing these letters.
>
> Is there any way to solve this?
To get the same character set compatibility set use:
unix charset = ISO8859-1
dos charset = CP850
in the [global] section of your smb.conf.
Jeremy.
Bjoern JACKE
>I had the same problem some time ago and I changed the unix charset. How
>to convert the filenames to the correct charset? And how to discover
>what charset is beeing using in a file?
check out http://j3e.de/linux/convmv/. A man page is availabel at
http://j3e.de/linux/convmv/man/.
convmv can convert whole directories recursively to a different
encoding, per default it is in "testmode", so it will not change the
filenames for you to see the conversion will do the right. When you
are sure, convert the files to utf-8 with --notest option. It's even
easier than changing the unix charset option. ;-)
Bjoern