headers
Juergen Nickelsen | 9 Feb 13:58
Picon
Picon
Favicon

Consquences of $lossy_encoding?

Hello all,

in the SquirrelMail installation I have inherited recently, we support
English and German, both with the ISO 8859-1 charset. When replying to
UTF8-encoded messages containing, for instane, german umlauts, there is
the usual charset problem.

I am preparing a new installation at the moment; with that one, I want
to do everything with UTF-8 to fix this class of problems. Of course
user settings, signatures, and addressbooks will have to be converted
(and we will probably put them into a database, while we are at it), so
this is not really a short-term solution.

But I understand that "$lossy_encoding = true" will heal at least some
of the problems, and that is what I would like to try with the currently
productive installation.

So, now my question is: are there any other consequences than the
intended one I should be aware of when I set $lossy_encoding = true?

Best regards,
Juergen.

--

-- 
Juergen Nickelsen <juergen.nickelsen <at> fu-berlin.de>
Freie Universitaet Berlin, Zentraleinrichtung fuer Datenverarbeitung
Fabeckstrasse 32, 14195 Berlin, Telefon +49.30.838-50740

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
(Continue reading)

Permalink | Reply |
headers
Juergen Nickelsen | 9 Feb 16:02
Picon
Picon
Favicon

Re: Consquences of $lossy_encoding?

On 09.02.2012 13:58, Juergen Nickelsen wrote:

> in the SquirrelMail installation I have inherited recently,
[...]
> So, now my question is: are there any other consequences than the
> intended one I should be aware of when I set $lossy_encoding = true?

Sorry, I forgot: This is a 1.4.21.
Regards, Juergen.

--

-- 
Juergen Nickelsen <juergen.nickelsen <at> fu-berlin.de>
Freie Universitaet Berlin, Zentraleinrichtung fuer Datenverarbeitung
Fabeckstrasse 32, 14195 Berlin, Telefon +49.30.838-50740

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
-----
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-users <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Permalink | Reply |
headers
Tomas Kuliavas | 9 Feb 18:04
Picon
Gravatar

Re: Consquences of $lossy_encoding?


Juergen Nickelsen-3 wrote:
> 
> Hello all,
> 
> in the SquirrelMail installation I have inherited recently, we support
> English and German, both with the ISO 8859-1 charset. When replying to
> UTF8-encoded messages containing, for instane, german umlauts, there is
> the usual charset problem.
> 
> I am preparing a new installation at the moment; with that one, I want
> to do everything with UTF-8 to fix this class of problems. Of course
> user settings, signatures, and addressbooks will have to be converted
> (and we will probably put them into a database, while we are at it), so
> this is not really a short-term solution.
> 
> But I understand that "$lossy_encoding = true" will heal at least some
> of the problems, and that is what I would like to try with the currently
> productive installation.
> 
> So, now my question is: are there any other consequences than the
> intended one I should be aware of when I set $lossy_encoding = true?
> 
If you reply to email asking for 1 billion euros, your answer will quote
only 1 billion question marks.

If you reply to Cyrillic text, all text will be converted to ?.

lossy_encoding = true converts all symbols unsupported by translation
charset to question marks.
(Continue reading)

Permalink | Reply |
headers
michael crane | 9 Feb 18:17
Picon

Re: Consquences of $lossy_encoding?

On 9 February 2012 17:04, Tomas Kuliavas <tokul <at> users.sourceforge.net> wrote:
<snip>
> lossy encoding improves existing situation, if webmail users handle only
> emails that contain texts in their native or similar language. For Germans
> with iso-8859-1 main problems are smart quotes and euro symbol.

Of course the sensible solution is for everybody to use english.
<duck>

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
-----
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-users <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Permalink | Reply |
headers
Juergen Nickelsen | 9 Feb 18:23
Picon
Picon
Favicon

Re: Consquences of $lossy_encoding?

On 09.02.2012 18:17, michael crane wrote:
> Of course the sensible solution is for everybody to use english.

Right. And use ASCII like God has created it. (Pardon my French. ;-)

--

-- 
Juergen Nickelsen <juergen.nickelsen <at> fu-berlin.de>
Freie Universitaet Berlin, Zentraleinrichtung fuer Datenverarbeitung
Fabeckstrasse 32, 14195 Berlin, Telefon +49.30.838-50740

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
-----
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-users <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Permalink | Reply |
headers
Juergen Nickelsen | 9 Feb 18:23
Picon
Picon
Favicon

Re: Consquences of $lossy_encoding?

On 09.02.2012 18:04, Tomas Kuliavas wrote:

> If you reply to Cyrillic text, all text will be converted to ?.

Yes, I have tried exactly that, finally putting the spam in Russian to
some good use. :-)

> lossy encoding improves existing situation, if webmail users handle only
> emails that contain texts in their native or similar language. For Germans
> with iso-8859-1 main problems are smart quotes and euro symbol.

Right. But as this text would be written in some other encoding that ISO
8859-1, it wouldn't come out right anyway. Okay, if that's everything, I
think we can go with it. Thanks!

Regards, Juergen.

--

-- 
Juergen Nickelsen <juergen.nickelsen <at> fu-berlin.de>
Freie Universitaet Berlin, Zentraleinrichtung fuer Datenverarbeitung
Fabeckstrasse 32, 14195 Berlin, Telefon +49.30.838-50740

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
-----
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
(Continue reading)

Permalink | Reply |
headers
Paul Lesniewski | 9 Feb 19:38
Favicon

Re: Consquences of $lossy_encoding?

On Thu, Feb 9, 2012 at 4:58 AM, Juergen Nickelsen
<juergen.nickelsen <at> fu-berlin.de> wrote:
> Hello all,
>
> in the SquirrelMail installation I have inherited recently, we support
> English and German, both with the ISO 8859-1 charset. When replying to
> UTF8-encoded messages containing, for instane, german umlauts, there is
> the usual charset problem.
>
> I am preparing a new installation at the moment; with that one, I want
> to do everything with UTF-8 to fix this class of problems. Of course
> user settings, signatures, and addressbooks will have to be converted
> (and we will probably put them into a database, while we are at it), so
> this is not really a short-term solution.

At some point in the next year, we'll start pushing harder to get all
the SquirrelMail translations changed over to all utf-8.  You of
course can do so on your own ahead of time.

--

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
(Continue reading)

Permalink | Reply |
headers
Juergen Nickelsen | 10 Feb 07:52
Picon
Picon
Favicon

Re: Consquences of $lossy_encoding?

On 2012-02-09 19:38, Paul Lesniewski wrote:

> At some point in the next year, we'll start pushing harder to get all
> the SquirrelMail translations changed over to all utf-8.

That is a good thing! Recently I read someone stating, half-jokingly, 
that there are only two kinds of character encodings left -- UTF-8 and 
obsolete ones. I am warming to that idea myself, but it is not really 
easy, of course.

> You of course can do so on your own ahead of time.

As I see, our german squirrelmail texts are already largely converted to 
using html character entities, so they are charset independent, and we 
can (with the next installation, after converting user data) switch to 
UTF-8 generally. I also see that there are a few exception, perhaps from 
later editing, but these can be fixed trivially, of course.

Allegedly they also contain a few text improvements, so it might be 
useful to push them back into your direction some time anyway. Please 
don't hesitate to remind me I said that when you need them. ;-)

Best regards,
Juergen.

--

-- 
Juergen Nickelsen <juergen.nickelsen <at> fu-berlin.de>
Freie Universitaet Berlin, Zentraleinrichtung fuer Datenverarbeitung
Fabeckstrasse 32, 14195 Berlin, Telefon +49.30.838-50740
(Continue reading)

Permalink | Reply |

Gmane