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


Присутствуют сообщения из эхоконференции UTF-8 с датами от 19 Apr 14 00:41:48 до 01 Apr 24 00:03:00, всего сообщений: 1367
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 531 из 1367 ============================================= UTF-8 =
От   : Kees van Eeten                   2:280/5003.4       15 Dec 17 16:07:00
Кому : Michiel van der Vlist                               15 Dec 17 16:07:00
Тема : Seasons Greetings
FGHI : area://UTF-8?msgid=2:280/5003.4+5a33ea27
На   : area://UTF-8?msgid=2:280/5555+5a33c15b
= Кодировка сообщения определена как: UTF-8 ==================================
Ответ: area://UTF-8?msgid=2:280/5555+5a353fa4
==============================================================================
Hello Michiel!

15 Dec 17 13:34, you wrote to me:

MvdV>>>   Arabic: سنة جديدة سعيدة
MvdV>>>   Armenian: Շնորհավոր Նոր տարի
MvdV>>>   Bengali: শুভ নতুন বছর
MvdV>>>   Bulgarian: Честита Нова година
MvdV>>>   Cantonese: 新年快樂
MvdV>>>   Greek: Ευτυχισμένο το νέο έτος
MvdV>>>   Hebrew: שנה טובה ומבורכת
MvdV>>>   Japanese: 明けましておめでとうございます
MvdV>>>   Polish: Szczęśliwego nowego roku
MvdV>>>   Russian: С новым годом
MvdV>>>   Ukrainian: З новим роком

KE>>  It looks exellent on a message reader supporting UTF8, but I still
KE>> cannot read it. ;)

MvdV> Rosa can read the Hebrew and the Greek. I can read the Cyrillic and the
MvdV> Polish. Sort of...

MvdV> You may not be able to read it, but you managed to properly display and
MvdV> quote it in your reader. Complete with a correct @CHRS: UTF-8 4
MvdV> kludge. Congratulations!

 Well I dont know what I did, but some time ago I did some tinkerimg.
 What surprises me is that almost half the exotic characters do resolve to the
 proper glyphs in my terminal emulator.

 Things like UTF-8 4 can be manipulated with much hassle. But I still maintain,
 that in the xlat implementation in Golded it should be UTF-8 2. As that is
 the type of translation table that is used. If the CHSRS character family is
 fixed to a translation table type, then that type is redundant and has no
 use.

 There is no implementation of xlat for type 4 translations as far as I know.
 Where proper translation is done, a different method is used and the '4' is
 irrelevant.

 My aguments sound familear, we must be a yearly pet peeve.

Kees

--- 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.011216 секунды