Am 01.11.2010 um 11:07 schrieb Kornel Benko:
> Am Montag, 1. November 2010 schrieb Stephan Witt:
>> Am 01.11.2010 um 07:41 schrieb Vincent van Ravesteijn:
>>
>>>> + if (binfo.empty()) {
>>>> + docstring fmt = _("%1$s unknown[[InsetNote]]");
>>>> + setText(bformat(fmt, from_utf8(name_)));
>>>> + } else
>>>
>>> InsetNote ?
>>
>> Sorry. Should be InsetInfo. I mixed it up while trying to fix the
>> latest compile problems, I'll correct that.
>>
>>>
>>> Please remember that this should be helpful for the translators to
>>> correctly translate the unknown part.
>>>
>>> And I have no clue what should be unknown here :S..
>>
>> (The value of the vcs buffer-info inset indexed by name is empty.
>> The replacement in this case is e. g. "vcs-author unknown".
>> The translator has to translate the word "unknown".)
>> I had to lookup your smiley in some smiley table manually ;-)
>>
>> I don't know how to be more helpful to the translator.
>>
>
> For instance "%1$s unknown[[vcs-author]]"
> as that gives a hint to author. In some languages "unknown" depends also on
> gender of "vcs-author"
vcs-author is on case out of:
* vcs-revision
* vcs-tree-revision
* vcs-author
* vcs-date
* vcs-time
These strings will substitute "%1$s" in front of the word unknown.
In case of translations depending on gender one has to think of e. g. "keyword
unknown".
But as I understand gettext that's not the aim of the context. It's used to make
multiple translations for the same string depending of the context in interface.
We may "abuse" it and make the context dynamic:
docstring fmt = _("%1$s unknown[[" + name_ + "]]");
setText(bformat(fmt, from_utf8(name_)));
But that would not work without some N_() magic and then the translator has to
provide 5 translations.
Looks like overkill.
Stephan
