Re: [Gravity] Send 8 bit chars doesn't work *anymore*



bad_n_mad@xxxxxxxxx Chupo wrote in news.software.readers ..

In article <MPG.1e703c53f02f8da9896f5@xxxxxxxxxxxxxxxxxxx>, Tom B.
<nfn03862@xxxxxxxxxx> says...
Chupo wrote in news.software.readers ..

Something weird happened to 'Send 8 bit characters' & 'Send 8 bit chars
in header lines' options a few day ago.

I have to use *send* 8 bit chars & 8859-2 encoding to properly *read*
the mail. Sending posts is not critical since I don't use any specific
characters. However, other people on some news groups (Croatian) are

Sending (encoding) and reading (decoding) are two different things.
Reading should be based on the headers of the post you are reading,
not Gravity's options.

I have made a few examples where it can be seen that my Sending
(encoding) settings affect reading, please take a look at

http://www.geocities.com/bad_n_mad/Gravity

How is that possible?

I don't know because I don't speak the language.

I was also examining the headers from some other news readers, there is
no encoding data inside some headers, do you know how exactly Gravity
handles such posts?

If there are no headers I assume gravity maps the characters to the
current Windows code page. That is the way it used to work before the
RFC 2047 stuff was added.

I thought there was only one character mapping to 8859-2.

Yes, but there were a few non standard encodings in the past that had
been in the use here around (YU-SCII, CRO-SCII, 8859-x, Win, ...) and
the best way is not to use Croatian graphemes on the usenet. However,
if one wants to be able to read all (OK, not quite *all* but...) the
articles without some strange or wrong characters, the only solution I
know is to install uniHR font. If you display uniHR font with the
Character Map, you can see that the same grapheme may exist on more
than one location. For instance Alt+0154 and Alt+0185 would have given
the same symbol.

As far as I know gravity only handles 8859-2. So, it probably does not
recognize the other character sets.

I know this is not quite good explanation but I am not an expert. I
believe users from some other countries (Hungary, Czech, Slovakia, ...)
that are using Central European encoding probably have similar
problems!?

Could be - but I haven't heard anything from them.

What
Content-Type: headers are people sending for a "special universal cro-
font?"


It is not the case. The people are not sending *for* an uniHR font, the
universal font was invented to make all kind of people's posts
readable.

The font concept is interesting - do you use the font? What shows in
Gravity?

I remember the 'DOS times'. Some of the standard characters ({,},\,...)
were simply replaced by Croatian letters. If you are really interested
in examining the issue (and maybe implementing some new options :-) ),

I would like to but my C++ skills are not so good. You would need to
find a programmer willing to hack at the code. "coding.cpp" is a good
place to start


--
Tom B. * * * Gravity Web Pages * * *
http://lightning.prohosting.com/~tbates/gravity/
http://gravity.tbates.org/
http://mpgravity.sourceforge.net/
.



Relevant Pages

  • Re: How come C allow structure members to be addressed like an array ?
    ... I won't allow a Roman gypsie within a foot ... There are RFCs that define the content of headers in Usenet articles. ... standard encoding that allows other characters to be represented ... and others will display the encoding; ...
    (comp.lang.c)
  • Re: PN Help !!!!! ?????
    ... is that it is *mothy* who is Sending Posts ... Sent using Quoted-Printable Encoding, that *their* Newsreader then ... Add the ">" Characters in my Reply.) ... Quoted-Printable Encoding is cos that happens when you are *Replying* ...
    (uk.people.silversurfers)
  • Re: [Gravity] Send 8 bit chars doesnt work *anymore*
    ... Sending (encoding) and reading are two different things. ... I was also examining the headers from some other news readers, ... articles without some strange or wrong characters, ...
    (news.software.readers)
  • Re: Okay to use "Quoted Printable" MIME in OE?
    ... > default is 76 characters but I lowered this to 72). ... > "None" for encoding which means you don't get any encoding (no MIME part ... So they get a single reply prefix ... > I've checked against some posts here where it looks like the poster used ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: Worldcon news
    ... they read her posts. ... Which part of Keith's "software is not properly decoding her ... certain characters are expressed as an equals sign, ... Newsreaders that generate quoted-printable without generating the headers ...
    (rec.arts.sf.fandom)

Loading