Skip to content

Full translation customization #1751

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

Closed
sdirix opened this issue May 12, 2021 · 1 comment
Closed

Full translation customization #1751

sdirix opened this issue May 12, 2021 · 1 comment

Comments

@sdirix
Copy link
Member

sdirix commented May 12, 2021

Offer the possibility to translate any part of JSON Forms
At the moment form labels can only be translated via exchanging JSON Schemas or UI Schemas. Errors can only be translated using ajv-errors. Some parts of the off-the-shelf renderers can't be translated at all.

Describe the solution you'd like
Offer a customization option which allows the user to translate any shown string. This is a simple string -> string transformation. It will be called with the determined label as input. If no translation is given the simple id function is used.

This allows the integration of any translation framework with JSON Forms.

Describe alternatives you've considered
We could also hand over more information to this translation function.

Describe for which setup you like to have the improvement
Framework: [all]
RendererSet: [all]

@sdirix
Copy link
Member Author

sdirix commented Oct 27, 2021

With #1825 it's now possible to fully translate JSON Forms content using the new i18n support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant