SC2Mapster

As some people know, US maps are bugged for EU people. Ingame stuff like 'Lives: 10' shows up as 'Param/Value/AB1491AAE3' or something like that. For this, I suggest adding the rule that maps must say where they were made.

Good idea :)

Or maybe report this because there should be no issues like this in the final game.

The problem is that basic map makers (everyone here right now) do not have the resources to translate the game in every language out there. We will at most translate it into 2 languages. I think that having the possibility to set a default locale would be the best way to deal with this problem.

Problem is also that some maps is unplayable, cause except that bad string with text it that trigger do nothing :)

for fix you could use http://forums.sc2mapster.com/development/map-development/520-easily-adding-new-locales/

If, of course, this wasn't intentional. I think it may be intentional, even if it would make the localised versions of the game somewhat unpopular. It is however monumentally silly that US English and EU English are two different string sets.

In Diablo 2 modmakers included their changed strings in every language version, so if you had the French copy it would turn your game into English.

Did another How-to, to 'fix' it currently for Text and stuff (another way than Fiskers)

http://forums.sc2mapster.com/development/tutorials/611-misc-how-to-prevent-localization-errors/

But still would be nice to be able to make a 'default' localization data for all languages :)
or some kind of pointer, refering your SC2Localization to MapLocalization
to avoid stuff like that

Quote from Sixen: Go

This isn't a bug, the problem is that people on US are only adding US Locale GameStrings, same with EU. Creating GameStrings for both Locales fixes this problem.

It might not be a bug, but since most map makers won't define all the locales (I think there are about 8 or 9?), they need to change this.

I'm a EU mapmaker, and it pains me along with several others to play all the great maps here but unable to see any text whatsoever. They need to change it so that if other locales are not defined, it reverts to the original (default) locale. If Sixen has a thread which Blizzard is paying attention to, I sincerely hope he will bring up this issue. There are many people from all over Europe suffering from this atm. :(

I just checked US vs GB version byte by byte, there is difference in 3 files, this files refer to language ID only, data is completely same.