- Where do I start?
- What do I have to do to make my translations?
- What tools do I have to have?
- What files do I have to create or edit?
- Do I need to look at any code files to do my translations?
- Will my translation work only if I've translated every single string?
- If the original (English) text is updated, is there any way for me to find out so I can update my own translations?
These are the sorts of questions I think we're going to get from our first translators and we should have answers for them before they are even asked. To be clear, I'm speaking strictly about what will our translators need to know. I'm not talking about what we programmers need to know to make translations work in the game. The best solution is to put this information on our wiki and probably have a step-by-step guide for new translators to follow. Battle for Wesnoth, which uses the GNU GetText localization library that we use, has something like this on their wiki right here. So we can look to their wiki pages on translation and mimic it to help us create our own.
Does anyone want to step up and create such a page (or pages) on the wiki?
On another note, I have some questions of my own. Obviously the fewer times we update the original text strings, the better. We don't want to cause our translators to re-do their text multiple times. So will we as a team have any sort of process where we declare certain parts of the text "final" and ready for translation? If we have to make changes or updates to existing strings, will we try to do these text updates in batches rather than intermittently?
This is pretty exciting because from the very beginning of this project we've wanted to make it multi-lingual and we're finally ready to make that happen. I have to confess though I'm feeling very anxious about it. Its something very new to this team and I don't think any of our active members have experience with it. I want to make sure that the new translators that join the team are not frustrated or annoyed with this work.