Thanks fior the link:
The page is pretty well done already.
Here are the few first changes I'd bring if you agree:
Which tools will I need to have?
You will need a simple text editor. Or, if you want to get fancy, there are PO file editing tools out there (you will be editing a .po file). PoEdit is an example of such a tool
I'd add a note about the fact that "simple" editors might break the encoding, so the use of poedit should be encouraged.
Location on Linux: txt/$lang/LC_MESSAGES/allacrost.mo
Location on OS X: Allacrost.app/Contents/Resources/translations/$lang/LC_MESSAGES/allacrost.mo
Location on Windows: txt/$lang/LC_MESSAGES/allacrost.mo
In VT, I've changed txt/ by po/ since it was more self-explanatory for me. Can we keep that?
cout << Translate("My name is Claudius.") << endl;
I'll change this to reflect the end of using namespace std; use, I mean:
std::cout << Translate("My name is Claudius.") << std::endl;
EDIT: Nevermind, I saw you wanted to keep that practice.
And finally, there is the general note about svn / autotools not used in VT. What are your plans according autotools, will you switch to cmake or do you prefer
to stay on autotools?
More delicate point, I guess you're going to stay with svn with your fresh low experience with git, or maybe you want to give it a bit more time?
EDIT: Nvermind bis, since I saw you'll keep svn and autotools.