pcsx2

History

gregory.hainaut 20958dede3 i18n: use standard pcsx2_Iconize instead of an additional key lookup. In others word, english string is now included directly in the po/pot Translators note: I save previous translation but a careful review is mandatory git-svn-id: http://pcsx2.googlecode.com/svn/trunk@5366 96395faa-99c1-11dd-bbfe-3dabce05a288		2012-08-10 10:10:55 +00:00
..
pcsx2_Iconized.pot	i18n: use standard pcsx2_Iconize instead of an additional key lookup. In others word, english string is now included directly in the po/pot	2012-08-10 10:10:55 +00:00
pcsx2_Main.pot	i18n: use standard pcsx2_Iconize instead of an additional key lookup. In others word, english string is now included directly in the po/pot	2012-08-10 10:10:55 +00:00
readme.txt	Fixed inconsistent newlines / added as many svn:eol-style=native properties as I could without killing myself.	2011-03-25 05:06:49 +00:00

readme.txt

PCSX2 Language Translation Templates (POT format)
-------------------------------------------------

Quick overview of using POT files:

POT files are essentially identical to PO files, except that they have no translated
text strings filled in yet.  Your job as a translator is to make copies of these files,
give then .PO extensions, fill in the properly translated text for each string in the
files, test, and then submit the new PO file to the PCSX2 Team.

The PCSX2 Team recommends using Poedit to help make your life easier.

Details on PCSX2's use of gettext, translation, and tesing/submitting new translations,
visit our wiki at googlecode:  https://code.google.com/p/pcsx2/wiki/TranslationGuide


Jake Stine (Air)
PCSX2 Development Team