> Translating the same way might make sense for one target language and > not for another, so I didn't speak of forbidding same translations. OTOH > it's quite simple, but possibly not desirable, to forbid different > translations, it's to use the same source text. If two slightly > different (or maybe not so slightly different) wordings are used in > English for what you called "semantically similar" (and I add: not > exactly synonymous) messages, then it is possible to translate them > differently into the languages where the wording difference makes sense.
And this is what actually happened. I bet this error would not appear if English messages were worded similarly: because similarly worded messages are likely to be translated by similarly worded messages in another language *and* they come one after each other. I would not bet if they were not located alongside though: they could get different translations just because different translations look better (it may also be the reason for different wording in English: one looked better in one case, other looked better in the other). I am looking from my point of view (i.e. what would I do if I was translating text) though: beauty matters for me, consistency matters more, but neither will make me remember translation I wrote a hundred lines ago. > I suppose that the fact that "parameter" is first translated "параметр" > out of context makes it difficult to get the target text "значение > параметра" with the appropriate genitive case, where one of the words > comes from a printf (or similar) template and the other from a %s > replacement string. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
