[MAGNOLIA-2929] Enhance unicode support Created: 05/Nov/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Won't Do Votes: 0
Labels: i18n, unicode
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
causality
is causing MAGNOLIA-3150 SimpleUrlPattern do not accept all th... Closed
dependency
is depended upon by MGNLWEBDAV-18 Unicode support Closed
relation
is related to MGNLWEBDAV-15 Node names aren't validated before cr... Closed
is related to MAGNOLIA-3009 Add support for extended characters f... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MAGNOLIA-2943 Provide a simple wrapper around java.... Sub-task Closed Magnolia International  
MAGNOLIA-2944 Relax SimpleUrlPattern so that it doe... Sub-task Closed Magnolia International  
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

In light of MGNLWEBDAV-15, we need Magnolia to be a little more lax with unicode names.

There are two sides to this issue:

  • the current SimpleUrlPattern implementation chokes on paths with unicode characters in the decomposed form.
  • Jackrabbit does no unicode normalization for node names, thus a node created with a name in the composed form can not be retrieved by using the decomposed form of the exact same name.

Since "clients" tend to use one or the other form arbitrarily (Firefox 3.0 on MacOSX sends GET parameters in the NFD form, Safari in NFC; while the Linux OS tends to favor NFC and OSX tends to favor NFD, for instance).

Node name normalization unfortunately requires using either Java 6 (java.text.Normalizer), the ICU4J library; there might be other implementations out there, so we should leave the option open to swap for another one.

See http://en.wikipedia.org/wiki/Unicode_equivalence#Normal_forms for background information.



 Comments   
Comment by Magnolia International [ 09/Nov/09 ]

The above has been done for 4.2; for actual support in AdminCentral, there's more work involved, which might not entirely possible before we have our new ui framework in place:
http://confluence.magnolia-cms.com/display/DEV/Unicode+support+status

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:41:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.