[Bug #83] [Language] Receiving notification email in unreadable encoding if using Russian local settings

http://anthill.vmlinuz.ca/anthill/query.php?bug=83

--- /home/zeus/www/anthill.vmlinuz.ca/bugs/html/shadow/83	2003-11-06 23:11:09.000000000 -0700
+++ /home/zeus/www/anthill.vmlinuz.ca/bugs/html/shadow/83.tmp.e3h1Bs	2003-11-06 23:11:09.000000000 -0700
@@ -161,3 +161,46 @@

 That's it.

+Comment posted: 2003-11-06 11:11 PM by [email protected]
+
+No, the RFC doesn't help me.  Maybe I'm too stupid to understand it.  =)
+
+I really don't know how to progress with this.  I don't see an easy way to do it.  You have
+to remember the diverse userbase here.  For instance, if your locale is set to russian
+and russian characters are displayed on the webpage for you, I can use that as a
+trigger to encode the message in russian, provided I knew how to properly do it.  Well,
+that's fine for you, but what about me?  I don't speak russian, so why do I need it in
+russian?
+
+Also, assume that, for the sake of argument, you post something in russian and
+someone else posts something in japanese, to the same bug.  If you post in russian,
+and I again use your browser preference as the trigger for inserting the headers, what
+happens to the japanese characters?  Or if he posts in japanese and the message is
+encoded for japanese, what happens to your russian characters?
+
+This is a big problem that goes beyond the scope of what I think can be done.  Yes, it
+would be fantastic to be able to do this, but the only way I can even remotely see this
+being plausible is to do russian encoding on a site where it is 100% russian... all the
+users are russian, all the postings are russian, etc.  Ie. in a russian company.  But for
+something like an open site (like this one), I don't think there is a good way to handle
+this appropriately.
+
+I don't have the skills to look at the comments in the database to use those as a trigger
+for how to encode messages (because, if I post this comment, and with the russian text
+in here, it will still not get encoded to your liking).  How do I determine, if I could analyze
+the comments, what encoding gets priority?
+
+I've already, for 0.2.5, removed what I can see that uses gettext() in email messages.
+All email messages will now have "prefab" text go out in english only.  This is a sanity
+thing.
+
+Unless you can come up with some really bright ideas (because I have none) on how to
+tackle this, I think we may have to just leave it as is.  I know that isn't the greatest, but I
+think it's the best.  I can have in the "NOTE: Please use plaintext only..." string below the
+comment boxes asking people to post comments in english only.
+
+The whole purpose of using gettext was to allow people navigating the site to be able to
+do so in their native tongue.  I didn't anticipate these issues when starting out, and I
+suppose that was a lack of foresight on my part.  But I honestly don't know if there is any
+sufficient way to handle it.
+

----
You are receiving this notice because you are the assignee, reporter, or a
watcher for this bug report.

_______________________________________________
Anthill-workers mailing list
Anthill-workers-+mQDA36h6dWw5LPnMra/[email protected]
http://vmlinuz.ca/mailman/listinfo/anthill-workers