> Stefan Küng wrote:
> I've changed the encoding detection so it defaults to utf8 now. This should fix your problem.
> Note: there simply is no perfect solution to this: as stated above, a file can be treated as utf8 or ascii if no special ascii (> 127) or utf8
> chars are in the file. And when merging, we also can't
> assume that the resulting file should have the encoding of the merge source - that might not what the user wants either. Who's to say that the
> user doesn't want to keep the existing encoding of the
> file?
>
> But making the default to utf8 is better than ascii I think...
>
> Stefan
Thank you for this fast solution on this!
I know that Encodings are always a bit tricky. ;-)
But since UTF-8 is becoming more common every day it's probably the best solution to make it default.
If there are problems with the new default UTF-8 enocding you could change it to only save UTF-8 if there are special Characters in the merge result?
Keep up the great work!
Greetings from Austria
Andreas
Andreas Schnederle - Wagner
Futureweb.at
Innsbrucker Str. 4
6380 St. Johann
schnederle_at_futureweb.at
www.futureweb.at
Fon: +43 (0) 5352 65335
Fax: +43 (0) 5352 63148
Gratis über Skype anrufen | Skype-ID: futureweb
Received on 2008-08-13 12:48:15 CEST