[MAGNOLIA-3009] Add support for extended characters for node/page names Created: 14/Jan/10 Updated: 23/Jan/13 Resolved: 15/Mar/10 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Fabrizio Giustina | Assignee: | Fabrizio Giustina |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| 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 |
|
(see also to the bug 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. A preliminary check showed that supported non-standard characters should not be so hard (before the We should probably review all the character-killing methods (like Path.getValidatedLabel() and similar) in order to admin a richer set of chars. |
| Comments |
| Comment by Magnolia International [ 14/Jan/10 ] |
|
Please see http://wiki.magnolia-cms.com/display/DEV/Unicode+support+status and |
| Comment by Jan Haderka [ 15/Jan/10 ] |
|
Something to keep in mind in connection with this as well: http://issues.apache.org/jira/browse/JCR-690 |
| Comment by Fabrizio Giustina [ 15/Mar/10 ] |
|
apart from few reserved chars (e.g. :[]{};.&?) now magnolia supports creating pages with any extended utf8 char when the magnolia.utf8.enabled property is set to true |