Index: openacs-4/packages/acs-core-docs/www/xml/kernel/i18n-requirements.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/i18n-requirements.xml,v diff -u -N -r1.5 -r1.5.6.1 --- openacs-4/packages/acs-core-docs/www/xml/kernel/i18n-requirements.xml 17 Jul 2006 05:38:38 -0000 1.5 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/i18n-requirements.xml 15 May 2009 12:42:20 -0000 1.5.6.1 @@ -686,48 +686,45 @@ install instructions for both PostgreSQL and Oracle. -Email and -Messaging + -When sending an email message, just as when delivering the -content in web page over an HTTP connection, it is necessary to be -able to specify what character set encoding to use. - + -
-110.10 The email message sending API -will allow for a character set encoding to be specified. + Email and Messaging -110.20 The email accepting API will -allow for character set to be parsed correctly (hopefully a well -formatted message will have a MIME character set content type header) -
+ When sending an email message, just as when delivering the + content in web page over an HTTP connection, it is necessary to be + able to specify what character set encoding to use, defaulting to UTF-8. - Mail is not internationalized. The following issues -must be addressed. +
+ 110.10 The email message sending API + will allow for a character set encoding to be specified. + + 110.20 The email accepting API + allows for character set to be parsed correctly (the message has a MIME + character set content type header) +
+ + Mail is not internationalized. The following issues must be addressed. - - Six different functions currently call ns_sendmail. This - means that there are six different end points for sending - mail. This should be brought down to no more than two (one - for acs_mail and one for acs_mail_lite), and ideally just - one. Functions that currently call ns_sendmail directly - should instead call acs_mail_lite. - - - Outgoing email functions (acs_mail and acs_mail_lite) must do - the following: 1) Determine the appropriate language or - languages to use for the message subject and message body. 2) - Encode the subject and body appropriately and set message - headers, in accordance with RFC 3282 - (http://www.ietf.org/rfc/rfc3282.txt) and other RFCs. - + + + Many functions still call ns_sendmail. This + means that there are different end points for sending + mail. This should be changed to use the acs-mail-lite API instead. + - Extreme Use case: Web site has a default language of Danish. A forum is set up for Swedes, so the forum has a package_id and a language setting of Swedish. A poster posts to the forum in Russian (is this possible?). A user is subscribed to the forum and has a language preference of Chinese. What should be in the message body and message subject? -INCOMPLETE - The mail functions in acs_mail and acs_mail_lite -are not internationalized. + + Consumers of email services must do + the following: Determine the appropriate language or + languages to use for the message subject and message body + and localize them (as in notifications). + + + Extreme Use case: Web site has a default language of Danish. A forum is set up for Swedes, so the forum has a package_id and a language setting of Swedish. A poster posts to the forum in Russian (is this possible?). A user is subscribed to the forum and has a language preference of Chinese. What should be in the message body and message subject? + Incoming mail should be localized.