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


Присутствуют сообщения из эхоконференции FTSC_PUBLIC с датами от 13 Sep 13 18:57:24 до 01 Aug 24 00:39:47, всего сообщений: 7127
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 629 из 7127 ======================================= FTSC_PUBLIC =
От   : Michiel van der Vlist            2:280/5555         28 Nov 13 00:46:46
Кому : Kees van Eeten                                      28 Nov 13 00:46:46
Тема : UTF-8
FGHI : area://FTSC_PUBLIC?msgid=2:280/5555+52968570
На   : area://FTSC_PUBLIC?msgid=2:280/5003.4+5296509d
= Кодировка сообщения определена как: UTF-8 ==================================
Ответ: area://FTSC_PUBLIC?msgid=2:5020/545+52a566de
==============================================================================
Hello Kees,

On Wednesday November 27 2013 20:56, you wrote to me:

MvdV>> UTF-8 and 7 bit only can co-exist and so they will.

KE>  And will feed numerous disputes, when cut and paste operations will
KE>  produce Bjerk and Mjerk.

Sure. He who wants to beat a dog, will always find a stick. That is no reason to ban all sticks. Banning sticks from the forst isn't practical either.

KE> It is nice if Bjorn get his umlaut. But the o umlaut does not have a
KE> a fixed position in the code table, so then we can have a dispute
KE> about the wich encoding to use. The group that can benefit most, will
KE> be in R50, but then Bjorn still does not have his o umlaut.

If sysops are allowed to have their name (or their city) properly spelled
in their own alphabet, all should have equal opportunity. If Björn is allowed a
Swedish character, then the Russians should be allowed to have their name in
Cyrillic in the nodelist.

We know this can't be realised with just one eight bit character encoding
scheme and I do not see how a mixed encodig scheme can be made to work. The
only logical solution that favours no one is UTF-8.

KE>  Moving to UTF-8 could be a solution, but leads to interesting times.

I love interesting times...


Cheers, Michiel

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

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