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


Присутствуют сообщения из эхоконференции UTF-8 с датами от 19 Apr 14 00:41:48 до 01 Apr 24 00:03:00, всего сообщений: 1367
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 1272 из 1367 ============================================ UTF-8 =
От   : Rob Swindell                     1:103/705          04 Mar 23 13:11:48
Кому : Michiel van der Vlist                               04 Mar 23 13:11:48
Тема : codepage
FGHI : area://UTF-8?msgid=329.fidoutf8@1:103/705+2868eb5d
На   : area://UTF-8?msgid=2:280/5555+640319a0
= Кодировка сообщения определена как: CP437 ==================================
Ответ: area://UTF-8?msgid=2:280/5555+6404929a
==============================================================================
  Re: codepage
  By: Michiel van der Vlist to Rob Swindell on Sat Mar 04 2023 11:00 am

> Hello Rob,
>
> On Thursday March 02 2023 17:02, you wrote to me:
>
>  >> All three of your messages have non-ASCCI characters. They all have
>  >> the degree character '°' in the sign off, or whatver you call it.
>  >> In the last message it is also present in the message test before
>  >> the "--" (two dashes).
>
>  RS> Ah, true. But in the message I posted using a UTF-8 terminal, that
>  RS> would have been a UTF-8 encoded "degree" symbol instead of a
>  RS> CP437-encoded one (as would have been in the other messages, including
>  RS> this one).
>
> The message I am respondig to, is indeed encoded in CP437.
>
> So let me get this straight:
>
> 1) If the message that is responded to, is encoded in CP437, Synchronet
> answers in CP437. Yes?

No. The message response itself determines the encoding and only CP437 terminals can faithfully author CP437 encoded messages. If a UTF-8 terminal user responds to a CP437 encoded message (with non-ASCII chars), the original message text is converted to UTF-8 before it is quoted and the response will be UTF-8. Unless there are no non-ASCII chars in the response, in which case the response charset witll just be ASCII.

> So what happens if the response does not fit into CP437?

I think this question is making false assumptions.

> What happens if the original message is encoded in a one byte encoding other
> than CP437?

The only encodings Synchronet supports for message text are ASCII, CP437, and UTF-8.

> 2) If the message that is responded to is encoded in UTF-8, Synchronet
> answers in UTF-8 if the terminal theis used supports UTF-8. Yes?

Yes.

> So what happens in that case if the terminal does not support UTF-8?

The message text would be converted to CP437 before being quoted and the response would be in CP437.

>  >>  RS> Norco, CA WX: 42.0°F, 79.0% humidity, 0 mph NE wind, 0.15
>  >> inches RS> rain/24hrs
>
> My software translates the CP437 encoded degree sign into UTF-8 as you can
> see.

Yup, most software does the same, when appropriate.
--
                                            digital man (rob)

Sling Blade quote #18:
Karl Childers: Some folks call it Hell, I call it Hades.
Norco, CA WX: 55.8°F, 64.0% humidity, 5 mph SE wind, 0.01 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

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