[
https://issues.apache.org/jira/browse/JCRVLT-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676889#comment-17676889
]
Julian Reschke edited comment on JCRVLT-49 at 1/14/23 1:20 PM:
---------------------------------------------------------------
FWIW, nowadays it would be more accurate to talk about "case-preserving"
filesytems (NTFS).
There's a related issue with composed and decomposed Unicode forms; JCR in
theory allows a mix (bad idea, FWIW), so mapping these to a filesystem that
standardizes on one form (many do) can create collisions as well.
was (Author: reschke):
FWIW, nowadays it would be more accurate to talk about "case-preserving"
filesytems (NTFS).
There's a related issue with composed and decomposed Unicode forms; JCR in
theory allows a mix (bad idea, FWIW), so mapping these to a filesystem that
standardizes on one form (most do) can create collisions as well.
> 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).
> Note that this isn't a problem in content package archives as entries in ZIP
> archives are always case sensitive.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
