Question mark

Otto Stolz otto.stolz at uni-konstanz.de
Mon Jun 10 12:33:55 CDT 2024


Привет Юрий,

am 2024-06-10 um 9:00 Uhr hast du geschrieben:
> how difficult and how feasible is it to add a question mark to the 
> Unicode table that would be identical to the regular question mark but 
> usable in Windows operating systems? > Almost all characters prohibited in
> Windows OS have their equivalents in the Unicode table,

If I understand you correctly, you are looking for look-alikes of some 
punctuation characters, and you would like to employ those in
file-names under the Windows operating system. However, this is not
what Unicode is all about.

Windows file-names is not the only instance of a character sequence that 
is bound to some syntactic rule, and Unicode surely cannot be expected 
to cope with all of these uncountable rules.

> allowing the use of characters like "/", "", ":", etc.

The look-alikes (or almost look-alikes) of these characters are no 
“equivalences”; rather they are characters in their own right meant for 
their respective particular purposes. For example, U+2044 “⁄”, the 
fraction slash, is used for composing arbitrary fractions, such as 
“⁴⁄₃”, and it is not, by any means, an equivalence for U+002F “/”, the 
solidus.

> Almost all characters prohibited in Windows OS have their equivalents in the Unicode table

Unicode is much, much more than a bare code table.
You cannot really understand the Unicode Code Table without some 
knowledge of the main text of the Standard. For example, the use of 
punctuation characters is discussed in
<https://www.unicode.org/versions/Unicode15.0.0/ch06.pdf#G7981>.

To assist newcomers, there are introductions, such as 
<https://home.unicode.org/technical-quick-start-guide/>
and FAQ lists, cf. <http://www.unicode.org/faq/>.

Back to your current issue: I guess, the users of a system such as the 
Windows OS should cope with that system’s syntactic rules and not try to 
circumvent them: A file-name, for example, is not only interpreted by 
the system but also by the human user which could be confused by such 
look-alikes. For example, under Windows, the solidus delimits the 
folder-name from the file-name proper; hence, a solidus look-alike would 
lead the human user to the wrong folder so he would not find the 
respective file on his disk or — even worse — confuse it with some other 
file in some other folder.

I hope I could help you.
   Otto




More information about the Unicode mailing list