[JIRA] Created: (MAGNOLIA-2929) Enhance unicode support
|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
 |
[JIRA] Created: (MAGNOLIA-2929) Enhance unicode support
by JIRA (on behalf of Jan Haderka)
::
Rate this Message:
Enhance unicode support ----------------------- Key: MAGNOLIA-2929 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2929 Project: Magnolia Issue Type: Improvement Components: core Reporter: Grégory Joseph Assignee: Grégory Joseph Fix For: 4.2 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 insance). Node name normalization unfortunately requires using either Java 6 ([{{java.text.Normalizer}}|http://java.sun.com/javase/6/docs/api/java/text/Normalizer.html]), the [ICU4J library|http://www.icu-project.org/]; 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <dev-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
[JIRA] Work started: (MAGNOLIA-2929) Enhance unicode support
by JIRA (on behalf of Jan Haderka)
::
Rate this Message:
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MAGNOLIA-2929 started by Grégory Joseph. > Enhance unicode support > ----------------------- > > Key: MAGNOLIA-2929 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2929 > Project: Magnolia > Issue Type: Improvement > Components: core > Reporter: Grégory Joseph > Assignee: Grégory Joseph > Fix For: 4.2 > > > 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 insance). > Node name normalization unfortunately requires using either Java 6 ([{{java.text.Normalizer}}|http://java.sun.com/javase/6/docs/api/java/text/Normalizer.html]), the [ICU4J library|http://www.icu-project.org/]; 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <dev-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
[JIRA] Commented: (MAGNOLIA-2929) Enhance unicode support
by JIRA (on behalf of Jan Haderka)
::
Rate this Message:
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24752#action_24752 ] Hudson CI server commented on MAGNOLIA-2929: -------------------------------------------- Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! [magnolia_main-trunk #1077|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1077/] introducing a wrapper/helper for unicode normalization > Enhance unicode support > ----------------------- > > Key: MAGNOLIA-2929 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2929 > Project: Magnolia > Issue Type: Improvement > Components: core > Reporter: Grégory Joseph > Assignee: Grégory Joseph > Fix For: 4.2 > > > 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 insance). > Node name normalization unfortunately requires using either Java 6 ([{{java.text.Normalizer}}|http://java.sun.com/javase/6/docs/api/java/text/Normalizer.html]), the [ICU4J library|http://www.icu-project.org/]; 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <dev-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
[JIRA] Commented: (MAGNOLIA-2929) Enhance unicode support
by JIRA (on behalf of Jan Haderka)
::
Rate this Message:
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24753#action_24753 ] Hudson CI server commented on MAGNOLIA-2929: -------------------------------------------- Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! [magnolia_main-trunk #1078|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1078/] Added default implementation for UnicodeNormalizer$Normalizer in mgnl-beans.properties > Enhance unicode support > ----------------------- > > Key: MAGNOLIA-2929 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2929 > Project: Magnolia > Issue Type: Improvement > Components: core > Reporter: Grégory Joseph > Assignee: Grégory Joseph > Fix For: 4.2 > > > 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 insance). > Node name normalization unfortunately requires using either Java 6 ([{{java.text.Normalizer}}|http://java.sun.com/javase/6/docs/api/java/text/Normalizer.html]), the [ICU4J library|http://www.icu-project.org/]; 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <dev-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
[JIRA] Commented: (MAGNOLIA-2929) Enhance unicode support
by JIRA (on behalf of Jan Haderka)
::
Rate this Message:
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24754#action_24754 ] Hudson CI server commented on MAGNOLIA-2929: -------------------------------------------- Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/yellow.gif! [magnolia_main-trunk #1079|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1079/] Added \p{Mn} to the list of allowed characters so that unicode paths in the decomposed form don't trigger irrelevant AccessDeniedException > Enhance unicode support > ----------------------- > > Key: MAGNOLIA-2929 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2929 > Project: Magnolia > Issue Type: Improvement > Components: core > Reporter: Grégory Joseph > Assignee: Grégory Joseph > Fix For: 4.2 > > > 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 insance). > Node name normalization unfortunately requires using either Java 6 ([{{java.text.Normalizer}}|http://java.sun.com/javase/6/docs/api/java/text/Normalizer.html]), the [ICU4J library|http://www.icu-project.org/]; 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <dev-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
[JIRA] Updated: (MAGNOLIA-2929) Enhance unicode support
by JIRA (on behalf of Jan Haderka)
::
Rate this Message:
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Haderka updated MAGNOLIA-2929: ---------------------------------- 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}}|http://java.sun.com/javase/6/docs/api/java/text/Normalizer.html]), the [ICU4J library|http://www.icu-project.org/]; 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. was: 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 insance). Node name normalization unfortunately requires using either Java 6 ([{{java.text.Normalizer}}|http://java.sun.com/javase/6/docs/api/java/text/Normalizer.html]), the [ICU4J library|http://www.icu-project.org/]; 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. > Enhance unicode support > ----------------------- > > Key: MAGNOLIA-2929 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2929 > Project: Magnolia > Issue Type: Improvement > Components: core > Reporter: Grégory Joseph > Assignee: Grégory Joseph > Fix For: 4.2 > > > 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}}|http://java.sun.com/javase/6/docs/api/java/text/Normalizer.html]), the [ICU4J library|http://www.icu-project.org/]; 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <dev-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
[JIRA] Work stopped: (MAGNOLIA-2929) Enhance unicode support
by JIRA (on behalf of Jan Haderka)
::
Rate this Message:
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MAGNOLIA-2929 stopped by Grégory Joseph. > Enhance unicode support > ----------------------- > > Key: MAGNOLIA-2929 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2929 > Project: Magnolia > Issue Type: Improvement > Components: core > Reporter: Grégory Joseph > Assignee: Grégory Joseph > Fix For: 4.3 > > > 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}}|http://java.sun.com/javase/6/docs/api/java/text/Normalizer.html]), the [ICU4J library|http://www.icu-project.org/]; 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <dev-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
[JIRA] Updated: (MAGNOLIA-2929) Enhance unicode support
by JIRA (on behalf of Jan Haderka)
::
Rate this Message:
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégory Joseph updated MAGNOLIA-2929: ------------------------------------- Fix Version/s: 4.3 (was: 4.2) 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 > Enhance unicode support > ----------------------- > > Key: MAGNOLIA-2929 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2929 > Project: Magnolia > Issue Type: Improvement > Components: core > Reporter: Grégory Joseph > Assignee: Grégory Joseph > Fix For: 4.3 > > > 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}}|http://java.sun.com/javase/6/docs/api/java/text/Normalizer.html]), the [ICU4J library|http://www.icu-project.org/]; 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <dev-list-unsubscribe@...> ---------------------------------------------------------------- |
| Free embeddable forum powered by Nabble | Forum Help |
