[Bug 224245] Merge Review: squirrelmail

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=224245





--- Comment #20 from Tomas <tokul at users.sourceforge.net>  2009-01-21 04:48:32 EDT ---
(In reply to comment #19)
> Tomas, if you could explain me (irc?) something about the utf-8 vs. CJK mess,
> it would be really appreciated. I've got this package with some fixes for CJK
> and that confuses me... I thought utf-8 should be able to handle it, so I'm
> little bit confused about all CJK workarounds/patches.

If you need explanation about patches in squirrelmail-1.4.16-1.fc10.src.rpm,
see information in bugzilla.

squirrelmail-1.4.6-japanese-multibyte-view-body.patch - RH bug #194457
squirrelmail-1.4.6-japanese-multibyte-view-text.patch - RH bug #195452
squirrelmail-1.4.6-zenkaku-subject-convert.patch - RH bug #196017

All patches written by RH/Fedora and information about them was never submitted
to upstream. I can't explain why scripts are modified without seeing broken
emails. zenkaku-subject-convert.patch might be needed because according to
Wikipedia article on Katakana, hankaku (halfwidth form of katakana) is not
supported by ISO-2022-JP.

If you need explanation why SquirrelMail Japanese translation works that way -
it was written that way by third party (risumail.jp) contributors in
SquirrelMail 1.3-dev branch. In SquirrelMail 1.4.4 and older utf-8 and charset
conversion support was very simple and limited to message display. Only
SquirrelMail 1.4.5 improved charset handling in compose. I suspect that
risumail.jp just wanted to get things working and they did it in their own
"works for us, lets ignore other part of the world" way.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.