[wesnoth-i18n] A Reminder Regarding Wesnoth Translation Hints

F Wolff friedel at translate.org.za
Wed Oct 2 17:49:01 UTC 2019


Op Wo. 28 Aug. 2019 om 00:19 het Steve Cotton <steve at s.cotton.clara.co.uk>
geskryf:

> On Tue, Aug 27, 2019 at 07:19:32PM +0100, Andrius Štikonas wrote:
> > Is there any reason why string substitution can't be used to hide it
> away?
> > i.e. keep string as '[%s|<command>]' and replace %s with 'all' in C++
>
> I agree that the "do not translate" hints should be replaced, and
> acknowledge
> that it's not the same as your suggestion, but pull requests #4276 and
> #4287
> would add replacements with enough space to provide translations of what
> "all"
> means in the player's language.
>
> Example of what's removed:
> - "do not translate the 'all'^[all|<command>]"
>
> Example of what's added:
> + Translators' note: These are the arguments accepted by the "help"
> command,
> + which are either "all" or the name of another command.
> + As with the command's name, "all" is hardcoded, and shouldn't change in
> the translation.
> + "[all|<command>]\n“all” = overview of all commands, <command> = name of
> a specific command (provides more detail)"
>
> I'm hoping this will be better for both players and translators, but I
> don't
> know enough about translation and would appreciate feedback on it.
>

Hi

I'm not sure if I'm following the discussion, but are you aware of the
pgettext functions that specify msgctxt? It is used to disambiguate
otherwise identical strings so that they can be translated differently.
Everything else should be in the comments, I feel.

A sad part of having anything in the msgid that should not be translated,
is that translation memory and quality checking tools break, since they
don't know of the Wesnoth convention. Is pgettext and msgctxt a
possibility? (Sorry if this was already discussed.)

Keep well
Friedel

-- 
https://fwolff.net.za/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.wesnoth.org/pipermail/i18n/attachments/20191002/cab5eb2e/attachment.html>


More information about the i18n mailing list