[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
use translation context for translations of in-document strings?
From: |
Patrice Dumas |
Subject: |
use translation context for translations of in-document strings? |
Date: |
Sat, 5 Nov 2022 17:25:07 +0100 |
Hello,
It will become possible to add translation context to in-document
translated strings in developments to come. I am not sure in which
situations it will be better to use contexts to be clearer on the
intended use of a translated string. In particular there are, for HTML,
many direction strings translations that can be used in different
contexts and may have the same words to translate. For example,
'Index' is translated in 3 different contexts:
* to represent a button label,
* as a short text for the direction,
* or as the longer direction description
For other strings, there could be differences in the different contexts,
for example, for the Contents directions, it is 'Contents' for the
button label and the short text, but is 'Table of contents' for the
description.
My feeling is that it is better to add context for those situations for
languages in which this is relevant, even if it makes more work for the
translators as they will have to translate 2 or 3 strings instead of 1
or two.
Another context that could be added when there is some translation would
be to give an idea on the command being associated with the translation,
or the class of command. For example there is '{number} {section_title}'
to be translated, which is for a section number, I am not sure that
'{number} {section_title}' is explicit, maybe adding a context, like
'sectioning command' would be better.
Any advice?
--
Pat
- use translation context for translations of in-document strings?,
Patrice Dumas <=