Text 16850, 54 rader
Skriven 2013-11-22 19:07:27 av mark lewis (1:3634/12.71)
     Kommentar till en text av Maurice Kinal (1:261/38.9)
Ärende: utf-8 fidonet messaging
===============================
On Fri, 22 Nov 2013, Maurice Kinal wrote to mark lewis:

 ml> my editor didn't do that... it was that way in the PKT that 
 ml> arrived here...

 MK> Ah!  Yeah I've seen that happen before.  I notice the reply I am 
 MK> replying to got it right so ... who knows?

the grinch knows ;)  it also means that it was changed upstream... most likely
at the originating system... why there? because no mail processing software
should be altering message content end-user reading software may translate to
the local codepage for display purposes... editing software should either match
the original codepage when replying (troublesome) or should translate to the
local codepage (better) so that the entire reply is in the same codepage since
no one was ever able to get "interlaced" control lines to work in FTN software
and at least one editor package (msged from memory) specifically broek such
attemptes by sorting all control lines to the top of the message while adding
SOT and the contrary EOT control lines to messages... EOT being contrary in
that it was not at the top of the message with other control lines...

 MK> Anyhow I am certain that more than a few of these will get 
 MK> filtered out simply because there are both utf-8 characters and 
 MK> whatever codepage included in the same reply flying an incorrect 
 MK> CHRS kludge to reflect that.

why would they be filtered out? no standard FTN mail processing software that
i'm aware of filters based on content being inaccurate...

 MK> In fact there is no correct CHRS kludge for this particular 
 MK> behavior which is why I won't quote back your entire reply.

hunh? what behavoir?

 MK> I do see the utf-8 characters correctly, as they got sent from you 
 MK> flying your kludge 'CHRS: IBMPC 2'.

that's because your software and/or processing assumes that certain sequences
of characters are something that they are not (intended to be)...

eg:  ö and ö

what do you see?

 MK> I won't bet the farm that anyone else will though but this reply 
 MK> should be fine as per fts-5003.001 and my kludge 'CHRS: UTF-8 4' 
 MK> given that there are no other codepage characters within this 
 MK> reply.  ;-)

hahaha :)

)\/(ark

--- FMail/Win32 1.60
 * Origin:  (1:3634/12.71)