I think removing this should be as easy as deleting the 3 other messages_xx.properties files. The code seems to look for a resource bundle in the current language and if that fails, it falls back to english. So deleting these files should resolve these issues and it would eliminate the danger I see when it comes to out-of-sync resource bundles.
Chris ________________________________________ Von: Alex Harui <aha...@adobe.com> Gesendet: Mittwoch, 24. Februar 2016 18:51 An: dev@flex.apache.org Betreff: Re: AW: AW: Think I found out, why the falcon integration-tests never succeed when running them Wow, that's really interesting. I'd be happy to simplify and remove localized compiler errors. I suppose an alternative is to add an error "identifier" to the error output. I think an error number is currently used, but error numbers don't really help in a search. I think other compilers use better identifiers like E_RESOURCE_BUNDLE_NOT_FOUND. Anybody think we should go down that road? Thanks, -Alex On 2/24/16, 9:14 AM, "Josh Tynjala" <joshtynj...@gmail.com> wrote: >In the past, I have heard other non-English speakers say the same thing as >Chris and Félix. There's more web content (blog posts, forum threads, >etc.) >about the English error messages, so trying to search for the error in >other languages ends up excluding relevant content. > >- Josh > >On Wed, Feb 24, 2016 at 9:03 AM, Félix GERZAGUET ><felix.gerzag...@gmail.com> >wrote: > >> Hello, >> >> On Wed, Feb 24, 2016 at 5:56 PM, Christofer Dutz < >> christofer.d...@c-ware.de> >> wrote: >> >> > Actually in the past they have slowed me down, cause if I have an >>error, >> > which I don't understand, I can be certain that I need to feed google >> with >> > the english version, so I tried to guess the english one and >>eventually >> > look it up in the resource-bundles :-) >> > >> >> I had the exact same experience. >> For a developper facing error message, I prefer english. >> >> --Félix >>
