-
-
Notifications
You must be signed in to change notification settings - Fork 22k
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
TranslationServer.translate()
non-functional in editor
#98935
Comments
This is expected currently.
Just curious, what's your use case for |
I have a tool that dynamically stitches together a text dynamically based on translated sub-stings. I use that to gradually reveal text as it is spoken. And because the voice lines and text can have different languages, that was the most practical thing to do. Working on that tool is really annoying I must say when the translations are not available in editor. Also: German and English have quite different lengths, so it is really difficult to work on ui when I cannot test with different translations in editor, even when I explicitly force it in code. Also: if no locale is loaded in the editor, then I don't think your workaround works btw:
prints
|
Sorry, I confused the changes I'm making with the stable version / master. I am working on removing the special handling for editor translations, so that the editor's translation workflow is consistent with the game's translation workflow, so that translations can be previewed in the editor and the For your use case, I think you can use |
Tested versions
v4.3.stable.nixpkgs [77dcf97]
System information
nixos-unstable
Issue description
TranslationServer
seems to not work in the editor at all, witch I partly understand, but especially it not working when being explicitly called from script is a hindrance to me right now.Steps to reproduce
EXPECTED:
prints "Es ist Mittwoch, meine Kerle!" both times.
OBSERVED:
only prints the translated message in game.
Minimal reproduction project (MRP)
i18-editor-bug.zip
The text was updated successfully, but these errors were encountered: