Bugzilla – Bug 325295
MoMA fails to load resources/descriptions if path contains certain non-ASCII characters
Last modified: 2008-01-02 03:56:38 UTC
---- Reported by joey@muhkuhsaft.de 2007-08-29 11:49:26 MST ---- Please fill in this template when reporting a bug, unless you know what you are doing. Description of Problem: Steps to reproduce the problem: 1. Place MOMA in a directory that contains non-ASCII characters (in my case: C:\Users\Johannes Rössel\MoMA [German umlauts seem to yield the problem, arbitrary Unicode do not]) 2. Start MoMA.exe from that folder 3. Watch MoMA produce the following error message: Actual Results: --------------------------- System.IO.FileNotFoundException: C:\Users\Public\MoMA�\Resources\monoback.png at System.Drawing.Image.FromFile(String filename, Boolean useEmbeddedColorManagement) at System.Drawing.Image.FromFile(String filename) at MoMA.MainForm.LoadImages() --------------------------- There was an error loading resources for MoMA, please try downloading a new copy. Error: {0} --------------------------- OK --------------------------- This seems to be an encoding problem of the filename string, though it is unclear to me whether this is a problem with the code or the CLR. Expected Results: MoMA starting without an error message How often does this happen? Every time th path to the program contains umlauts (äöü, some other Latin accented characters as well, arbitrary valid Unicode code points don't produce a problem, however. I've tried with some Latin [not encoded in Latin 1], Chinese and Devanâgarî). Additional Information: (none) Unknown bug field "cf_op_sys_details" encountered while moving bug <cf_op_sys_details>Windows NT 6.0, .NET CLR 3.0</cf_op_sys_details> Unknown operating system other. Setting to default OS "Other".
I tried looking at this again, only to find I could no longer reproduce it. It appears this is fixed in .Net Framework 2.0 SP1. Unfortunately, it seems Mono suffers from a similar problem. I will file a bug for Mono for this.