PCSX2 Documentation/Translation Guide: Difference between revisions

Jump to navigation Jump to search
m
a wee better
(Updated all links, should be useful now.)
m (a wee better)
 
(2 intermediate revisions by 2 users not shown)
Line 13: Line 13:
Fortunately there are tools now available to make editing .po files easier. The recommended tool for creating and updating .po files is Poedit. It's an open source app that makes using gettext (usually a terse command line tool) almost a pleasurable experience. Since I personally have no earthly idea how to use gettext, and have only ever used Poedit, the rest of this quick tutorial will read as if Poedit is the only way to actually get the job done.
Fortunately there are tools now available to make editing .po files easier. The recommended tool for creating and updating .po files is Poedit. It's an open source app that makes using gettext (usually a terse command line tool) almost a pleasurable experience. Since I personally have no earthly idea how to use gettext, and have only ever used Poedit, the rest of this quick tutorial will read as if Poedit is the only way to actually get the job done.


See our UsingPoedit page for details on how to download, install, and configure Poedit.
See our [[PCSX2 Documentation/Using Poedit|Using Poedit]] page for details on how to download, install, and configure Poedit.


==PCSX2-specific Extension: Iconized gettext Identifiers==
==PCSX2-specific Extension: Iconized gettext Identifiers==
Line 66: Line 66:
When you're done, you will be given the rights to post in the specific forum for the language you translated into in our board. There you can attach either the actual PO file archive you have created, or a patchfile that can be applied against the current svn copy of the translation.
When you're done, you will be given the rights to post in the specific forum for the language you translated into in our board. There you can attach either the actual PO file archive you have created, or a patchfile that can be applied against the current svn copy of the translation.


For those of you who are familiar and comfortable with Subversion (SVN): The PCSX2 Team hosts all available translations from our googlecode repository. Available translations and their submission history can be viewed online at https://pcsx2.googlecode.com/svn/trunk/locales/. You can also use an Svn tool such as TortoiseSvn to perform more detailed commit history analysis.
For those of you who are familiar and comfortable with Github: The PCSX2 Team hosts all available translations from our github repository. Available translations and their submission history can be viewed online at https://github.com/PCSX2/pcsx2/tree/master/locales/templates. You can also use an Git tool such as Git for windows to perform more detailed commit history analysis.


Translations are branched according to the releases of PCSX2 that they conform to.
Translations are branched according to the releases of PCSX2 that they conform to.
67,565

edits

Navigation menu