Text 6703, 76 rader
Skriven 2013-02-20 19:57:24 av Sergey Dorofeev (2:5020/12000)
   Kommentar till text 6663 av mark lewis (1:3634/12.42)
Ärende: LOL!
============
Hello mark,

orig.message to echo FIDONEWS on 19 Feb 13  16:33:48
 ml> oh... that's some kind of sql database or such... the option to store the
 ml> original character set and the local character set is not available in the
 ml> "standard" message base format used by most(??) systems... definitely not
 ml> BBS systems... MSG doesn't offer such a place unless the tosser
 ml> specifically adds another control line to kludge in the storage... HMB has
 ml> the same limitation but this leads to even less space for actual message
 ml> text... SQU and JAM may be able to store this info with custom fields but
 ml> again, the tosser needs to handle this since it stuffs the messages into
 ml> the message base... i don't know enough about goldbase, or synchronet's
 ml> message base format... and there are numerous others, too... so this is
 ml> definitely not something that is available globally...

I afraid classical FTN formats because they all tend to corrupt.
RDBMS usually are more robust.

 ml> then one of us is missing something... take the CP437 ALT-148 'ö' for
 ml> instance... if you translate is to your local character set and it is now
 ml> ALT-365 (for example), how is that going to be translated to someone using
 ml> CP850 when reading from your message base? are you going to convert it

"Someone" must use codepage specified in CHRS, nothing else. What to duscuss
about it, I do not understand.

 ml> then we get to the reply... are you going to emit it back out in the
 ml> original CP437 format or your local character set format? i would say in
 ml> your local character set format since the entire message, included quotes,
 ml> should have been converted but then we come back to old-school systems and
 ml> the inability of converting from UTF-8 (for instance) to CP437... i

If you want to reply to CP437 message, you should use CP437. In the reply to
CP866, you should use CP866. Common rule - reply keeps languague. If you want
to forward, you must transliterate forwarded message to represent its foreign
letters inside your codepage's character set.

But that's not issue if you are allowed to post in UTF-8 - in this case you can
mix all languagues.

 ml> haven't had time to work on transliteration tables but i believe it can be
 ml> done even though others say not and point out that german's ability to go
 ml> from "ö" to "oe" is quite different for others... i'm just a single spoken
 ml> language individual... i just want to be able to read the posts without a
 ml> bunch of graphical gibberish and i want to do this using my existing old
 ml> school BBS and all the software i have been using since i set up this BBS
 ml> years ago... i'm not the only one with this desire, either... i do not

You cannot do it without changing things. You cannot fly with your good old
Buick.

 ml> want to stiffle innovation but i also do not, more importantly, loose what
 ml> we already have and thus possibly loose many long time systems and
 ml> participants who rely on our old school systems for their contact and
 ml> conversations with others...

No any codepage affects ability to contact and conversate in plain english
(except for rusty EBCDIC). The main loose with UTF-8 (also with LATIN-1 that is
somewhy is liked by someone) is incompatible representation of pseudographics
(LATIN-1 lacks it at all).

 ml> understand... i would assume that to be another field instead of modifying
 ml> the original existing data and taking a chance on loose it somehow...
 ml> personally, i would keep all of the original data as received and use
 ml> additional fields for the modified data based on the original control
 ml> lines and header information...

May be it is most orthodoxal way but it costs much. I keep received bundles
seven days after they are succesfully processed (it may be useful for resolving
issues) but do not want to keep them permanently.

Sergey

... vim
--- PyFTN
 * Origin: fluid.fidoman.ru (2:5020/12000)