Добро пожаловать, Гость. Пожалуйста авторизуйтесь здесь.
FGHIGate на GaNJa NeTWoRK ST@Ti0N - Просмотр сообщения в эхоконференции FTSC_PUBLIC
Введите FGHI ссылку:


Присутствуют сообщения из эхоконференции FTSC_PUBLIC с датами от 13 Sep 13 18:57:24 до 15 Nov 24 00:30:01, всего сообщений: 7128
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 624 из 7128 ======================================= FTSC_PUBLIC =
От   : Kees van Eeten                   2:280/5003.4       27 Nov 13 22:29:38
Кому : Roy Witt                                            27 Nov 13 22:29:38
Тема : Extended character sets
FGHI : area://FTSC_PUBLIC?msgid=2:280/5003.4+529665ef
На   : area://FTSC_PUBLIC?msgid=1:387/22+52955d8b
= Кодировка сообщения определена как: LATIN-1 ================================
==============================================================================
Hello Roy!

26 Nov 13 20:47, you wrote to me:

RW> I'm by far no authority on this subject, but Unicode is a 16-bit codepage,
RW> ISO-10646 is a 32-bit codepage (which uses the characters defined by
RW> Unicode as a linear sub-set), but UTF-8 is no codepage at all.

RW> i.e. it's just a method used to tunnel 16-bit or 32-bit binary data
RW> streams through an 8-bit wide channel. (There are similar univeral
RW> transfer encoding methods for 16-bit and 7-bit systems, e.g. UTF-7, and
RW> UTF-16).

 Whatever you are trying to explain here, text encoded in UTP-8 has 8 and
 16 bit characters intermixed. Just check on messages by Michiel with
 Bjorns name in it. Written with o umlaut. As may have shown converting
 this 16 bit character produces two characters on systems that cannot
 handle UTF-8 conversion to the local set.

Kees

--- FPD v2.9.040207  GoldED+/LNX 1.1.5
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

К главной странице гейта
Powered by NoSFeRaTU`s FGHIGate
Открытие страницы: 0.049738 секунды