Replies: 1 comment 3 replies
-
I am not sure what is your concern here? Unicode symbols are supported by this library and all the major compilers. They are also the default for all the units that require them. ISO C++ Committee wants Unicode characters as default as well. The only thing that might change here is the actual encoding of a specific character, as the same glyph may often be obtained with a few different Unicode sequences. SG16 promised to help with that when we provide papers with systems of units. Non-unicode alternatives have one big issue. They are not specified in SI or ISO 80000. This means that for many symbols, we do not know what is the best alternative. For example, how to replace Ω with non-Unicode text? Even if we chose something we might not be content with similar but different choices done by other vendors. |
Beta Was this translation helpful? Give feedback.
-
Hey, is there already any committee/expert feedback on unicode names for unit symbols? It appears that both
Ω
andµF
are acceptable as identifiers for both GCC and clang (godbolt). It appears to me that those identifiers should be accepted by any standard-conforming compiler (assuming that the specific unicode symbols here have indeed the XID_Start property), though I'm no expert.It's likely that not everybody would prefer those variants over pure-ascii names, so we could consider supplying both variants. To support users using compilers which do not support such unicode identifiers, there could be demand for a preprocessor switch to disable the unicode variants completely.
Beta Was this translation helpful? Give feedback.
All reactions