[OAK-4857] Support space chars common in CJK inside item names

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.7, 1.5.10
• Fix Version/s: 1.9.0, 1.10.0
• Component/s: core
• Epic Link: Naming Restrictions
• Assignee: Julian Reschke
• Reporter: Alexander Klimetschek
• Created: 28/Sep/16 00:16
• Updated: 29/Mar/23 15:25
• Resolved: 26/Jan/18 17:38

Description

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 will not escape these spaces), nor is it documented for applications how to do so.

Issue Links

• relates to: OAK-1891 Regression: non-space whitespace not allowed in item names
• relates to: JCR-4917 spi-commons: NameParser is too picky (allow non-ASCII whitespace)
• relates to: JCRVLT-700 package creation fails for node names that are valid in Oak, but invalid in Jackrabbit