Re: Armenian, Sumerian, Burushaski, and Turkic languages

Brian M. Scott <b.scott@xxxxxxxxxxx> wrote in message
news:172x4a5l7broh.jr8pq8qts19z$.dlg@xxxxxxxxxxxxx
On Fri, 8 Jun 2007 17:09:28 +1200, Paul J Kriha
<paul.nospam.kriha@xxxxxxxxxxxxxxx> wrote in
<news:4668e3fe@xxxxxxxxxxxx> in sci.lang:

[...]

Is "40tude_Dialog/2.0.12.1" the name of that piece of sw?
Yes. <http://www.40tude.com/dialog/>
It's a very nice newsreader, though it can be a bit of a
space hog if you don't compact the database often enough.

Are you also able to make ad hoc choice of a charset with
a simple 1 or 2 key stroke?
When posting? I don't think so.

The newsreader I am using at the moment doesn't allow me
to chose iso-8859-15. I don't remember what it does when
it receives a post in that charset.

Let's find out: žè. (That was z-hachek and e-grave, a
combination that Dialog first finds in iso-8859-15.)

Well what a surprise, it screws it up.
I checked, your post header indeed contains
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 8bit

I see z-hachek displayed as an ogonek, just a little black
tail descender with otherwise blank character. The e-grave
is displayed as e with a grave accent.

It seems that IE uses the charset it calls "Western European (Windows)".
That seems to be my default set. After it's displayed I can force it to
redisplay it using one of the several available sets but since none
of them is iso-8859-15 they all screw it up in a number different ways.

So the result of this little experiment is that IE behaves in a typical
MS way. When it doesn't have the set it's told to use it uses its
Windows' defaults and doesn't give you any warning at all that
the text might not look at all the way it's supposed to look.

Thanks Brian for your time.

pjk

Brian


.

Quantcast