https://bugzilla.novell.com/show_bug.cgi?id=643248
https://bugzilla.novell.com/show_bug.cgi?id=643248#c2 --- Comment #2 from bryan costanich <[email protected]> 2010-10-05 05:19:44 UTC --- these are two separate issues. one is the invalid characters and two is that the error messages during build are hidden. on the first, it seems like it would be better to just lowercase them during the build. on the second, the errors need to be parsed and displayed to the user. you can get all kinds of errors, for example, malformed xml, etc. many of these errors have nothing to do with illegal file names.(In reply to comment #1) > The question is, what's the appropriate thing to do? > > The glib answer is "allow UpperCase characters to be used in resource names." > Unfortunately, since we're currently wrapping Android's tooling (aapt > package), > and Android's tooling requires all lowercase...this isn't feasible at this > time. > > Next would be for the error message to be...useful. That would be a dupe of > 643660. > > Given the current choices, I'm going with "dupe". > > *** This bug has been marked as a duplicate of bug 643660 *** -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
