#20 renaming of incomming files

[Ernesto Bricca]

if the files are moved to the incomming folder and a dl link was
used the name of the file is a bit scrambled as the special
characters aren't converted back .. like %20 for space

[Fred Bonzoun]

Logged In: YES
user_id=548735

Should be better in 0.23. But the accents still get converted to a
strange \xxx form and I don't know how to solve that. I think that
mldonkey has issues with the accents.

[Ernesto Bricca]

Logged In: YES
user_id=569491

think that the \xxx are ascii number substituents.
postprocessing the files in the incoming folder maybe an option ..
searched a bit at google .. and the terminal
as ex ä (html) is represented in the terminal by a\314\210
first the \xxx numbers seem to be in the octal format (basecalc from
versiontracker may help to transverse the numbers)
where /210 seems to represent ISO 8859-1
(136 210 88 hs Character tabulation set (hts))
and /314 seems to represent the double points (maybe ebcdic or roman8
encoding ??)

[Ernesto Bricca]

Logged In: YES
user_id=569491

well .. should have known that .. special characters in the terminal are
unicode formated.
correct is that the \xxx numbers are in the octal format. (an example ..
"16" in decimal format is "20" in octal format and "10" in hex)
in my example about the (a\314\210 in unicode(utf-8) or ä in
html) the a is followed by a (double point) extention character that goes
upon the a ..
to be compatible with the terminal (standard ascii output) the unicode
sign "\314\210" has utf-8 encoding. the hex values of "\314" "\210" would
be "cc" "88". (possible to check it with "HexEdit" and osx "TextEdit")