= Сообщение: 1274 из 1367 ============================================ UTF-8 = От : Rob Swindell 1:103/705 05 Mar 23 11:40:06 Кому : Michiel van der Vlist 05 Mar 23 11:40:06 Тема : codepage FGHI : area://UTF-8?msgid=331.fidoutf8@1:103/705+286a2761 На : area://UTF-8?msgid=2:280/5555+6404929a = Кодировка сообщения определена как: CP437 ================================== Ответ: area://UTF-8?msgid=2:280/5555+640651dc ============================================================================== Re: codepage By: Michiel van der Vlist to Rob Swindell on Sun Mar 05 2023 02:01 pm
> Hello Rob, > > On Saturday March 04 2023 13:11, you wrote to me: > > >> So let me get this straight: > >> > >> 1) If the message that is responded to, is encoded in CP437, > >> Synchronet answers in CP437. Yes? > > RS> No. The message response itself determines the encoding and only CP437 > RS> terminals can faithfully author CP437 encoded messages. If a UTF-8 > RS> terminal user responds to a CP437 encoded message (with non-ASCII > RS> chars), the original message text is converted to UTF-8 before it is > RS> quoted and the response will be UTF-8. Unless there are no non-ASCII > RS> chars in the response, in which case the response charset witll just > RS> be ASCII. > > I see... So it is the terminal - or whatever functions as its equivalent - > and only the terminal that determines the encoding of the message at hand.
Or rather, the message content created with that terminal. If the content is just plain ASCII, regardless of the terminal that created it, then the message will fly the ASCII charset flag. In Synchronet, a CP437 terminal cannot be used to created UTF-8 content, so messages created by such a terminal will either be ASCII or CP437 encoded.
> It is making assumtions, but they are not false I would say. Read on.. I > will come back to that further down. > > >> What happens if the original message is encoded in a one byte > >> encoding other than CP437? > > RS> The only encodings Synchronet supports for message text are ASCII, > RS> CP437, and UTF-8. > > Hmmm... That leaves out a big part of Fidonet. These days the majority, > maybe the vast majority is writen in a language that uses the Cyrillic > alfabet and the encoding is CP866.
True, that's the state of things.
> >> 2) If the message that is responded to is encoded in UTF-8, > >> Synchronet answers in UTF-8 if the terminal that is used supports > >> UTF-8. Yes? > > RS> Yes. > > OK, so far so good... > > >> So what happens in that case if the terminal does not support > >> UTF-8? > > RS> The message text would be converted to CP437 before being quoted and > RS> the response would be in CP437. > > And now I come back to my previous question: what happens if it does not fit > into CP437? That can easely happen. A Euro sign '¿' can be composed in UTF-8 > but it does not fit into CP437.
When a CP437 terminal user quotes a UTF-8 message that contains untranslatable UNICODE codepoints without a CP437 equivalent, they're translated to character that indiciates it was untranslatable. By default, that character is the upside down question mark. -- digital man (rob)
Sling Blade quote #14: Karl Childers: Some folks call it a sling blade, I call it a kaiser blade. Norco, CA WX: 51.1°F, 73.0% humidity, 4 mph E wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
