[
https://issues.apache.org/jira/browse/JCRVLT-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676885#comment-17676885
]
Konrad Windszus edited comment on JCRVLT-49 at 1/14/23 10:40 AM:
-----------------------------------------------------------------
The filename escaping rules outlined at
https://jackrabbit.apache.org/filevault/vaultfs.html#Filename_escaping already
allow url escaping for every character. That can be leveraged for
case-sensitivity as well, but should only be leveraged in case there is really
a conflict. In that case the first node on the level (no matter if using upper
or lower case characters) does not require escaping but the subsequent nodes
which are conflicting require escaping.
was (Author: kwin):
This requires some special escaping rules (which should be
backwards-compatible) for filenames:
https://jackrabbit.apache.org/filevault/vaultfs.html#Filename_escaping
> Support case-sensitivity on case-insensitive file systems
> ---------------------------------------------------------
>
> Key: JCRVLT-49
> URL: https://issues.apache.org/jira/browse/JCRVLT-49
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: vlt
> Affects Versions: 3.1.6
> Reporter: Konrad Windszus
> Priority: Major
>
> Since JCR distinguishes nodes whose names only differ in terms of lowercase
> and uppercase characters in their name, FileVault should be able to deal with
> that even on case insensitive file systems (like Mac OS by default or on
> Windows).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
