just installed the latest release on Windows and I'm noticing that the (all?) Umlaute in the interface translation appear as garbage. I'm afraid something went wrong with the updated de.po file I sent to Allin this time instead of committing it myself to cvs.

Am 07.05.2014 00:05, schrieb Allin Cottrell: > On Tue, 6 May 2014, Sven Schreiber wrote: > >> just installed the latest release on Windows and I'm noticing that the >> (all?) Umlaute in the interface translation appear as garbage. I'm >> afraid something went wrong with the updated de.po file I sent to Allin >> this time instead of committing it myself to cvs. > > Yep, de.po is broken, I'm afraid. In CVS I've rolled it back to revision > 1.321, the last version with correct encoding. Hopefully you may be able > to salvage something from rev. 1.322. > I still don't understand the problem I must say. When I re-download rev 1.322 from (web) cvs and set the file encoding in the text editor (Scite on Windows) to UTF-8, everything looks fine. Viewing it with Sourceforge's webcvs indeed shows it being messed up, but that looks as if they somehow use a Windows codepage encoding for that -- at least the appearance is the same if I set the encoding in the editor to Windows's own.