Make default_charset utf-8?

[Thijs Kinkhorst]

Hi all,

Currently config_default.php defines the SquirrelMail default charset to be
iso-8859-1 (latin-1). Would choosing utf-8 not be a much more sensible
default value?


Thijs


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-----
squirrelmail-i18n mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
Information about translations: http://squirrelmail.org/wiki/LanguageTranslation
List address: squirrelmail-i18n@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.internationalization
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-i18n

[Paul Lesniewski]

On Sat, May 24, 2008 at 1:22 AM, Thijs Kinkhorst <kink@...> wrote:
> Hi all,
>
> Currently config_default.php defines the SquirrelMail default charset to be
> iso-8859-1 (latin-1). Would choosing utf-8 not be a much more sensible
> default value?

Maybe only in dev?  The plan is to make dev all utf-8 anyway.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-----
squirrelmail-i18n mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
Information about translations: http://squirrelmail.org/wiki/LanguageTranslation
List address: squirrelmail-i18n@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.internationalization
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-i18n

[Miro Konecny]

> Currently config_default.php defines the SquirrelMail default charset to be
> iso-8859-1 (latin-1). Would choosing utf-8 not be a much more sensible
> default value?

Hello Thijs,

using utf-8 would of course make much more sense today, however I'm afraid
that changing $default_charset is not enough. This setting is only used by
en_US translation, while all other translations ignore this setting and use their
own charset. This has confused several users in the past, including myself.
   
Thus I'd propose to change all translations to utf-8 as discussed with Fredrik
in another thread. After this change, SM would only use utf-8 for everything
- thus $default_charset would become unnecessary and could be removed.
This will make the en_US translation behave the same way as all others,
removing the potential source of user confusion.

Regards,
Miro


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-----
squirrelmail-i18n mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
Information about translations: http://squirrelmail.org/wiki/LanguageTranslation
List address: squirrelmail-i18n@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.internationalization
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-i18n

[Thijs Kinkhorst]

Hi Miro,

On Mon, May 26, 2008 09:04, Miro Konecny wrote:

> using utf-8 would of course make much more sense today, however I'm
> afraid that changing $default_charset is not enough. This setting is only
> used by en_US translation, while all other translations ignore this
> setting and use their own charset. This has confused several users in the
> past, including myself.
>
> Thus I'd propose to change all translations to utf-8 as discussed with
> Fredrik
> in another thread. After this change, SM would only use utf-8 for
> everything - thus $default_charset would become unnecessary and could be
> removed. This will make the en_US translation behave the same way as all
> others, removing the potential source of user confusion.

Right, I'll readily admit that I'm not well versed with the internals of
SquirrelMail i18n, but as you put it makes sense. Perhaps we could at
least, until this process is completed, add an extra comment to the config
file for that option to indicate what "default_charset" really means?


Thijs


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-----
squirrelmail-i18n mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
Information about translations: http://squirrelmail.org/wiki/LanguageTranslation
List address: squirrelmail-i18n@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.internationalization
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-i18n