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


Присутствуют сообщения из эхоконференции FTSC_PUBLIC с датами от 13 Sep 13 18:57:24 до 01 Aug 24 00:39:47, всего сообщений: 7127
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 936 из 7127 ======================================= FTSC_PUBLIC =
От   : Nicholas Boel                    1:154/701          04 Jan 14 12:20:42
Кому : Maurice Kinal                                       04 Jan 14 12:20:42
Тема : all over but the crying?
FGHI : area://FTSC_PUBLIC?msgid=1:154/701+52c852e5
На   : area://FTSC_PUBLIC?msgid=1:153/7001.0+52c83c7a
= Кодировка сообщения определена как: UTF-8 ==================================
Ответ: area://FTSC_PUBLIC?msgid=2:280/5003.4+52c85d74
Ответ: area://FTSC_PUBLIC?msgid=1:153/7001.0+52c862a3
==============================================================================
Hello Maurice,

On 04 Jan 14 16:53, Maurice Kinal wrote to Nicholas Boel:

MK> Hey Nicholas!

NB>> FTS-5003.001 covers how UTF-8 _should_ be posted, and with what
NB>> level.

MK> Exactly what is a level and how is it supposed to be implimented?
MK> Near as I can tell characters are either UTF-8 or they aren't no
MK> matter what level the kludge claims they are.  Can this be considered
MK> another bogus claim to the word 'standard'?  Methinks it is and you
MK> have provided evidence that this is so.

From FTS-5003.001:

Level 4
-------

Level 4 is for multi byte character encodings. The only presently known
implementation is UTF-8.

[snip]

So basically, posting in UTF-8 should be level 4 regardless whether the
actual level parameter is there or not. It shouldn't matter. Either way, it
should definitely NOT be showing up as "UTF-8 2".

If what Kees says is true, and it's in the translation tables (which I've
tried manually setting to a level 4, and also using a workaround that was done
for the Win32 version that Michiel uses), then those translation tables are
still maintained by the developers of Golded, since their formatting has been
changed so Golded can read them properly. There's definitely something wrong,
and I'd like to find out what it is.

NB>> As it seems, the current maintainer of Golded happens to be one
NB>> of the authors of FTS-5003.001, so that may help the cause at
NB>> least.

MK> I won't be betting the farm on that.  Like I say above, UTF-8
MK> characters are UTF-8 characters despite what some might claim they
MK> are.  The current maintainer of Golded ought to know if indeed he
MK> actually cares about UTF-8 compatibilty.

He may or may not care about it, but since he also co-authored FTS-5003.001,
the level 4 kludge should at least be honored while I'm using a multibyte
character encoding. No?

MK> I for one think this is on topic for this particular echo.

While it is in relation to documented standards, I suppose I can agree there.

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20130910
* Origin: Dark Sorrow | darksorrow.us (1:154/701)

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