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

["Alexander Klimetschek (JIRA)" <ji...@apache.org>]

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

Alexander Klimetschek commented on OAK-4857:
--------------------------------------------

OS filesystems:
* https://en.wikipedia.org/wiki/Filename#Comparison_of_filename_limitations
* http://www.comentum.com/File-Systems-HFS-FAT-UFS.html
* Notably, OSX HFS+ only has / as restricted character.

Cross-platform compatible filename tips from Apple: https://support.apple.com/en-us/HT202808

Dropbox: https://www.dropbox.com/en/help/145

Box:
* https://community.box.com/t5/Box-Sync/What-do-problem-file-notifications-in-Sync-4-0-mean/ta-p/82#name
* https://community.box.com/t5/Box-Sync/Which-File-Types-Are-Ignored-Or-Blocked-In-Box-Sync/ta-p/117

Microsoft OneDrive/Sharepoint: https://support.microsoft.com/en-us/kb/2933738

Adobe Creative Cloud Files: https://helpx.adobe.com/creative-cloud/kb/arent-my-files-syncing.html

Apple iCloud (Drive): ???

Google Drive: ???

Google Cloud Platform:
* https://cloud.google.com/storage/docs/naming
* https://cloud.google.com/storage/docs/gsutil/addlhelp/Filenameencodingandinteroperabilityproblems (slightly tooling specific)

Amazon S3: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html


> 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)