Postings on ACF

  • Thread starter Thread starter W H G
  • Start date Start date
W

W H G

Dear Tramp,

I keep getting a message to add Arabic language support
on your posts. Is there anyway you can setup to post
in English text only?
I just prefer not to load Chinese, Japanese, Arabic ...

Best wishes,
Bill
W H G
 
W H G said:
Dear Tramp,

I keep getting a message to add Arabic language support
on your posts. Is there anyway you can setup to post
in English text only?
I just prefer not to load Chinese, Japanese, Arabic ...

I know that a lot of people don't like Tramp's postings, but can you a
little bit more precise?
I don't like the current lettertype, but I didn't got a message to add
Arabic support.
I'm happy with the Tramp information, but the lettertype could and should be
smaller.
Read's better :-) if you haven't Tramp in your killfilter.
 
chris said:
I know that a lot of people don't like Tramp's postings, but can you a
little bit more precise?
I don't like the current lettertype, but I didn't got a message to add
Arabic support.
I'm happy with the Tramp information, but the lettertype could and should
be
smaller.
Read's better :-) if you haven't Tramp in your killfilter.

See my previous post in Tramp's "Browser Hijack Retaliator" thread. I've not
seen anything about Arabic but his/her posts are unreadable in OE preview
panel, and sometimes "null" characters (the sort which appear when the
original is in a non-Latin script) appear. Also, sometimes the message does
not appear at all, but the preceding message remains on display.

===

Frank Bohan
¶ Put not your trust in money, but put your money in trust.
 
See my previous post in Tramp's "Browser Hijack Retaliator" thread. I've
not seen anything about Arabic but his/her posts are unreadable in OE
preview panel, and sometimes "null" characters (the sort which appear when
the original is in a non-Latin script) appear. Also, sometimes the message
does not appear at all, but the preceding message remains on display.

Tramps posts
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-8" <==arabic
Content-Transfer-Encoding: 7bit

Tramps posts prompt to install arabic , you could do it, or just ignore
them.
http://en.wikipedia.org/wiki/ISO-8859-8


Your reader is set to read all messages as plain text , as it should be in
a text newsgroup, so they just show as untranslated garbage.
 
Terry Russell said:
Your reader is set to read all messages as plain text , as it should be in
a text newsgroup, so they just show as untranslated garbage.

It also exposes a bug in OE .
 
Tramps posts
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-8" <==arabic
Content-Transfer-Encoding: 7bit

Tramps posts prompt to install arabic , you could do it, or just
ignore them.
http://en.wikipedia.org/wiki/ISO-8859-8

That's a Hebrew charset, as the Wikipedia page says. He has also
recently posted with ISO-8859-6, an Arabic charset. AFAICT, his
"Content-Transfer-Encoding: 7bit" header is due to a bug in Gravity;
it should be 8bit.
Your reader is set to read all messages as plain text , as it
should be in a text newsgroup, so they just show as untranslated
garbage.

Those things are plain text. They show up ok with Xnews, which makes
no attempt to translate or decode them. I don't know why OE seems to
have such trouble with them.

His posts' charsets are probably artifacts of his cutting-and-pasting
8bit characters from the WWW. Tramp, if you're reading this and you're
a Firefox user, the Copy Plain Text extension can help with that.

<http://mozmonkey.com/>
 
»Q« said:
That's a Hebrew charset, as the Wikipedia page says. He has also
recently posted with ISO-8859-6, an Arabic charset. AFAICT, his
"Content-Transfer-Encoding: 7bit" header is due to a bug in Gravity;
it should be 8bit.

Hah, didn't catch that..it was 6 and I resurrected a draft , how many posts
get started then dropped I wonder ? and repointed it to the matching
wikipedia page.
Anyway..the idea is the same :-)
Those things are plain text. They show up ok with Xnews, which makes
no attempt to translate or decode them. I don't know why OE seems to
have such trouble with them.

They may contain plain text, but the content isn't supposed to be
interpreted as plain text, it isn't described as
Content-Type: text/plain; charset=ISO-8859-1

It does produce other bugs in OE, those using OE, which is great many, with
the default setting, which is
a great many, will see garbage.
 
They may contain plain text, but the content isn't supposed to be
interpreted as plain text, it isn't described as
Content-Type: text/plain; charset=ISO-8859-1

I guess it's a matter of semantics. The Content-Type of the
ISO-8859-6, -8, and -15 posts is text/plain, which is what I meant.
but clearly they are not 7bit ASCII, which is what I reckon you
meant.
 
|That's a Hebrew charset, as the Wikipedia page says. He has also
|recently posted with ISO-8859-6, an Arabic charset. AFAICT, his
|"Content-Transfer-Encoding: 7bit" header is due to a bug in Gravity;
|it should be 8bit.

Is it a bug? It might just be a setting. I have the these for options
under Preferred Character Set. I'm currently using #15

iso-8859-1
iso-8859-2
iso-8859-3
iso-8859-4
iso-8859-5
iso-8859-6
iso-8859-7
iso-8859-8
iso-8859-9
iso-8859-10
iso-8859-15

I also have to boxes called
Send 8 bit characters
Send 8 bit chars in header lines

Neither of those boxes is ticked off.



|His posts' charsets are probably artifacts of his cutting-and-pasting
|8bit characters from the WWW.
|Tramp, if you're reading this and you're
|a Firefox user, the Copy Plain Text extension can help with that.
|
|<http://mozmonkey.com/>


Thanks for the info. I use Firefox for somethings but I still like IE
better. BTW there is a program called PureText
http://stevemiller.net/puretext/ that cleans up copied text as well.
 
| AFAICT, his "Content-Transfer-Encoding: 7bit" header is due to a
| bug in Gravity; it should be 8bit.

Is it a bug? It might just be a setting. I have the these for
options under Preferred Character Set. I'm currently using #15

iso-8859-1
iso-8859-2
iso-8859-3
iso-8859-4
iso-8859-5
iso-8859-6
iso-8859-7
iso-8859-8
iso-8859-9
iso-8859-10
iso-8859-15

Yeah, using any of those charsets, the Content-Transfer-Encoding header
should be 8bit.
I also have to boxes called
Send 8 bit characters
Send 8 bit chars in header lines

Neither of those boxes is ticked off.

Headers should always be 7bit characters, so I'd leave that second one
unchecked. Checking the first one, though, might help. You're sending
8bit characters anyway (in some of your posts), so I don't see how it
could hurt. If it does hurt, I'm sure someone will let us know. ;)
 
»Q« said:
Yeah, using any of those charsets, the Content-Transfer-Encoding header
should be 8bit.


Headers should always be 7bit characters, so I'd leave that second one
unchecked. Checking the first one, though, might help. You're sending
8bit characters anyway (in some of your posts), so I don't see how it
could hurt. If it does hurt, I'm sure someone will let us know. ;)

--

Well, whatever the problem was it has now disappeared. I find it strange
that it only affected OE's preview display, not the full screen or "reply
group" displays. Verily, a piece of Microsoft which passeth all
understanding.

===

Frank Bohan
¶ Computer programmers know where their next byte is coming from.
 
Back
Top