Issue Details (XML | Word | Printable)

Key: CONF-6423
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Thomas Wana
Votes: 0
Watchers: 2
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Confluence

Merge algorithm reliably destroys Umlauts

Created: 22/Jun/06 09:01 AM   Updated: 27/Jun/06 02:39 AM
Component/s: Editing
Affects Version/s: 2.2.1
Fix Version/s: 2.2.5

Time Tracking:
Not Specified

Environment: Sun J2RE 1.5, Apache Tomcat 4.1.31

Participants: Matt Ryall [Atlassian] and Thomas Wana
Since last comment: 3 years, 1 week, 1 day ago
Resolution Date: 27/Jun/06 02:39 AM
Labels:


 Description  « Hide
The merge algorithm when resolving concurrent edits seems to destroy Umlauts (possibly other non-ascii-characters as well). How to reproduce:

Assume you have a page with content "asdfäöü".

User 1 then clicks on edit and waits. User 2 clicks on edit, adds a line, lets say "jkl;" and saves. User 1 then clicks on save too (although he didn't change anything), and the page's content becomes "asdf&#xFC&#xFD&#xFE" (or whatever the LATIN1-codes for Umlauts are). Seems that the merge algorithm destroyed the umlauts.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Matt Ryall [Atlassian] added a comment - 27/Jun/06 02:39 AM
Thanks for the report, Thomas.

This is fixed for 2.2.5.