RE: [microdc-devel] German Umlauts

[Vladimir Chugunov]

> On 061213 at 18:20, Hermann Schneider wrote:
> > i have found the problem, a knowledged guy said me, that 
> the msg from
> > users, are displayed in the charset THE CLIENTS have set.
> 
> Not exactly, the *bytes* that clients send your when *they* type ü
> depends on what their client likes. The \374-values you see seem to be
> from iso8859-1 or similar. You can also see real umlauts, so 
> some users
> seem to send you byte-streams that are compatible with your
> utf8-settings.
Probably I'll disappoint you but according to dcpp client used in StrongDC it 
looks like the transmition between hub and client is made using current 
codepage set in Windows. I don't think that hub software convert the incoming 
chat messages to some internal format - I think it simply distributes the 
messages to other client without conversion. This means that all clients 
connected to the same hub must have the same codepage settings in their Windows 
systems. For example microdc2 is working perfectly on russian hub using cp1251 
codepage but in this case the we speak not about several characters but about 
complete alphabet.

> > i change only the behavior of my display in the hubmsges. 
> So i can only
> > fit to some group of users with the same charset,
> 
> Yes.
According my explanation above all clients must have the same encoding as the 
hub uses.

> 
> > Also he said, that the most dc clients, autoregocnize the 
> charset the
> > user has and converts, and thats why other clients havent 
> that kind of
> > probs.
Probably I'm wrong but I think it is impossible in general case - there is no 
way to automatically detect encoding between CP1250 and CP1251 codepage for 
example. It can be implemented just in some special cases like for example UTF8 
encoding detection.

> 
> This may be an interesting feature. I think it would already help alot
> if at least utf8 is recognised automagically. Hubs using different
> old charsets should not be that common, are they?
Unfortunately hub has no encoding at all, I think. Just because it doesn't need 
to understand the client messages.

Regards, Vladimir.

P.S. Hermann, try to set the hub_charset variable to CP1250 or CP1252 value.