Details
-
Bug
-
Resolution: Fixed
-
Medium
-
None
Description
It seems like TAC is way too smart when it validates messages that contain a ChoiceFormat
I was unable to provide a translation for:
inviteuser.warning={0} {0,choice,1#invitation was|1<invitations were} sent successfully! {1} {1,choice,1#invitation was|1<invitations were} invalid and {1,choice,1#was|1<were} not sent.
inviteuser.warning={0,choice,1\#¡La invitaci\u00F3n fue enviada con \u00E9xito!|1<¡Se han enviado {0} invitaciones con \u00E9xito!}. {1,choice,1\#Una de las invitaciones no era v\u00E1lida|1< {1} invitaciones no eran v\u00E1lidas} y por lo tanto, {1,choice,1\#no fue enviada|1<no fueron enviadas}.
The validation to be performed should be that the message format is syntactically correct (it can be parsed correctly) and that all variables have been used at least one time in the translation. In this case the variables are 0 and 1
Attachments
Issue Links
- is duplicated by
-
I18N-437 TAC Import check of arguments in the translated message is a bit too strict
- Closed
- is related to
-
JRACLOUD-27909 Update Spanish Translations for JIRA 5.0.3
- Closed
-
JRASERVER-27909 Update Spanish Translations for JIRA 5.0.3
- Closed