Re: Question mark

Giacomo Catenazzi via Unicode wrote in
 <[email protected]>:
 |On 11.06.2024 03:38, David Starner via Unicode wrote:
 |> On Mon, Jun 10, 2024, 1:08 PM Piotr Karocki via Unicode 
 |> <[email protected] <mailto:[email protected]>> wrote:
 |> 
 |>     In my humble opinion, only "portable filename character set" should
 |>     be used
 |>     in filenames.
 ...
 |The problem is not about operating systems, but file system, and if you 
 |follow StackOverflow and related sites you see many weird failures. For 
 |your personal files normally it is not a problem: do what you want. But 
 |you may get problems as the file touch a remote filesystem (network 
 |filesystem, including NAS, "the cloud", etc.), but also same filesystem 
 |on different computers (not necessary different operating system), like 
 |"usb pen" and other detachable hard-disks
 |
 |Unix-like systems works usually on bytes (so encoded strings), so fully 
 ...
 |Microsoft uses code units, so if a filename contain invalid Unicode 
 |string (or just not writable), things may get difficult to access. 
 |(single surrogate is most common problem).
 |
 |Typing or also selecting a file not in your locale may be difficult 
 |(also on a GUI: if you see just replacement character, which one is a 
 |text file, and which it is a virus?)
 |
 |PS: Microsoft has over restriction in filename. "Com" is not allowed.

These are special names like "aux"[.any-extension??] which have
a special Microsoft (or DOS?) specific meaning, in each and every
directory (as far as i know).  lpr, nul and whatnot, i think.
Just like /dev/null, /dev/tty in Unix, but without hierarchy.

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)