Here's what ya do if you are converting the map from language A to language B:
Save the map as a sc2components file. This will split it into a bunch of different files. Close the map.
Open a file browser, and locate your sc2compnents folder. Open that up. Locate the Language Folder, and rename it to your language (enUS, enGB, etc...)
Open the components list in NOTEPAD (not sc2) and change the language reference tag to the new name of your language folder (enUS, enGB, etc...)
Save the file, and then open it in Sc2. You are now localized- save the file somewhere else as a normal sc2map.
Here's what you do if you are merging 2 languages into 1 (say, if people form multiple regions worked on the map). Note that you will be modifying some important data, so make a backup, PLEASE.
Save the map as a sc2components file. This will split it into a bunch of different files. Close the map.
Open a file browser, and locate your sc2compnents folder. Open that up. Locate the Language Folders- there will be more than 1. Decide which one you want to keep (your native language). Between all the language folders, you will find these 4 files: "GameHotkeys.txt", "GameStrings.txt" "ObjectStrings.txt" and "triggerStrings.txt". You need to merge all their contents into 1- your native language.
Open the folders of the languages you don't want. Copy the contents of any files inside into the same files in your language folder. Say I'm converting to US. I'll open the "triggerStrings.txt" file in the EU folder, copy it's contents, and then add that to the "triggerStrings.txt" file in the US folder. You are basically moving all the text into your local language.
In the End, you will have all 4 of these files in your local language's folder. Delete the other folders you don't want.
Open the components list in NOTEPAD (not sc2). You will see multiple language tags. Delete the unwanted languages, leaving only the one you wanted to keep.
Save the file, and then open it in Sc2. You are now localized- save the file somewhere else as a normal sc2map.
It's actually really simple once you get it, and it's much better than using the localizer (localizer causes a huge file size and potential bugs)
Rollback Post to RevisionRollBack
Feel free to Send me a PM if you have any questions/concerns!
The localizer inside the sc2 editor doesn't seem to work but the one you can download from sc2mapster does, I used it for Hive Keeper and it works! http://www.sc2mapster.com/assets/sc2-localizer/
If it didn't work for you it's probably because the program failed to detect the starting localization that must be copied to the others, go in the options and specify your current editor localization and it should work fine!
The localizer inside the sc2 editor doesn't seem to work but the one you can download from sc2mapster does, I used it for Hive Keeper and it works! http://www.sc2mapster.com/assets/sc2-localizer/
If it didn't work for you it's probably because the program failed to detect the starting localization that must be copied to the others, go in the options and specify your current editor localization and it should work fine!
Still, the localizer produces huge amounts of unneeded texts and unnecessarily increases your file size by a lot. I recommend the method zeldarules explained. Also, you need to run the localizer everytime you publish, while the other method is a one time thing, if you don't work on the map using multiple language versions of the editor.
No- if you only have 1 language file in your map, sc2 will automatically use that language and there will be no problems. EVEN if you use, say, enUS in the EU region. Localization problems appear only when you have multiple languages- if your text is divided between 2 different languages, the editor can still only use 1. So if half your triggers are in US and half are in EU, whichever region it picks will leave out half the text. The sc2 localizer program (afaik) takes all these files and COPIES them a million times into all the different languages- which means you have a ton of language files instead of just 4.
So no, you just do it once, and then publish that map to everywhere. You will only need to do it more than once if you plan on working with partners in different regions.
Actually I had problems in the past that made my EN-GB map unreadable when published on NA servers where EN-US was used.
However I always used one single localization but it never worked on others :|
How do i localize maps
Tutorials are outta date, and the localizer doesnt seem to work for me whatsoever, it changes things but doesnt make anything work...
@Taintedwisp: Go
Here's what ya do if you are converting the map from language A to language B:
Here's what you do if you are merging 2 languages into 1 (say, if people form multiple regions worked on the map). Note that you will be modifying some important data, so make a backup, PLEASE.
It's actually really simple once you get it, and it's much better than using the localizer (localizer causes a huge file size and potential bugs)
@zeldarules28: Go
Alright THanks i'll try it tomorrow
And since its a group project the newest version is in the Personal messag ebox at all times :D
Edit: COULDNT WAIT!!!, THANK YOUS SOOO MUCH!!!, The only problem is i gotta rename the triggers which is NOTHING at all :d
and the 2 guys who are working with me on this project are EU so now That I know how to do this it is much easier.
The localizer inside the sc2 editor doesn't seem to work but the one you can download from sc2mapster does, I used it for Hive Keeper and it works!
http://www.sc2mapster.com/assets/sc2-localizer/
If it didn't work for you it's probably because the program failed to detect the starting localization that must be copied to the others, go in the options and specify your current editor localization and it should work fine!
Still, the localizer produces huge amounts of unneeded texts and unnecessarily increases your file size by a lot. I recommend the method zeldarules explained. Also, you need to run the localizer everytime you publish, while the other method is a one time thing, if you don't work on the map using multiple language versions of the editor.
@Kueken531: Go
I used that localizer,
The file stayed the same, But it erased part and the totally screwed up the leaderboard.
The way zelda said worked perfect.
Plus its so easy, there wasn''t any need for a program it took like 45 seconds.
I didn't get his method, does it require to do the process with each of the available SC2 localizations?
@Bibendus: Go
No- if you only have 1 language file in your map, sc2 will automatically use that language and there will be no problems. EVEN if you use, say, enUS in the EU region. Localization problems appear only when you have multiple languages- if your text is divided between 2 different languages, the editor can still only use 1. So if half your triggers are in US and half are in EU, whichever region it picks will leave out half the text. The sc2 localizer program (afaik) takes all these files and COPIES them a million times into all the different languages- which means you have a ton of language files instead of just 4.
So no, you just do it once, and then publish that map to everywhere. You will only need to do it more than once if you plan on working with partners in different regions.
@Taintedwisp: Go
You shouldn't have had to rename your triggers O.o You might have missed a section of a file. But I'm glad it worked ;)
I'll try to create a tutorial with pictures and whatnot soon, if there isn't one already.
Actually I had problems in the past that made my EN-GB map unreadable when published on NA servers where EN-US was used.
However I always used one single localization but it never worked on others :|
anyone know if i can join more than one team
@CRAZYWARPIG: Go
uhhh trollin much? that was your first post lawl.
to answer your irrelevant post yes you can join lots of teams.