> Tennant Stuart wrote:
>>> That's not the way it should be though, trying Unicode now, although
>>> that's usually a very bad idea
>> Didn't work either.
> Didn't think it would. I asked in the Mozilla newsgroups and they said
> my posts are encoded correctly, so it's a problem on your end. You can
> solve it by simply migrating to a Mozilla based client as well ;)
S'okay, I can solve it simply by altering it by hand, so you look pretty.
> Your headers don't say much about your OS (or your reader for that
> matter) but there's Mozilla ports for just about anything, so there
> should be one for you as well :P
Other people have managed to do it okay, I'll have a go...
<types silly things into her name & the subject title>
..there, how does that look to you?
Tennant
--
____ ____ _ _ _ _ __ _ _ ____
(_ _)( ___)( \( )( \( ) /__\ ( \( )(_ _) Greetings to family
)( )__) ) ( ) ( /(__)\ ) ( )( friends & neighbours
(__) (____)(_)\_)(_)\_)(__)(__)(_)\_) (__) @argonet.co.uk & MCR
> Other people have managed to do it okay, I'll have a go...
>
> <types silly things into her name & the subject title>
>
> ..there, how does that look to you?
Re: Subject titles with € ›ž¢©¹²³°¼½¾äæçéîñöüß symbols
You really shouldn't drink that much coffee, y'know...
Anyway, this wasn't about my newsreader, which encodes my posts
correctly, it was about your newsreader decoding mine incorrectly! :)
--
We're the generation of men raised by women -
I'm wondering if another woman is really the answer we need...
I'm just replying to show André that my newsreader handles it okay. :)
> Ténnànt ß Stüärt wrote:
>> Other people have managed to do it okay, I'll have a go...
>> <types silly things into her name & the subject title>
>> ..there, how does that look to you?
> Re: Subject titles with € ›ž¢©¹²³°¼½¾äæçéîñöüß symbols
> You really shouldn't drink that much coffee, y'know...
Grin.
> Anyway, this wasn't about my newsreader, which encodes my posts
> correctly, it was about your newsreader decoding mine incorrectly!
Well, that's because your newsreader is making such a pig's breakfast
of doing it. Instead of just typing the damn characters, it's encoding
them in 7-bit ASCII, on an 8-bit ASCII system.
You might not be able to see this, but instead of just saying...
Subject titles with € ›ž¢©¹²³°¼½¾äæçéîñöüß symbols
..your newsreader has put...
Subject titles with =?windows-1252?Q?=80=8D=8F=9B=9E=A2=A9=B9?=
=?windows-1252?Q?=B2=B3=B0=BC=BD=BE=E4=E6=E7=E9=EE=F1=F6=FC=DF_symbols?=
..and in case it can't handle that either, that was...
Subject titles with EQUALS QUERY windows DASH 1252 QUERY Q QUERY
EQUALS 80 EQUALS 8D EQUALS 8F EQUALS 9B EQUALS 9E EQUALS A2 EQUALS A9
EQUALS B9 QUERY NEWLINE EQUALS EQUALS QUERY windows DASH 1252 QUERY Q
QUERY EQUALS B2 EQUALS B3 EQUALS B0 EQUALS BC EQUALS BD EQUALS BE
EQUALS E4 EQUALS E6 EQUALS E7 EQUALS E9 EQUALS EE EQUALS F1 EQUALS F6
EQUALS FC EQUALS DF UNDERSCORE symbols QUERY EQUALS
..otherwise known as bloatware. :)
>> Anyway, this wasn't about my newsreader, which encodes my posts
>> correctly, it was about your newsreader decoding mine incorrectly!
>
> Well, that's because your newsreader is making such a pig's breakfast
> of doing it. Instead of just typing the damn characters, it's encoding
> them in 7-bit ASCII, on an 8-bit ASCII system.
Seeing as it's Mozilla, it's most likely based on some sort of RFC or
whatever and therefore that way of encoding the header is the way it's
intended
> ..your newsreader has put...
>
> Subject titles with =?windows-1252?Q?=80=8D=8F=9B=9E=A2=A9=B9?=
> =?windows-1252?Q?=B2=B3=B0=BC=BD=BE=E4=E6=E7=E9=EE=F1=F6=FC=DF_symbols?=
>
> ..and in case it can't handle that either, that was...
>
> Subject titles with EQUALS QUERY windows DASH 1252 QUERY Q QUERY
> EQUALS 80 EQUALS 8D EQUALS 8F EQUALS 9B EQUALS 9E EQUALS A2 EQUALS A9
> EQUALS B9 QUERY NEWLINE EQUALS EQUALS QUERY windows DASH 1252 QUERY Q
> QUERY EQUALS B2 EQUALS B3 EQUALS B0 EQUALS BC EQUALS BD EQUALS BE
> EQUALS E4 EQUALS E6 EQUALS E7 EQUALS E9 EQUALS EE EQUALS F1 EQUALS F6
> EQUALS FC EQUALS DF UNDERSCORE symbols QUERY EQUALS
>
> ..otherwise known as bloatware. :)
that's MIME-encoding, actually, and if your newsreader isn't decoding it
properly, i'd say it's a problem on your end. MIME has been a published
standard for several years now, and any mail/newsreader that can't handle
it should be considered broken.
MIME, in this case, is intended to encode 8-bit ASCII characters as 7-bit
ASCII, since some servers don't handle 8-bit ASCII so well, esp. in
message headers (i'm sure nowadays most servers don't have problems).
personally i tend to leave MIME turned off, since for non-compliant
mail/newsreaders you get the crap you pasted above, whereas with normal
8-bit the only mistakes you'll see are generally a missing character (and
a news server that can't handle 8-bit charsets will most likely just drop
the message, or mangle it in some fashion - but as i said, such servers
are probably very rare). in any case, whoever is using the windows-1252
codepage and posting to an international forum where many people are using
different character sets (as well as many people not on windows), you
really should be using iso-8859-1 (or -15 if you really need the euro
symbol).
-brian
> in any case, whoever is using the windows-1252 codepage
oops, that was me messing about with the character coding options. I've
set it back to iso-8859-1 now since I do need the Euro sign ;)
I hope it's worked, Thunderbird has a mind of his own sometimes when it
comes to character encoding...
André
> oops, that was me messing about with the character coding options. I've
> set it back to iso-8859-1 now since I do need the Euro sign ;)
errm, that should have read "don't need the Euro sign" - at least not in
newsgroups...
> Brian J. Tarricone wrote:
>
>> in any case, whoever is using the windows-1252 codepage
>
> oops, that was me messing about with the character coding options. I've
> set it back to iso-8859-1 now since I do need the Euro sign ;) I hope
> it's worked, Thunderbird has a mind of his own sometimes when it comes
> to character encoding...
aware that i'm moving even farther off-topic...
what's your opinion of thunderbird? i've been using mozilla for web and
mail since pre-1.0, but i'd like to switch to firebird/thunderbird as they
seem to be faster independently. however, i remember some earlier
milestones of mozilla eating my mail, so i'm not prepared to put tens of
thousands of mail messages in the hands of a beta-quality mail reader. at
the same time, i'm really itching to try out thunderbird and hopefully
soon make it my primary mail reader...
-brian
> Tennant Stuart wrote:
>>> Anyway, this wasn't about my newsreader, which encodes my posts
>>> correctly, it was about your newsreader decoding mine incorrectly!
>> Well, that's because your newsreader is making such a pig's breakfast
>> of doing it. Instead of just typing the damn characters, it's encoding
>> them in 7-bit ASCII, on an 8-bit ASCII system.
> Seeing as it's Mozilla, it's most likely based on some sort of RFC or
> whatever and therefore that way of encoding the header is the way it's
> intended
Sure. :)
Have you tried just typing them in?
> aware that i'm moving even farther off-topic...
>
> what's your opinion of thunderbird?
I've been using Mozilla 1.4 (before that I used Netscape 4-7) and
switched to Thunderbird 0.2 when it came out. As far as I can tell, the
major difference is the UI for Thunderbird, everything else is pretty
much the same, which is hardly surprising as Thunderbird 0.2 is based on
the Mozilla 1.5 trunk (btw. RC2 has been released today ;) ).
I don't know if you use any extentions for Moz, but the majority of them
will not work for either bird (and I'm not talking about girls/women
here, for all you Brits). Firebird and Thunderbird together use up more
RAM and disk space (due to both of them using their own Gecko Runtime
instead of sharing one) but it's fairly neglectable if you manage to run
Mozilla at decent speeds on your system. Overall I'm quite happy with
switching from Mozilla to the birds, although I don't think they're
superior to the suite. (Nor is the suite superior to them)
> i remember some earlier milestones of mozilla eating my
> mail, so i'm not prepared to put tens of thousands of mail messages
> in the hands of a beta-quality mail reader.
As of now, the developers do not guarantee that you'll always be able to
migrate your profile to the next version of Thunderbird. However as it
is now, you simply copy your Mozilla profile folder (the one named
*.slt) into the new Thunderbird profile folder and everything should
appear there. Or you setup your mail and news accounts in Thunderbird,
so that it creates the according subfolders in the Mail folder and then
you simply copy them, which is what I did :)
Better and more detailed help here:
http://www.texturizer.net/thunderbird/
> at the same time, i'm
> really itching to try out thunderbird and hopefully soon make it my
> primary mail reader...
*g* I know what you mean... One of the reasons why I migrated to
Firebird/Thunderbird is that they're still pre-1.0 and I think it's
quite interesting to follow the development and work that goes into it.
The amount of time I spend browsing through Bugzilla recently is
ridiculous ;)
André
--
Into my big mouth, you could fly a plane
http://fear.mybigmouth.com
>> Seeing as it's Mozilla, it's most likely based on some sort of RFC or
>> whatever and therefore that way of encoding the header is the way it's
>> intended
>
> Sure. :)
>
> Have you tried just typing them in?
Have I tried typing what in?
> Tennant Stuart wrote:
>> Have you tried just typing them in?
> Have I tried typing what in?
The 'fancy' characters, like this - André.
>>> Have you tried just typing them in?
>
>> Have I tried typing what in?
>
> The 'fancy' characters, like this - André.
I type them in all the time, it's just that I have hardly any influence
on what ends up in the message headers.
As for the "chicken" in the subject line (I only realised it now), there
were two reasons why I removed all the special characters, #1 being
readability and #2 being the obvious differences between our newsreaders
causing several of the special characters to no longer be recognized and
be replaced by question marks instead.
It's all your fault really :P
André
> Tennant Stuart wrote:
>>>> Have you tried just typing them in?
>>> Have I tried typing what in?
>> The 'fancy' characters, like this - André.
> I type them in all the time, it's just that I have hardly any influence
> on what ends up in the message headers.
> As for the "chicken" in the subject line (I only realised it now), there
> were two reasons why I removed all the special characters, #1 being
> readability and #2 being the obvious differences between our newsreaders
> causing several of the special characters to no longer be recognized and
> be replaced by question marks instead.
> It's all your fault really :P
That's okay. :)