Bugs item #3462889, was opened at 2011-12-20 00:28 Message generated for change (Comment added) made by pegacat You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=480577&aid=3462889&group_id=55394
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: jpstotz (jpstotz) >Assigned to: Christopher Betts (pegacat) Summary: Windows: Wrong charset used for loading translations Initial Comment: I installed JXplorer using the current stable installer for Windows (jxplorer-3.2.2-windows-installer.exe) on a German Win7 system. It seems to me like JXplorer loads the translations using the default charset (which is on Windows "Cp1252" and not UTF-8) which results in bogus characters displayed in the GUI everywhere an umlaut would be used (see attached screen-shot). ---------------------------------------------------------------------- >Comment By: Christopher Betts (pegacat) Date: 2012-02-21 14:42 Message: Not sure why this stopped working, as the code hasn't been touched for years... however these days I think we can take it that UTF-8 is the default. The existing code tried to 'test' for UTF-16 and UTF-8 and defaulted to the local encoding; I've changed this so that it now defaults to UTF-8 if there's any ambiguity. I've also added a 'force.locale' config flag to make it easier to test this stuff :-). Fix is in v3.3b3, which I'll upload today... ---------------------------------------------------------------------- Comment By: jpstotz (jpstotz) Date: 2012-02-17 05:35 Message: I made a quick check where the problem is located. I found out that JXplorer uses some really strange encoding which is used for the German and French translation file. Both are currently encoded the way Java defines Unicode characters but processed by custom code - which seems to fail on current Java versions. The simplest way is just to remove this strange encoding and use UTF-8 instead. I have done that for the German translation file (see attached). If someone could take this over for the French file as well that everything would be fine again. ---------------------------------------------------------------------- Comment By: https://www.google.com/accounts () Date: 2012-02-15 07:21 Message: Same here. Bug confirmed! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=480577&aid=3462889&group_id=55394 ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Jxplorer-devel mailing list Jxplorer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jxplorer-devel
