Quoted printable w/ iso-8859-2

[john1979]

Hello,

our company is just a few weeks before the complete transition to Scalix. We found 1 very important issue. As we are from the Czech Republic, ASCII often is not enough for us. All encoding/transmision seems OK, except for quoted printables in address (ie To) and Subject headers.
Sent message containing

Code: Select all

Subject: Test diakritiky: =?ISO-8859-2?Q?=EC=B9=E8=F8=BE=FD=E1=ED=E9=EF=BB?=
 =?ISO-8859-2?Q?=F2=F9=FA_?=

in the header (also saved properly via imap) results into

Code: Select all

Subject: Test diakritiky: **************

in the received header (all non-ASCII characters are substituted by asterisks). It seems like character representation in the message storage does not fit our needs, but it is just a hypothesis. I have tried several settings, but none of them changed the behavior, so I believe, you can help me easily.

The question nr. 2 is: where shall we set character set for messages/subjects sent by webmail? It uses quoted printable iso-8859-1 as default.

Thanks alot!

[ScalixSupport]

Hi,

ISO8859-2 is not a supported character set as of now. Our next version will add support for UTF8 which will probably get you going much better.

Cheers,

Sascha.

[john1979]

Hi Sascha,

your statement is either incomplete or false, because

Code: Select all

From: =?iso-8859-2?Q?Kate=F8ina_Hrube=B9ov=E1?= <email@domain.cz>

is displayed properly inside both webmail web client and inside imap mail client as

Code: Select all

Kateřina Hrubešová <email@domain.cz>

Also message bodies work well w/ iso-8859-2 quoted printables, as I have already written. So the problem is not pricipal, but specific to the Subject header.

So, please, could you be more concrete (exact) in your answers? It is both crucial and urgent for us.


Thanks in advance.

[dkelly]

Sascha is correct. We do not currently support that character set for the very reason you have illustrated, there is no consistency between how we handle the body parts and subject data.

This has been fixed for the next major release.

Cheers

Dave

[john1979]

So what is the message? Will iso-8859-2 work everywhere in the new version? What about windows-1250? Although normal people do not use it, majority in the Czech Republic does.

In either case, when will you release this version? Proper handling of diacritic is a normal functionality in these days, mailserver w/o it would not make a good image of us before the clients.

Thanks for the clarification.

[gren]

Both ISO-8859-2 and WINDOWS-1250 will be supported with the next major release for body parts and for subjects etc. i.e. It should work "everywhere".

Regards,
Gren.

[john1979]

Great!!!

And once more the last question:
When do you plan to launch the next major release?

Is there any road map / issue tracking system available to the public?

Regards
John

[dkelly]

We were hoping to keep you on tenterhooks

All things being equal, we're expecting this to be available late Q3 this year.

Cheers

Dave

[florian]

Hi John,

you're persistent! Which is good! So maybe one or two further clarifications....

1. Scalix 11 will have very broad character set support; actually, as our character set conversion will be based on the iconv framework, we'll be supporting all character sets that are supported by iconv - please type the "iconv -l" command for a complete list.

2. Scalix 11 will be generally available Q4/2006, however, we'll make a Community Preview version available for LinuxWorld San Francisco, which is next week, so you will be able to start testing if this meets your requirements later this month.

3. As part of our Open Source strategy, we'll be making public bug and issue tracking available as well; check our Open Source press release for details and stay tuned for Linux World and shortly thereafter.

Exciting weeks ahead at Scalix!

Cheers, looking forward to hear back from you how all this works,
Florian.

[john1979]

Hi Florian,

you are right, I am persistent in situations of high importance, especially when I do not get complete answers. Thanks for yours, they finally satisfy me.
(Nevertheless the fact, that the local distributor is not aware of (or says nothing about) this feature crucial for our conditions seems funny to me.)

As I know iconv, I am now confident, that Scalix will work in our regional conditions in short time. The sooner we get a functional pre-release, the better, and we can also provide you a feedback concerning all different situations affected by encoding/character sets (ie calendar, which is neither working properly at the moment).

We will watch public resources, if there were any possibilities not mentioned that way, please, inform us.


Thanks again, regards
John

[Michal1966]

Hi Florian and the other

I am Michal - a John`s boss.

For us is support of czech characters absolutely necessary.
You can imagine this problem as unpossibility to write in english keyboards characters "q","w","e","r' and "t". It`s a good example - instead of this characters our groupware will write only "_" or "?".
Solution (of course in betaversion) either exists or not exists.
If solution exists, just give to us some link and instructions.

We would like to use Scalix, because of Scalix is conform to our needs. In case of impossibility to write national characters, this solution is valueless for us.

Sorry for this persistence. Our local distributor of Scalix cannot help to us. I am responsible in our company for implementation of groupware and cannot explain this problem to our board.

BTW: The best testers for support of czech language are native czech people

Thanks for help, have a nice day

Michal

[florian]

Hi Michal,

thanks again for your message. I'll ask you though to hold off for a few more days - you will certainly be able to start testing Scalix 11 this month - stay tuned watching scalix.com for announcements!

if you need a more precise date, please contact me directly - my email is florian - at - scalix dot com.

Cheers,
Florian.