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


Присутствуют сообщения из эхоконференции FTSC_PUBLIC с датами от 13 Sep 13 18:57:24 до 01 Aug 24 00:39:47, всего сообщений: 7127
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 1162 из 7127 ====================================== FTSC_PUBLIC =
От   : Michiel van der Vlist            2:280/5555         14 Apr 14 15:54:43
Кому : Kees van Eeten                                      14 Apr 14 15:54:43
Тема : Byte Order Mark
FGHI : area://FTSC_PUBLIC?msgid=2:280/5555+534be9f2
На   : area://FTSC_PUBLIC?msgid=2:280/5003.4+534be363
= Кодировка сообщения определена как: UTF-8 ==================================
Ответ: area://FTSC_PUBLIC?msgid=2:280/5003.4+534bf391
==============================================================================
Hello Kees,

On Monday April 14 2014 15:29, you wrote to me:

MvdV>> How so? What do you mean by "unwanted leakage"? That notepad
MvdV>> inserts a BOM? What is the problem? A BOM can be useful as a
MvdV>> signature to help autodetect UTF-8.

KE>  The BOM as used in your case is part of the embrace and extend
KE> attitude from MS.

Yes. So what is the problem?

KE>  Moreover it has noring to do with UTF-8 it is a UTF-16 fixed
KE> bytelength thing.

It can be useful as a signature for UTF-8 though. From Wikipedia:
http://en.wikipedia.org/wiki/Byte_order_mark

> UTF-8

> The UTF-8 representation of the BOM is the byte sequence 0xEF,0xBB,0xBF.
> A text editor or web browser interpreting the text as ISO-8859-1 or
> CP1252 will display the characters  for this.

> The Unicode Standard permits the BOM in UTF-8,[2] but does not
> require nor recommend its use.[3] Byte order has no meaning in UTF-8,[4]
> so its only use in UTF-8 is to signal at the start that the text stream
> is encoded in UTF-8. The BOM may also appear when UTF-8 data is
> converted from other encodings that use a BOM. The standard also does
> not recommend removing a BOM when it is there, so that round-tripping
> between encodings does not lose information, and so that code that
> relies on it continues to work.[5] [6]

"The Unicode Standard permits the BOM in UTF-8".

What more needs to be said?


Cheers, Michiel

--- GoldED+/W32-MINGW 1.1.5-b20110320
* Origin: http://www.vlist.org (2:280/5555)

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