-
-
Notifications
You must be signed in to change notification settings - Fork 299
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
Preview for Localisation purposes #1098
Comments
A partial solution is already available in Crowdin. Each translation string can have a picture and description set in the field Context from which translator can more easily understand where the string is shown and in what context. But many of the strings are currently without context in Crowdin. You can request the context via:
This unfortunately does not solve the issue of checking the display of translated string - if it's long / short enough.... |
this is configured as special "pseudo" language in Crowdin and when the user selects to use the app in this language the UI will show Crowdin in-context editor for easier localization.
Crowdin in-context translation for Esperanto uses automatic msgstr which don't have these characters. This in turn causes compilemessages to fail! Note: this is mostly an issue where we use blocktrans and multi-line strings. The solution is to make them look uglier :-(. In the final HTML/email they will be displayed the same.
Crowdin in-context translation for Esperanto uses automatic msgstr which don't have these characters. This in turn causes compilemessages to fail! Note: this is mostly an issue where we use blocktrans and multi-line strings. The solution is to make them look uglier :-(. In the final HTML/email they will be displayed the same.
Crowdin in-context translation for Esperanto uses automatic msgstr which don't have these characters. This in turn causes compilemessages to fail! Note: this is mostly an issue where we use blocktrans and multi-line strings. The solution is to make them look uglier :-(. In the final HTML/email they will be displayed the same.
Crowdin in-context translation for Esperanto uses automatic msgstr which don't have these characters. This in turn causes compilemessages to fail! Note: this is mostly an issue where we use blocktrans and multi-line strings. The solution is to make them look uglier :-(. In the final HTML/email they will be displayed the same.
Django needs this language into the eo/ directory while Crowdin uses a coutry suffix as well.
enables special 'translation mode' by switching the application language to Esperanto. The rest of the integration is provided via Crowdin JavaScript and their special pseudo msgstr mappings. Use ?disable_jipt as URL parameter to turn-off Crowdin mappings!
Django needs this language into the eo/ directory while Crowdin uses a coutry suffix as well.
Django needs this language into the eo/ directory while Crowdin uses a coutry suffix as well.
enables special 'translation mode' by switching the application language to Esperanto. The rest of the integration is provided via Crowdin JavaScript and their special pseudo msgstr mappings. Use ?disable_jipt as URL parameter to turn-off Crowdin mappings!
Please introduce possibility to check somehow the translated strings so that the localisation becomes perfect.
The text was updated successfully, but these errors were encountered: