bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Is @emph{See} translatable?


From: Petr Pisar
Subject: Is @emph{See} translatable?
Date: Tue, 26 Sep 2023 21:12:23 +0200

Hello,

when translating texinfo_document-7.0.92 I noticed problem with translating
"See". I wanted to translate the word in these two messages like this:

    # FIXME: "See" should be translatable, but gettext insists that it's an 
identifier.
    #. TRANSLATORS: redirect to another index entry
    #: tp/Texinfo/Convert/HTML.pm:5669
    #, perl-brace-format
    msgid "@code{{main_index_entry}}, @emph{See} @code{{seenentry}}"
    msgstr "@code{{main_index_entry}}, @emph{Vizte} @code{{seenentry}}"

    # FIXME: "See" should be translatable, but gettext insists that it's an 
identifier.
    #. TRANSLATORS: redirect to another index entry
    #: tp/Texinfo/Convert/HTML.pm:5675
    #, perl-brace-format
    msgid "{main_index_entry}, @emph{See} {seenentry}"
    msgstr "{main_index_entry}, @emph{Vizte} {seenentry}"

However, GNU gettext reports an error on them:

    $ msgfmt --statistics --check --strict -o texinfo_document.mo cs.po
    cs.po:854: a format specification for argument 'See' doesn't exist in 
'msgstr'
    cs.po:860: a format specification for argument 'See' doesn't exist in 
'msgstr'

Is the "See" word supposed to be translated? I think it is. Compare to another
meesage which passes the test:

    #. TRANSLATORS: refer to another index entry
    #: tp/Texinfo/Convert/HTML.pm:5692
    #, perl-brace-format
    msgid "@emph{See also} {see_also_entry}"
    msgstr "@emph{Vizte též} {see_also_entry}"

For this time, I kept the strings untranslated to be able to upload the
translation.

-- Petr

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]