-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handling correspondence with related messages #316
Comments
I think that you can resolve both cases using selectors. For instance:
|
So, for the first issue, you could have a term for
There are caveats about this detailed in https://discourse.mozilla.org/t/on-message-and-termreferences/53217. For the solution for the second case probably falls more in the realm of dynamic term references. The proposal @macabeus made has challenges that dynamic term references face as well, the interface of the message isn't language-dependent, but intended to span localizations. Which |
Hi, I recently discovered this project and find it quite promising. As it focuses on natural-sounding translation, I'm curious whether it can handle the case that a message has different translations according to another message used together, on the translator's side.
A possible use case is such a dialog below:
where some languages don't have exact words for "Yes" and "No", so that they should be most naturally stated as if in English:
and the verb obviously needs to be changed along with the question.
So far I haven't found a way to achieve it without coder's intervention. Is it currently possible? If not, is it implementable? Of course, the source string should be WET, but in such a case I suppose devs won't even likely imagine that it could break down to multiple notions in another language.
Another possible use case:
Japanese has (and only has) one general word for creatures making their characteristic sound, thus the developer gives a single source string:
where
$animal
takes finite options, say [cat, mouse, dog, duck, human]. But in English you have to translate each differently as:The text was updated successfully, but these errors were encountered: