[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26889#action_26889 ]
Hudson CI server commented on MAGNOLIA-3009: -------------------------------------------- Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! [magnolia_main-trunk #1437|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/1437/] MAGNOLIA-3009 merge back from branch > Add support for extended characters for node/page names > ------------------------------------------------------- > > Key: MAGNOLIA-3009 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3009 > Project: Magnolia > Issue Type: Improvement > Reporter: Fabrizio Giustina > Assignee: Fabrizio Giustina > Fix For: 4.2.x > > > (see also to the bug MAGNOLIA-3008) > Magnolia allow a very reduced set of characters to be used for page names, > replacing everything non-ascii char by "-". This is pretty "aggressive", > since there is no reason to not support for example accented chars or > similar, which are perfectly valid for jcr node names. > Especially for the always increasing importance of URLs for SEO this could be > a relevant problem. > For example if you try to create a page with the name "pietà" the resulting > url is "piet-" which is definitively bad. Also changing the name to "pieta" > is better but not satisfying in terms of SEO. > For asian languages this is even worst, you can't use speaking urls at all, > since all the characters will not be supported. Trying to create a page named > "モクレン" (magnolia in japanese) results in a page named "----.html" which is > definively not user/seo friendly... > A preliminary check showed that supported non-standard characters should not > be so hard (before the MAGNOLIA-3008 related changes actually existing > content with extended chars was already readable by Magnolia). > We should probably review all the character-killing methods (like > Path.getValidatedLabel() and similar) in order to admin a richer set of chars. > If somebody think this could be a big change for a minor version we may > simply add a new system property like "magnolia.allowutf8urls" that can be > enabled explicitly (and that we can enable by default in Magnolia 5) > -- 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-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------