All geek questions in one place

Why was the ASCII and ISO-8859-1 encoding not related to history?

It seems to me that UTF-8 was the only encoding used everywhere ever, there would be much less code problems:

  • No need to even think about encoding issues.
  • There is no problem with mixed 1-2-byte character transmission, because everything uses 2 bytes.
  • The browser does not need to wait for the tag <meta>that defines the encoding before they can do anything. StackOverflow doesn't even have a meta tag, so browsers first load a full page, slowing down page rendering.
  • You will never see ?other random characters on old web pages (for example, instead of special quotes from Microsoft Word [read: horrible]).
  • Other characters may be represented in UTF-8.
  • Other things I can't think of right now.

So why not shorten the encodings from space?

+3
source share
5 answers
  • No need to even think about encoding issues.

True Except for all data that is still stored in the old ASCII format.

  • There is no problem with mixed 1-2-byte character transmission, because everything uses 2 bytes.

Wrong. UTF-8 is a variable length, from 1 to 6 or so.

  • The browser does not need to wait for the tag that defines the encoding before they can do anything. StackOverflow doesn't even have a meta tag, so browsers first load a full page, slowing down page rendering.

, , .

  • ? - (, Microsoft Word [read: horrible]).

-, , UTF-8 ( - ).

  • UTF-8 .

True. .

+9

EBCDIC, ? - , ?

.

+6

1-2- , 2 .

. UTF-8 1, 2, 3 4 . , UTF-16, 4- . "" , UTF-32.

? -

- UTF-8 , , .

UTF-8.

. , . , - , .. . , Unicode, .

, , , , TI-83 Unicode .

, , UTF-8, , 8- ( ).

, ?

, "" . , C ++ ( COBOL!), Unicode .

, , , char, UTF-8, , char , Unicode wchar_t, , wchar_t UTF-16 UTF-32 ( ).

+1

, UTF-8 "2 " . - UTF-16 UTF-32 , , ASCII ISO-8859-1 .

0

, - , --- . , . , , UTF-8, , UTF-8 UTF-8 -.

, - , . .

There are also many documents on the Internet with non-Unicode encoding in many formats. Someone CAN convert them, but he, as indicated above, requires a lot of effort.

Thus, non-unicode support should also remain.

And for current times, keep as a rule that when someone uses an encoding other than Unicode, the kitten dies.

0
source

Source: https://habr.com/ru/post/1762781/

More articles:


All Articles