The SC2Localizer is usually obsolete and produces unneeded file size increase. You just need to make sure, that your map only includes data for one language.
If your map has localization issues, try the following:
(save a backup of your map)
Save the map as component list, close the editor afterwards
Decide for one main language you use for the project, for example enGB for european english. If only files for one language exist, all languages will use these files.
Merge all text files within your language folders. So you open for example enUS.SC2Data/LocalizedData and copy&paste the text of all included text files in the files of the same name in the enGB.SC2Data/LocalizedData folders. If one text file is not present, copy the entire file. Repeat for any other language.
If you used the localizer before, these files could be copies of each other; in this case, you don't need to merge them. Just make sure, all needed text is present.
Delete all language folders, except your main one. Make sure, all available text is within this folder
Open the ComponentList.SC2Components with a text editor and delete all lines, which include a not-main language like this: <DataComponent Type="text" Locale="enUS">GameText</DataComponent>
Open the ComponentList.SC2Components again, this time with the galaxy editor. Save it as a map file again.
Sounds more complicated than it is. It shouldn't take more than a few minutes.
This should fix any localization issue.
The SC2Localizer is usually obsolete and produces unneeded file size increase. You just need to make sure, that your map only includes data for one language.
If your map has localization issues, try the following:
If you used the localizer before, these files could be copies of each other; in this case, you don't need to merge them. Just make sure, all needed text is present.
<DataComponent Type="text" Locale="enUS">GameText</DataComponent>
Sounds more complicated than it is. It shouldn't take more than a few minutes.
This should fix any localization issue.