You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2017/01/19 13:42:26 UTC

[jira] [Comment Edited] (OAK-4857) Support space chars common in CJK inside node names

    [ https://issues.apache.org/jira/browse/OAK-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528875#comment-15528875 ] 

Julian Reschke edited comment on OAK-4857 at 1/19/17 1:41 PM:
--------------------------------------------------------------

use case is storing files in JCR and retain their filename. this is currently not possible, if the filenames contains for example a u3000.


was (Author: tripod):
use case is storing files in JCR and retain thir filename. this is currently not possible, if the filenames contains for example a u3000.

> 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
>            Assignee: Julian Reschke
>             Fix For: 1.8
>
>         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)