PIKApp/upstream-documentation
Cassowary d472f6348d Update upstream 2023-12-02 11:03:24 -08:00
..
ChangeLog.pre-1-0 Import newer upstream. Update README 2023-09-25 16:53:31 -07:00
ChangeLog.pre-1-2 Import newer upstream. Update README 2023-09-25 16:53:31 -07:00
ChangeLog.pre-2-0 Import newer upstream. Update README 2023-09-25 16:53:31 -07:00
ChangeLog.pre-2-2 Import newer upstream. Update README 2023-09-25 16:53:31 -07:00
ChangeLog.pre-2-4 Import newer upstream. Update README 2023-09-25 16:53:31 -07:00
ChangeLog.pre-2-6 Import newer upstream. Update README 2023-09-25 16:53:31 -07:00
ChangeLog.pre-git Import newer upstream. Update README 2023-09-25 16:53:31 -07:00
MAINTAINERS.upstream Import newer upstream. Update README 2023-09-25 16:53:31 -07:00
NEWS Update upstream 2023-12-02 11:03:24 -08:00
NEWS.pre-2-0 Import newer upstream. Update README 2023-09-25 16:53:31 -07:00
NEWS.pre-2-2 Import newer upstream. Update README 2023-09-25 16:53:31 -07:00
NEWS.pre-2-4 Import newer upstream. Update README 2023-09-25 16:53:31 -07:00
NEWS.pre-2-6 Import newer upstream. Update README 2023-09-25 16:53:31 -07:00
NEWS.pre-2-8 Import newer upstream. Update README 2023-09-25 16:53:31 -07:00
NEWS.pre-2-10 Import newer upstream. Update README 2023-09-25 16:53:31 -07:00
README.upstream Update upstream 2023-12-02 11:03:24 -08:00
README.upstream.i18n Import newer upstream. Update README 2023-09-25 16:53:31 -07:00

README.upstream.i18n

This file contains some important hints for translators.


The current status of the PIKA translation can be checked at

  https://l10n.gnome.org/module/pika


Translation of the Photo and Image Kooker Application is handled by the
GNOME Translation Project (see https://l10n.gnome.org/). If you want to
help, we suggest that you get in touch with the translation team of
your language (see https://l10n.gnome.org/teams/).


PIKA is different

 PIKA is a complex application which has a bunch of scripts and
 plug-ins that all want to be internationalized. Therefore there is
 not one catalog but many. For a full translation of PIKA's UI, you
 will have to add translations for the following catalogs:

   po/pika20.po                                       --  the core
   po-libpika/pika20-libpika.pot                      --  the libpika library
   po-plugins/pika20-std-plugins.pot                  --  the C plug-ins
   po-python/pika20-python.pot                        --  the pypika plug-ins
   po-script-fu/pika20-script-fu.pot                  --  the script-fu scripts
   po-tips/pika20-tips.pot                            --  the startup tips
   po-windows-installer/pika20-windows-installer.pot  --  the windows installer

 If you are looking for the translations of pika-perl, please note that
 pika-perl has been moved into it's own git module called
 pika-perl.


PIKA Tips dialog

 In addition to message catalogs PIKA provides a file with tips that
 are displayed in the Tips dialog. This file is in XML format and can
 be found in the tips directory. The english tips messages are
 extracted from pika-tips.xml.in so translators can use the usual
 tools to create a <lang>.po file that holds the translations. All
 translations are then merged into pika-tips.xml with language
 identifiers taken from the po filename.

 PIKA needs to know what language it should select from pika-tips.xml.
 Therefore, there's the special message "tips-locale:C" in the main
 message catalog that needs to be translated correctly. For a german
 translation of the tips this would look like this:

 #: ../app/dialogs/tips-parser.c:188
 msgid "tips-locale:C"
 msgstr "tips-locale:de"


Localization of third-party plug-ins

 Third-party plug-ins (plug-ins that are not distributed with PIKA)
 can't have their messages in the pika-std-plugins textdomain.  We
 have therefore provided a mechanism that allows plug-ins to install
 their own message catalogs and tell PIKA to bind to that
 textdomain. This is necessary so that PIKA can correctly translate
 the menu paths the plug-in registers. Basically the plug-in has to
 call pika_plugin_domain_add() or pika_domain_plugin_add_with_path()
 before it registers any functions. Have a look at the script-fu
 plug-in to see how this is done in detail.