Development/Tutorials/Localization/Message Appearance: Difference between revisions

    From KDE TechBase
    m (typo)
     
    (17 intermediate revisions by the same user not shown)
    Line 1: Line 1:
    = What Translators See =
    {{TutorialBrowser|


    This page is a short summary that tries to show how translators see the translatable messages. The information that translators see about a given message also depends on where the message comes from.
    series=Localization|


    For more information one can always look at the template (pot) files. (TODO: Write where they can be found.)
    name=Understanding How Messages Appear to Translators|


    (The idea is that I'll move this page to somewhere once it's at least somewhat useful.)
    pre=[[../i18n|Writing Applications With Localization in Mind]]|


    == Messages coming from i18n() and friends ==
    }}


    For these messages translators will only see the following:
    == Abstract ==
     
    By reading the source code it can be hard to see how translators would see (or not see) the context of a message. This page is a short summary intended mostly for developers that lists the major points of what can be seen from the PO files and gives a few examples.
     
    == Introduction ==
     
    Not all context information that can be seen or figured by reading the source code is extracted to the PO files. Because the amount and type of extracted information depends on from where and how the message is extracted, the rest of this page is divided into different sources of translatable messages.
     
    The goal of this page is only to serve as an introduction and quick reference for this topic. For more information one can always look at the generated template (.pot) files, either by opening them in any text editor or with [http://userbase.kde.org/Lokalize Lokalize]. In KDE infrastructure they can be found in [[Getting_Started/Sources/Subversion|SVN]] under branches/stable/l10n-kde4/templates and trunk/l10n-kde4/templates.
     
    == Messages translated using i18n() and friends ==
     
    For these messages the template files will only contain the following:
    *the source string (and plural form if i18np is used)
    *the source string (and plural form if i18np is used)
    *the context parameter if i18nc is used
    *the context parameter if i18nc is used
    *the code comment beginning with "i18n:" if used
    *the code comment beginning with "i18n:" if used
    *list of file names and row numbers the messages appears in
    *list of file names with row numbers for the locations the message appears in
     
    *the order in which the messages were extracted (sometimes useful, but not a replacement for other context information)
    If the message appears in many places, the context information from all the places is shown.


    For example this message:
    For example this message:
    Line 21: Line 32:
    <syntaxhighlight lang="cpp-qt">
    <syntaxhighlight lang="cpp-qt">
    QString msg = i18nc("%1 and %2 are file names", "Do you want to replace %1 with %2?",
    QString msg = i18nc("%1 and %2 are file names", "Do you want to replace %1 with %2?",
                      oldFile, newFile)
                        oldFile, newFile);
    </syntaxhighlight>
    </syntaxhighlight>


    Appears like this:
    Appears like this in Lokalize:


    <syntaxhighlight lang="gettext">
    [[File:What_Translators_See_i18n.png]]
    #: example.cpp:57
    #, kde-format
    msgctxt "%1 and %2 are file names"
    msgid "Do you want to replace file %1 with file %2?"
    msgstr ""
    </syntaxhighlight>


    (Perhaps have a screenshot of Lokalize here?)
    If the message appears in many places, the context information from all the locations is shown.


    == Messages in UI files ==
    == Messages in .ui files ==


    For these messages translators will see everything that they see for messages coming from i18n() and friends. They will additionally see the following:
    For these messages the template files will contain everything that they contain for messages translated using i18n() and friends. They will additionally contain the following:
    *the type and name of the widget the message it appears in
    *the type and name of the widget the message appears in
    *the name of the property the message is a value for
    *the name of the property the message is a value for


    Examples:
    Examples:


    <syntaxhighlight lang="gettext">
    [[File:What_Translators_See_ui.png]]
    #. i18n: ectx: property (displayFormat), widget (QDateEdit, dateEdit)
    #: mainwindowview.ui:137
    msgid "d/M/yyyy"
    msgstr ""
     
    #. i18n: ectx: property (toolTip), widget (KComboBox, maintypeBox)
    #. i18n: ectx: property (whatsThis), widget (KComboBox, maintypeBox)
    #: mainwindowview.ui:154 mainwindowview.ui:157
    msgid "The main game of the theme"
    msgstr ""
     
    #. i18n: ectx: property (title), widget (QGroupBox, groupBox_2)
    #: conf/dlgeditorbase.ui:19 conf/preferencesdialog.cpp:56
    msgid "Editor"
    msgstr ""
    </syntaxhighlight>


    (Perhaps have some screenshots of Lokalize here?)
    [[File:What_Translators_See_ui2.png]]


    For example from "property (displayFormat), widget (QDateEdit, dateEdit)" it could be inferred that the translatin should use the specific format that QDate's toString() accepts. Some translators cannot infer this, though, so it is good to additionally use "(qtdt-format)" as context as said on page [[Development/Tutorials/Localization/i18n]].
    For example from "property (displayFormat), widget (QDateEdit, dateEdit)" it could be inferred that the translation should use the specific format that QDate's toString() accepts. Some translators cannot infer this, though, so it is a good idea to additionally use "(qtdt-format)" as context as mentioned in [[Development/Tutorials/Localization/i18n|Writing Applications With Localization in Mind]].


    == Messages in .kcfg files ==
    == Messages in .kcfg files ==


    All the things mentioned in the first section also apply here. Additionally the following context information is automatically added:
    For these messages the template files will contain everything that they contain for messages translated using i18n() and friends. They will additionally contain the following:
    *the tag the string is for
    *the tag the string is for
    *the name of the entry the tag is for
    *the name of the entry the tag is for
    *the name of the group the entry belongs to
    *the name of the group the entry belongs to


    Example:
    For example:


    <syntaxhighlight lang="gettext">
    [[File:What_Translators_See_kcfg.png]]
    #. i18n: ectx: label, entry (UseGL), group (View)
    #: kstars.cpp:176 kstars.kcfg:726 kstarsinit.cpp:238 skymap.cpp:1150
    #: skymap.cpp:1158 skymap.cpp:1166
    msgid "Switch to OpenGL backend"
    msgstr ""
    </syntaxhighlight>

    Latest revision as of 03:33, 30 November 2013

    Understanding How Messages Appear to Translators
    Tutorial Series   Localization
    Previous   Writing Applications With Localization in Mind
    What's Next   n/a
    Further Reading   n/a

    Abstract

    By reading the source code it can be hard to see how translators would see (or not see) the context of a message. This page is a short summary intended mostly for developers that lists the major points of what can be seen from the PO files and gives a few examples.

    Introduction

    Not all context information that can be seen or figured by reading the source code is extracted to the PO files. Because the amount and type of extracted information depends on from where and how the message is extracted, the rest of this page is divided into different sources of translatable messages.

    The goal of this page is only to serve as an introduction and quick reference for this topic. For more information one can always look at the generated template (.pot) files, either by opening them in any text editor or with Lokalize. In KDE infrastructure they can be found in SVN under branches/stable/l10n-kde4/templates and trunk/l10n-kde4/templates.

    Messages translated using i18n() and friends

    For these messages the template files will only contain the following:

    • the source string (and plural form if i18np is used)
    • the context parameter if i18nc is used
    • the code comment beginning with "i18n:" if used
    • list of file names with row numbers for the locations the message appears in
    • the order in which the messages were extracted (sometimes useful, but not a replacement for other context information)

    For example this message:

    QString msg = i18nc("%1 and %2 are file names", "Do you want to replace %1 with %2?",
                        oldFile, newFile);
    

    Appears like this in Lokalize:

    If the message appears in many places, the context information from all the locations is shown.

    Messages in .ui files

    For these messages the template files will contain everything that they contain for messages translated using i18n() and friends. They will additionally contain the following:

    • the type and name of the widget the message appears in
    • the name of the property the message is a value for

    Examples:

    For example from "property (displayFormat), widget (QDateEdit, dateEdit)" it could be inferred that the translation should use the specific format that QDate's toString() accepts. Some translators cannot infer this, though, so it is a good idea to additionally use "(qtdt-format)" as context as mentioned in Writing Applications With Localization in Mind.

    Messages in .kcfg files

    For these messages the template files will contain everything that they contain for messages translated using i18n() and friends. They will additionally contain the following:

    • the tag the string is for
    • the name of the entry the tag is for
    • the name of the group the entry belongs to

    For example: