@codepo8
Using that feature feels very user-hostile as a decision.
Jargon would have been untranslateable in any case; but it seems to deliberately cause language from one version to hold over. So the word continue, or a title can persist. Why?
It's a technical story, with user stories missing. 🥲
@lewiscowles1986
There’s a number of pretty good examples in the link.
Like preventing translation of the text on a remote control button.
The hardware won’t be translated so users will have to look for “VOLUME” even if their language calls it Lautstärke.
Or source code:
WÄHLE Land VON Benutzern
is not the same as
SELECT country FROM users
@Landa@codepo8
So for code blocks, and incredibly specific product documentation, and propper names.
That one sentence would have stopped me asking. Just re-format the article. I Read the whole thing and thought they were just choosing bizare words to have stay the same. In one of the examples a title was kept.
@lewiscowles1986
I thought the examples were clear enough.
A physical button on a printer is always going to have the text "Continue" so writing about the button should not translate it so one can recognize the button by its appearance, even if one doesn't know what the text means.
If you're writing about HTML, the label element is always going to be written as <label>, not <etichetta>, <etikett>, or another translation of "label." @codepo8
Add comment