What fundamental hardware and software limitations can arise for software developers whose task is to develop systems using Cyrillic, as the main character set, instead of common ASCII codes?

PS And are there any examples of such Russified systems?

Closed due to the fact that the issue is too common for Kromster , insolor , rjhdby , Xander , Nofate participants ♦ 21 Mar '17 at 18:24 .

Please correct the question so that it describes the specific problem with sufficient detail to determine the appropriate answer. Do not ask a few questions at once. See “How to ask a good question?” For clarification. If the question can be reformulated according to the rules set out in the certificate , edit it .

  • one
    In my opinion, there is nothing fundamental. The code table corresponds to the symbol table. If you accept the Cyrillic standard type ASCII, then there will be no problems. The problem is that there is no such standard. ASCII regulates only 7 bits (half a table), then there are variations. - DNS
  • 2
    The main (and only) fundamental limitation is that nobody needs it. - Yaant
  • 2
    The limitation is, in fact, one thing - weakened compatibility with ASCII-only-systems. Many existing low-level systems are built without (rather complicated) Unicode support, many C / C ++ programs still do not know how to calculate the length of a Cyrillic string in characters. Since there are a lot of ASCII systems, this will most likely lead to problems. - VladD
  • But what about 1C .... - tCode
  • one
    Imho need to once and for all hammer in iron 16 bits per character and use Unicode - then there will be no problems - Barmaley

0