snes9x/gtk/po
StanleyKid-22 4336892724
Updated Ukrainian translation
2024-02-14 15:47:32 +02:00
..
POTFILES.in * Add plurals 2023-10-30 15:46:21 +01:00
README.md Add GTK+ pl translations 2023-08-31 11:42:32 +02:00
de.po Add de l10n 2023-11-18 19:28:18 +01:00
es.po Gtk: Fix some missing lines again. 2023-03-21 17:41:08 -05:00
fr_FR.po Merge branch 'master' into master 2020-06-30 14:13:50 -05:00
ja.po Merge branch 'master' into master 2020-06-30 14:13:50 -05:00
pl.po * Add plurals 2023-10-30 15:46:21 +01:00
pt_BR.po Updated brazilian portuguese translation 2023-03-22 11:54:04 -03:00
ru.po Merge branch 'master' into master 2020-06-30 14:13:50 -05:00
snes9x-gtk.pot * Add plurals 2023-10-30 15:46:21 +01:00
sr@latin.po Merge branch 'master' into master 2020-06-30 14:13:50 -05:00
uk.po Updated Ukrainian translation 2024-02-14 15:47:32 +02:00
updatepot.sh Add de l10n 2023-11-18 19:28:18 +01:00
zh_CN.po Update version and copyright for 1.61. 2022-01-30 17:52:50 -06:00

README.md

Adding a New Language or Updating Existing Ones

  1. Generate the template file. Run the shell script updatepot.sh or change to the gtk directory and run:

    xgettext -f po/POTFILES.in --from-code=UTF-8 -o po/snes9x-gtk.pot -kmaybegettext -k_
    

    This will update the snes9x-gtk.pot file in this directory with the latest strings.

    • Use the program “poedit” with this template or your favorite text editor with a spell checker to create a new translation or,
    • merge the templates new strings into an existing .po file with msgmerge first and then edit the new .po file.
  2. In order to test your translations, you will have to build the message catalog and install Snes9x. Add the language code for your language to the list on the line in gtk/CMakeLists.txt beginning with:

    # Add any new language to this foreach loop
    foreach(lang es fr 
    

How to Add Language Files and What to Translate

Please avoid suffixing your language code with a region code unless it is absolutely necessary. In other words, if you know of any region specific distinctions in your language then and only then add the affected messages exclusively in a xx_XX.po file. Do not duplicate all messages from the base xx.po language file in a xx_XX.po language file but only translate region specific messages.

Source File Encoding

Make sure all source files are UTF-8 encoded.