3 ms·
Oh, then this is management issue, not tooling. You need to sit down and analize where your stuff will be developled. Some very basic rules to start with: file
by Borg3 1y ago
Oh, then this is management issue, not tooling. You need to sit down and analize where your stuff will be developled. Some very basic rules to start with: file names need to be all lower case (they are case-insensitive), use 7bit ASCII encoding for source code files. And vioala :)
- bawolff 1y agoWhat exactly is the lowest common denominator platform we are trying to target here where we need 7bit ascii? MS-dos?
- keybored 1y agoCould just be Linux. Filenames are just bytes so two equivalent Unicode filenames that have been normalized differently could be confusing. I guess? I guess since I’m too afraid to use non-ASCII in filenames much.
- bawolff 1y agoI guess that is fair. If i remember right mac uses NFD where literally everyone else in the world uses NFC (linux might not normalize but basically it usually ends up being NFC). That said, i feel like this is something most tooling could just handle, and not really an issue. Certainly its not a problem diffX is going to solve since it appears to only store charset and not filename normalization rules.
- dotancohen 1y agoI had this condition a few years ago. A folder shared with Dropbox was then renormalized either by Dropbox or by another system, then when it was synced back to the original machine I had two folders with identical names, normalized differently. I still have some ls and hd output that I stored in my notes files, if anybody is interested.
- dotancohen 1y agoHere, found it: $ ls Español Español Français Français $ ls | hexdump -C 00000000 45 73 70 61 6e cc 83 6f 6c 0a 45 73 70 61 c3 b1 |Espan..ol.Espa..| 00000010 6f 6c 0a 46 72 61 6e 63 cc a7 61 69 73 0a 46 72 |ol.Franc..ais.Fr| 00000020 61 6e c3 a7 61 69 73 0a |an..ais.| 00000028
- bawolff 1y agoThe first one (6e cc 83) is NFD which is used by mac, the second one (c3 b1) is NFC which is used by everyone else.
- dotancohen 1y agoThanks. I did have a company Mac in 2017, and it was connected to that account.
- Joker_vD 1y ago> I’m too afraid to use non-ASCII in filenames much. I suggest installing a fresh Linux distribution with e.g. bg_BG.UTF-8 locale and playing with it, especially with XDG directories like "Плот", "Свалени" and "Документи", and apps that should use them by default. Everything should Just Work™. Although I admit that when reporting bugs for apps that can't handle non-ASCII paths, the responses from the developers (unless they're themselves from non-English speaking countries, but sometimes even then) quite often seem to be very thinly veiled "I can't be bothered to figure out where I botch things, why can't you just speak English like all reasonable people".
- bawolff 1y agoTo be fair, as far as unicode goes, cryllic is kind of the easy case (no combining characters, no rtl, etc). In some ways its even easier than (non-english) latin scripts because in latin you can get easily confused with windows-1252 where things sort of work where if you are accidentally using a legacy 8bit encoding with cryllic you are more likely to figure that out quickly.
- HelloNurse 1y agoIt's "Cyrillic", named after St. Cyrill.
- theamk 1y agoAny system which uses encodings, including Windows and Linux in non-utf8 locale.
- NavinF 1y agoPoe's law at work. Replies are taking you literally, but I'm almost certain that you're joking. Very few large projects exclusively have lowercase filenames