Re: [microdc-devel] German Umlauts

[Hermann Schneider]

Hi,

first of all, i wanna to provide that *mixed* log :)

microdc2> set log
connections    download       publicchat     upload
debug          joinpart       searchresults

with hub_charset UTF-8 and filesystem_charset UTF-8.
I set that only that u got your mixed log :)
I hope that are the right settings, i will run that log a day, to be
sure have a really mixed log :)

The second is, that if i change to CP1252 the hub_charset AND
the filesystem_charset, nearly all "äöÜ" are right displayed, also in
filenames, BUT the the Names in the hub are still trash, it seems to me,
that the names in the hub, dosnt react on that i change the charset, i
get allways the same trash names, no matter if UTF-8 CP1250 CP1252.
Wenn I use CP1252, which is better, cause there are more guys that dont 
use UTF-8 i get following:


> microdc2> who
> [AF]Rick              [KH]Crease            [KH]Tomata            [KH]kasper  
>           [NR]Suprmofo          [RE]FiL
> [AG]jake_jones        [KH]D'Oh              [KH]_Gasolin          [KH]maz     
>           [NR]injkaans          [RE]Schneckelecker
> [AG]jizzmaster-zero   [KH]Filmlager         [KH]abab32            [KH]pirat   
>           [NR]nono              [RE]bomberharris
> [AG]mhmo              [KH]Frosti            [KH]boiana            [KH]tekmun  
>           [NR]starwish          [RE]hans
> [AS]Ombre             [KH]Galinha           [KH]casper26          [KH]v       
>           [NR]\302\240\\(^o^)/  [RE]ktal
> [AS]Schu              [KH]Joze              [KH]chiquita          [NR]Alutil  
>           [PP]TheLeach          [RE]kuchen
> [AV]STD               [KH]Masa              [KH]conscience        
> [NR]DomsLinux         [PS]marcel            [SG]Sheppard
> [CA]F\303\211         [KH]Mr.Orange         [KH]daishan           [NR]Evarice 
>           [PW]DERBES            [XX]DrBunsenHoneydew
> [CA]exodos            [KH]ODIN              [KH]fertxo            [NR]JOHNNY  
>           [PW]Seilo
> [KH]Babus             [KH]Speed_Junkie      [KH]guixx             
> [NR]Perflubon         [RE]808y
> [KH]Carmen            [KH]ThePriest         [KH]guto              
> [NR]Rumbomme          [RE]FVLLE
> microdc2> who [CA
> [CA]F\303\211  [CA]exodos
> microdc2> who [CA]F\303\211
> Nick: [CA]FÉ
> Description: <++ V:0.674,M:A,H:1/0/0,S:3>
> Speed: LAN(T1)
> Level: 1
> E-mail:
> Operator: 0
> Share Size: 74533659630 bytes (71080 MB)
> microdc2> browse [CA
> [CA]F\303\211  [CA]exodos
> microdc2> browse [CA]F\303\211
> Connecting to user on 130.83.142.105:11974
> User unknown1: Connected to user.
> User connection `unknown1' renamed to `[CA]FÉ|'.
> User connection `[CA]FÉ|' renamed to `[CA]FÉ|DL'.
> [CA]FÉ: Starting download of `files.xml.bz2' (9030 bytes).
> [CA]FÉ: Download of `files.xml.bz2' succeeded (transfer complete). 8,9KiB 
> transferred in 2s (4,5KiB/s).User [CA]FÉ|DL: No more files to download.
> Shutting down user connection process for `[CA]FÉ|DL'.
> Now browsing [CA]FÉ.
> microdc2:[CA]FÉ:/> ll


well u see the thing i mean? if i look for users there i have a 
[CA]F\303\211 guy, if i who hin, his nick is displayed corerct,
or better said all execpt that nick in the "console mode" are displayed
correct. If i canged back to UTF-8 i saw only [CA]F\303\211 everywhere.
I think in "that area" there is the "internationl support" missing?
Because that part of the names, dosnt hear to hub_charset of
filesystem_charset.
But i think u can tell me more, and find maybe a reason :)

i will sent the mixed chat log, in some hours.

Greetz,

Hermann





Am Donnerstag, den 14.12.2006, 08:50 +0300 schrieb Vladimir Chugunov:
> Steffen Schulz wrote:
> >
> > On 061213 at 21:40, Vladimir Chugunov wrote:
> > > 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.
> >
> > Hub and client? You mean client system and client software. Yes, it
> > would be typical for windows software to not care at all and just send
> > what they got...
> >
> I mean client software. It looks strange for me because according to 
> dcpp client sources I have in StrongDC package the StrongDC internally 
> stores all strings in UTF8 but translate them to active codepage before 
> sending to a hub. I have the only one explanation for this behavior - it 
> was done for backward compatibility.
> >
> > > 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.
> >
> > I think so, too.
> >
> > > > 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.
> >
> > Yes, I wasn't very accurate(one could go as far as to say I was wrong).
> > I meant the set of client connected to the hub.
> >
> > Windows guys will indeed just send whatever they like. But as Hermann
> > said, he can see "some" umlauts, so some people are obviously sending
> > in utf8.
> >
> > The point I wanted to make is that this may indeed be pretty common, as
> > (windows-)clients are getting modernized to use utf8. A set of clients
> > connected to a hub with different local, old charsets by contrast
> > should not be so common.
> >
> > This is because utf8-detection may be interesting. Use the encoding
> > that should be used by legacy systems and detect utf8 automatically.
> > But its an ungly hack and I don't really care..
> >
> I don't like this solution too much because it looks like just 
> workaround. What charset should we use in this case for sending a 
> message to the public chat?
> According to the dcpp.net documentation there is a flag in the chat 
> string what mark utf8 encoded strings. But I've never seen it before so 
> if somebody can provide me a complete log file with such *mixed* chat 
> I'll implement the correct algorithm in the microdc2. (To make such log 
> you have to specify "debug" value in the log variable in addition to the 
> values you have there already). Of course I can just believe 
> documentation and implement it in way the documentation proposes but I 
> prefer to check it first.
> >
> > > P.S. Hermann, try to set the hub_charset variable to CP1250 or CP1252
> > > value.
> >
> > This may break the umlauts for case where they were shown correctly.
> > Its simply stupid protocol design to not specify the encoding..
> >
> Sure, it was easily to specify utf8 encoding for protocol level and then 
> have no problem with national characters at all. Unfortunately we are 
> powerless to make such changes because the implementation is dictated by 
> this weak specification.
> 
> Regards, Vladimir.
> 
> 
> _______________________________________________
> microdc-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/microdc-devel
> 
-- 
öhmmmmmmmm,