View Single Post
Old 02-04-2023, 12:20 PM   #321
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
BTRFS filesystem encoding & revised test version

As I stated in my previous post, I suspect it is a BTRFS filesystem encoding issue for CALM. JS was 100% "future-proofed" in that regard (i.e., future operating systems), but CALM had a few holes in it.

I have plugged those holes and added more debugging information to tell us exactly what the filesystem encoding is in your system.

For my Windows 11 system:
Code:
filesystem_encoding is:  utf-8
The BTRFS encoding could easily mess with the upper/lower cases, and a lot more, including transliteration errors in paths. Think of "ASCII versus Unicode" differences.

Attached is a revised test version for you.


Please post a full debug log of your testing.



DaltonST

Last edited by DaltonST; 02-04-2023 at 05:23 PM.
DaltonST is offline   Reply With Quote