Re: TB: Problems with Charsets by Sending into NNTP

M Cowperthwaite wrote:
> Shanky-TMW wrote:
>> I have a Problem with my Thunderbird (V1.0.5)
>> 
>> TB send all Messages in UTF-8 (Windows 1225), if I used Western ISO 
>> 8859-1 on the Send Message Font Option.
> 
> "1225"?  I can't find any reliable reference to "Windows-1225" -- are 
> you sure you don't mean "windows-1252"?  That is definitely not the same 
> thing as UTF-8, not even close.

Yes I mean 1252 - my fault.
I know that 1252 and UTF-8 are different. Because, TB sends my message 
in one of this two Charsets.


>> If I use 8859-15, it sends in 8859-15.
> 
> ISO-8859-15 defines these particular characters that 8859-1 does not:
>    € Š š Ž ž Œ œ Ÿ
> (All of these are also defined in Windows-1252; however, their encoding 
> values are different than those defined under Unicode/UTF-8.)
> 
> For a message using one of those characters, if your selected encoding 
> is ISO-8859-1, TB/Mozilla must select a different charset.  By default, 
> it will prompt you to send in UTF-8; if you don't want to use that 
> encoding, then you need to pick a different one.
> 
> In your case, you might be better off simply defining your default 
> composition (outgoing) charset to be ISO-8859-15 (or Windows-1252, or 
> UTF-8).

I eaven know that. But TB send my Message with or without this special 
Charsets in 1252 or UTF-8, but the Options still stand on 8859-1
That's what I'm wondering.


> For more advanced control, you can define a "fallback" encoding to be 
> used when the selected charset doesn't cover all the characters in use. 
> You define a fallback for each character set you want to use.  So, for 
> instance, you can define this preference:
>    intl.fallbackCharsetList.ISO-8859-1
> 
> to be    UTF-8     or     ISO-8859-15,Windows-1252
> 
> In the first instance, Moz will automatically convert an 8859-1 message 
> to UTF-8 without prompting; in the second case, it will convert the 
> 8859-1 message to 8859-15, if that encoding works; if not, it will 
> convert to Windows-1252, if *that* encoding works; if neither works, it 
> will prompt you to convert to UTF-8 or return to select a different 
> character set.

Maybe this solves the Problem, but I had write a new user.js for that.

I don't know why it works in the past without a user.js?

So the Problem solved, but I don't know why it appears.

Thanks for help
  Klaus