-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
single quote ' in translation string breaks ui_app.jade #10580
Comments
Note that in the welcome message, {
"UI-WELCOME_MESSAGE": "En chargeant Kibana, s'il vous plait!",
"UI-WELCOME_ERROR": "Kibana n'a pas chargé correctement. Vérifiez le rendement du serveur pour plus d'information."
} I wonder if it should be |
@srl295 Good catch, thanks. This would have been a silent issue until Phase 4, so it is good that you could do some testing with other languages that introduce single quotes. It only applies to To show this message the server would need to be killed as welcome/loading page is in progress. Then the error page would be loaded. |
@hickeyma to be clear, the error prevents Kibana page startup… it's not just a broken message when the server is killed at the right time. |
@srl295 My bad on #10580 (comment). It ewas the way I was testing the issue initially. |
Closing this as we’re moving to a different localization system which should address this problem. |
Kibana version: master (6.0.0 alpha, 7084d55)
Original install method (e.g. download page, yum, from source, etc.): source
Description of the problem including expected versus actual behavior:
French translation with a single quote breaks startup page, because
UI-WELCOME_ERROR
is substituted into the inline script without escaping.The specific translation bundle (
plugins/kibana_translation/translations/fr.json
) looks like this:Steps to reproduce:
plugins/kibana_translation/…
)npm run start
fr
)Errors in browser console (if relevant):
The specific line is:
This is caused by the source in
ui_app.jade
:I think this can be corrected with some escaping. Probably using
JSON.stringify
as elsewhere on the same page.The text was updated successfully, but these errors were encountered: