The Samba-Bugzilla – Bug 425
charset/unicode documentation incorrectnesses
Last modified: 2005-08-24 10:26:02 UTC
I'll attach a fix for unicode.xml. Things about previous Samba defaults are
But one more thing about unicode.xml. It's written there that Japanese is a
problem due to iconv problems with CP932. Is this still a problem? I never
heared about a problem here before and Japanese works okay for me with Samba3.
Created attachment 130 [details]
unicode docu fix
Fixed in book CVS. Should be in 3.0 CVS by monday.
the patch also corrected the link to convmv for filename conversion. The cvs
now doesn't seem to contain the link to convmv anymore, no hint anymore. Where
is that gone?
The changes I wrote in the patch have been somewhat more verbose than what is
written in the howto now, did you not like what I wrote?
And what about the japanese support which doesn't seem broken at all, I wrote
I don't know why the convmv link went out ... Anyway, it's back in. I didn't
apply the other part of your patch because it was incorrect.
sorry if I do not agree ;-)
I added this sentence:
The default in previous samba releases was to save filenames in the encoding
of the clients, for example cp850 for western european countries.
What is wrong about that? That's what Samba 2.x does.
Befere there was written, that ASCII would be the default and THAT was not
The above sentence is quite important for people reading the howto to
understand how their existing files from the Samba2 server are encoded.
That's not what this is about. This is the charset samba assumes the OS is using
internally. I can agree with the fact that the current document is confusing,
Ping, still there?
sorry, are you expecting any additional information from me? Can I do anything
Sorry, my mistake.
Jelmer, this bug still needs some work. ASCII was not the default in previous
samba versions, this is still wrong in the HOWTO. I'm still sure that my change:
"default was to save filenames in the encoding of the clients' codepage" is
correct. That happened when no "character set" varibale was set. Samba did no
assumptions. "client codepage" parameter was used to convert to "character set"
when that was set.
updating qa contact
Rest of the patch applied. Thanks for your patience ;-)
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.