Content Ex/Im: Documents are not imported into folders with upper case characters in their name, new folder is created instead with all lower case chars

While using the Exim plugin, the following was noticed.
 
 
a document named:  section-jackpot-spiele placed in the following path *https://myhost.server.lan/cms/content/path/content/documents/games/Jackpot-Spiele/section-jackpot-spiele*; notice the capital J and S in the path
 
Upon exporting the document using the EXIM plugin REST Endpoint, the exported json contains the following jcr:path: /content/documents/games/Jackpot-Spiele/section-jackpot-spiele, notice the proper J and S. Also, in the zip file which contained the json file, the folders had the proper capitalization.
 
Importing the same previously exported json back into the CMS using the EXIM plugin REST Endpoint, the following happens:
a folder named jackpot-spiele (all lower case) will be created under /games/ folder, and the section-jackpot-spiele file is imported in the newly created folder.
*https://myhost.server.lan/cms/content/path/content/documents/games/jackpot-spiele/section-jackpot-spiele* ; notice the lowercase j and s.
 
my question is: Is this the intended behavior of the exim plugin? to always create lowercase paths for imported documents? This could be confirmed by the  org/onehippo/forge/content/exim/core/util/ContentPathUtilsTest.java which contains the following test: 
 

nodePath="/content/documents/MyHippoProject/a/b/C/d/E";
assertEquals("/content/documents/MyHippoProject/a/b/c/d/e",ContentPathUtils.encodeNodePath(nodePath));
 

 
If so, then, is it a problem that in my hippo instance we have document paths that contain the upper case characters?
 
My expected behavior would be that the exported document be placed in the same folder from which it was exported

HippoCMS version 14.7.3
ExIm Verision: 4.0.1