Hello Maksym,
Tuesday, January 27, 2004, 2:00:24 PM, you wrote:
MK> First things first, in this case you cannot (and should not) call your
MK> character set "Default character set".
Yes, we can - it's a shortened form of "Default character set for
non-7-bit ASCII characters", but the latter is a
Hello Thomas,
Monday, January 26, 2004, 8:01:14 PM, you wrote:
>> The behaviour you propose cause more problems because some systems
>> (especially those functioning in the US and Canada) do not know anything
>> about character sets other than us-ascii (and ISO, if one is lucky)
>> and that cause
Hello Stefan,
I agree to what Thomas said in his message.
ST> Well, here is the problem - I use a Russian character set by default.
ST> When I send messages in English, I'm always sure that they're going
ST> out in us-ascii, no need to change anything here. Now, imagine I'm
ST> sending a message
Hello Stefan,
On Mon, 26 Jan 2004 09:30:00 +0200 GMT (26/01/2004, 14:30 +0700 GMT),
Stefan Tanurkov wrote:
> The behaviour you propose cause more problems because some systems
> (especially those functioning in the US and Canada) do not know anything
> about character sets other than us-ascii (an
Hello Maksym,
On Sun, 25 Jan 2004 22:09:25 +0200 GMT (26/01/2004, 03:09 +0700 GMT),
Maksym Kozub wrote:
> Hope you get my point.
Yes. And I admit to still not having read the RFC.
> Any high ASCII letter can never be 7bit data, - that's right, and
> that's what RFC2045 says. What it does _not_
On Monday, January 26, 2004 at 2:30:00 AM, Stefan Tanurkov wrote in
the message "Fwd: Bug (maybe wrong understanding of RFCs): an encoding
selected by the user sometimes silently replaced with 7-bit US-ASCII"
<mid:[EMAIL PROTECTED]>:
> So, basically, there is no problem on our
Hello Maksym,
Sunday, January 25, 2004, 5:07:51 PM, you wrote:
MK> As a result of this behaviour combined with some other MUAs' (e.g.
MK> Microsoft-made ones') improper behaviour, there is the following
MK> problem reported by various people.
The behaviour you propose cause more problems because
Hello Carsten,
On Mon, Jan 26 2004, 0:52:14 you wrote:
>> That sounds wrong.
CT> Huh? This is the way good mail clients work. It is not wrong at all.
It _is_ wrong. See my other messages in this thread, where I clearly
demonstrate that 1) there is actually _nothing_ in RFC2045 preventing
a MUA
* Thomas Fernandez writes:
> Maksym Kozub wrote:
> Let me understand this. You explicitely tell TB to use:
>> "Content-Type: text/plain; charset=koi8-r /
>> Content-Transfer-Encoding: 8bit"
> but TB changes it to
>> "Content-Type: text/plain; charset=us-ascii
>> Content-Transfer-Encoding: 7bit"
Hello Thomas,
On Sun, 25 Jan 2004 20:41:42 you wrote:
TF> OK, let's read on:
>> Alexandr Kiselev, administrator, Dec 02, 2003, 07:28:24 pm:
>>
>> "If all characters in a message are us-ascii, then Bat has been alway
Hello Maksym,
On Sun, 25 Jan 2004 20:02:39 +0200 GMT (26/01/2004, 01:02 +0700 GMT),
Maksym Kozub wrote:
TF>> just because it doesn't detect a high ASCII character?
> Yep. Looks exactly so.
TF>> That sounds wrong.
> For me too.
OK, let's read on:
> Alexandr Kiselev, administrator, Dec 02, 200
Hello Thomas,
On Sun, 25 Jan 2004 г. 18:39:19 you wrote:
TF> Let me understand this. You explicitely tell TB to use:
>> "Content-Type: text/plain; charset=koi8-r /
>> Content-Transfer-Encoding: 8bit"
TF> but TB changes it to
>> "Content-Type: text/plain; charset=us-ascii
>> Content-Transfer-En
Hello Peter,
On Sun, 25 Jan 2004 18:30:51 +0100 GMT (26/01/2004, 00:30 +0700 GMT),
Peter Meyns wrote:
TF>> just because it doesn't detect a high ASCII character?
TF>> That sounds wrong.
> That's exactly what happens here with my default setting of Latin-9
> (ISO-8859-15).
Then it sounds like a
Hi Thomas,
on Sun, 25 Jan 2004 23:39:19 +0700GMT (25.01.04, 17:39 +0100GMT here),
you wrote in mid:[EMAIL PROTECTED] :
TF> Let me understand this. You explicitely tell TB to use:
>> "Content-Type: text/plain; charset=koi8-r /
>> Content-Transfer-Encoding: 8bit"
TF> but TB changes it to
>> "Con
Hi Thomas,
on Sun, 25 Jan 2004 23:39:19 +0700GMT (25.01.04, 17:39 +0100GMT here),
you wrote in mid:[EMAIL PROTECTED] :
>> If you choose an 8-bit encoding for your outgoing messages, but the
>> message actually does not contain any symbols with decimal values
>> higher than 127, then TB! would jus
Hello Maksym,
On Sun, 25 Jan 2004 17:07:51 +0200 GMT (25/01/2004, 22:07 +0700 GMT),
Maksym Kozub wrote:
> If you choose an 8-bit encoding for your outgoing messages, but the
> message actually does not contain any symbols with decimal values
> higher than 127, then TB! would just make it "Content
I sent this message on TBTECH first; it seems however that there is
almost nobody reading the tech list, so I decided to resend it here. I
recently submitted the problem described in this message as a bug
(https://www.ritlabs.com/bt/bug_view_advanced_page.php?bug_id=0002349);
decided to also report
17 matches
Mail list logo
