-
Notifications
You must be signed in to change notification settings - Fork 29
🎨 [Frontend] Enh: Wording and .po file #7418
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
Conversation
…into feature/locales
…into feature/locales
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👌
@Mergifyio queue |
🟠 Waiting for conditions to match
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
very nice!
- I took the liberty to link with the issue i had opened for the backend
- why not add some translation (e.g. in Chinese) as a proof-of-concept? Can be flagged as in dev mode only
|
What do these changes do?
In this PR the
en.po
file generated at compilation time is added to the repository. This po file contains all the strings (the ones that are marked for translation:qx.locale.Manager.tr(str)
) the frontend shows to the user.This po file, together with our messages guidelines, was passed to an AI and it proposed some changes.
As proof of concept of how the po files work in the animation you can see what happens when one changes the locale. For the demo, I generated and populated the

en
andde
locale po files:Related issue/s
How to test
Dev-ops