-
Bug
-
Resolution: Fixed
-
High
-
5.1
-
None
-
Confluence 5.1.1, used with german umlauts
When translating the blueprints into german, you have the effect that umlauts that are contained in the instructional text are not saved.
See attachments for a visual "proof" of the problem:
- (a) go as administrator to change a global template
- (b) insert umlauts in the instructional text and elsewhere
- (c) save the template, and edit it again: umlauts are lost in instructional text (but present in the "normal" template text
- (d) created pages from the template also do not contain the "missing" umlauts
This makes this feature nearly unusable in an internationalized environment, at least in germany.
Test notes
- Test umlauts as well as Japanese/Russian characters on text placeholders on new and existing templates
- Insert variables into a template
- Verify the tested characters from step 1 characters show up on template insertion page too
- duplicates
-
-
- Closed
-
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
[CONFSERVER-28971] Instructional text in Blueprints loses umlauts and other characters, when saving
jcorea - the testing notes need to be more specific. You need to test these characters in text placeholders, not just anywhere in the template.
I'm not sure what you're trying to test here
cpetchell - it is part sanity check on template variables, part trigger for the template variables page to verify the characters render OK there. afaik, this should work ok 
2. Insert variables into a template
I'm not sure what you're trying to test here, unless it's potentially bugs in other parts of templates that already exist (and this fix didn't try to address).
don.willis@atlassian.com, iloire - can I pair with whoever does the qr for this? Please just come get me when you are ready. Thanks
StoragePlaceholderUnmarshaller.java. didn't require a fix, as we automatically expand entities on the storage format side (due to it being XML rather than HTML as I understand it).
In tech review now.
Thank you for raising this, and for finding the underlying cause, Gerhard!
This could also be browser-specific, as it would depend on whether the browser sends through entities (ü) or Unicode characters (ü) in the placeholder content.
This bug could possibly affect all characters which can be represented as XML or HTML entities (list). It isn't specific to umlauts or German, so I'll update the issue summary.
Thank you Gerhard Müller for all your help and research on this one. We will take a look at this ASAP and keep this issue updated.
My apologies for the hassles.
Right you are! Have changed the notes. Thanks!