[ https://issues.apache.org/jira/browse/OAK-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15532264#comment-15532264 ]
Julian Reschke commented on OAK-4857: ------------------------------------- Well, there are some: 1) The repo may need to put identifiers into contexts where they now might need escaping - for instance, we previously had problems because code made the (incorrect) assumption that it's ok to delimit identifiers by LF. 2) The repo might be restricted by the persistence layer with respect to what IDs it can persist - that affects leading and trailing whitespace (think RDBs) and broken surrogate pairs (affects Mongo). > Support space chars common in CJK inside node names > --------------------------------------------------- > > Key: OAK-4857 > URL: https://issues.apache.org/jira/browse/OAK-4857 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core > Affects Versions: 1.4.7, 1.5.10 > Reporter: Alexander Klimetschek > Attachments: OAK-4857-tests.patch > > > Oak (like Jackrabbit) does not allow spaces commonly used in CJK like > {{u3000}} (ideographic space) or {{u00A0}} (no-break space) _inside_ a node > name, while allowing some of them (the non breaking spaces) at the _beginning > or end_. > They should be supported for better globalization readiness, and filesystems > allow them, making common filesystem to JCR mappings unnecessarily hard. > Escaping would be an option for applications, but there is currently no > utility method for it > ([Text.escapeIllegalJcrChars|https://jackrabbit.apache.org/api/2.8/org/apache/jackrabbit/util/Text.html#escapeIllegalJcrChars(java.lang.String)] > will not escape these spaces), nor is it documented for applications how to > do so. -- This message was sent by Atlassian JIRA (v6.3.4#6332)