subject encoding in bug report

emailaya · Post by **emailaya** » Mon Sep 25, 2006 8:03 pm

no problem
hope to see new official release of madexcept soon

be happy to use it

emailaya · Post by **emailaya** » Fri Oct 20, 2006 7:35 am

Hi

i dont want to be pushy
just wanted to know if a new release will be out soon
and whether the subject issue is fixed there

thanks allot

Post by **madshi** » Mon Oct 30, 2006 6:16 pm

Here's a new beta build:

http://madshi.net/madCollectionBeta.exe

You can now set the undocumented variable "ForceUtf8" to "true". It's exported by madExcept.pas.

Do you know how I can check whether I must use Utf8 or not? I mean the normal encoding I've used until now did work quite fine for me - and it seems to be the default encoding normal email clients are using. So I'd like to keep using the old encoding, unless the subject contains chars which need Utf8. So it would be helpful if I could find out whether the subject I need to encode needs Utf8 or not. Any ideas?

emailaya · Post by **emailaya** » Mon Oct 30, 2006 7:54 pm

hi
thanks for this beta
should i just download and install it?

u wrote: "It's exported by madExcept.pas. "
but this release does not have source code, or does it?

where exactly can i ForceUtf8 property to TRUE?

regarding your question:
in order to be on the safe side
if the subject does not contain english characters
it should be converted to utf8

but mayb a property like u added is a good idea
(if i understood its purpose correctly)

Post by **madshi** » Mon Oct 30, 2006 8:42 pm

emailaya wrote:thanks for this beta
should i just download and install it?

Yes.

emailaya wrote:u wrote: "It's exported by madExcept.pas. "
but this release does not have source code, or does it?

It's also exported by madExcept.dcu.

emailaya wrote:where exactly can i ForceUtf8 property to TRUE?

Just add "madExcept" to the uses clause and then do "ForceUtf8 := true". That's it.

emailaya wrote:regarding your question:
in order to be on the safe side
if the subject does not contain english characters
it should be converted to utf8

That's not true. If a subject only contained english characters, I wouldn't need to do ANY encoding. I could just use "Subject: bla bla". Why then use "=?ISO-8859-1?Q?" in the first place?

If I send an email via Thunderbird with only english chars, there's no encoding used at all. If I send an email with german umlauts, Thunderbird is using "=?ISO-8859-1?Q?". If I send en email with russian chars, Thunderbird is using UTF8. So there must be a way to find out which encoding is needed when.

emailaya · Post by **emailaya** » Mon Oct 30, 2006 9:18 pm

u wrote: "That's not true" but then said the same as me

u wrote: So I'd like to keep using the old encoding, unless the subject contains chars which need Utf8

so if u want to be on the safe side, if a subject contains non english chars, convert it to utf8. if all subject is english chars, either do not encode anything or use the current default encoding iso_8859_1

there is a whole phylosophy about how to know which encoding to use
but UTF8 saves u lots of troubles and time

Post by **madshi** » Mon Oct 30, 2006 9:35 pm

Well, my goal is to behave similar to the email clients. And they use UTF8 only if they absolutely have to. That is what I'm trying to achieve.

Sometimes my mail client asks "shall I use UTF8?", especially if I reply to a mail which was encoded with UTF8. So I'm a bit uneasy with using UTF8 by default. I don't want madExcept email receivers to get nasty questions about UTF8.

emailaya · Post by **emailaya** » Mon Oct 30, 2006 9:42 pm

then u should read here for more information
http://synapse.ararat.cz/

emailaya · Post by **emailaya** » Mon Oct 30, 2006 9:55 pm

just tested the new beta
and it works perfect!

thanks allot

Post by **madshi** » Tue Oct 31, 2006 7:09 am

You're welcome!