Opened 5 years ago

Last modified 5 years ago

#3833 new enhancement

Validate tags in GUI string translations

Reported by: fcxSanya Owned by:
Priority: Nice to Have Milestone: Backlog
Component: Internationalization & Localization Keywords:
Cc: Patch:


GUI strings may include tags (for example [font="<...>"]), so the text renderer is trying to parse sequences starting from [ character as tags, what results in errors if translators lose the escape character \ before [ (examples: #3706 and #3831). Currently such issues are likely to stay unnoticed until someone will open a corresponding GUI page using a language with broken translation. It's preferable to perform an automated check before releases, like it's already done for links (see ReleaseProcessDraft: Translation check).

Change History (3)

comment:1 by Itms, 5 years ago

Similar: #4250.

comment:2 by Itms, 5 years ago

Another possibility of breakage: writing [font = "<...>"] (with extra spaces) will fail.

comment:3 by Itms, 5 years ago

In 18902:

Fix some issues with the manual translations, refs #3833. On top of a quick manual check, translations have been automatically checked for spam.

Note: See TracTickets for help on using tickets.