Index: openacs-4/packages/acs-lang/www/doc/i18n-requirements.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-lang/www/doc/i18n-requirements.html,v diff -u -r1.5 -r1.6 --- openacs-4/packages/acs-lang/www/doc/i18n-requirements.html 29 Dec 2017 10:51:45 -0000 1.5 +++ openacs-4/packages/acs-lang/www/doc/i18n-requirements.html 3 Sep 2024 15:37:33 -0000 1.6 @@ -310,7 +310,7 @@ character set before loading the files, probably from the filename.

Submitted Form Data Character Set

-50.30 Data which is submitted with a HTTP request using a +50.30 Data which is submitted with an HTTP request using a GET or POST method may be in any character set. The system must be able to determine the encoding of the form data and convert it to Unicode on demand. @@ -388,21 +388,20 @@ supported language.

VI.G Time Zones

-
90.10 Provide API support for specifying a time -zone +
90.10 Provide API support for specifying a timezone

90.20 Provide an API for computing time and date operations which are aware of timezones. So for example a calendar module can properly synchronize items inserted into a calendar from -users in different time zones using their own local times.

-

90.30 Store all dates and times in universal time zone, +users in different timezones using their own local times.

+

90.30 Store all dates and times in universal timezone, UTC.

-

90.40 For a registered users, a time zone preference +

90.40 For a registered users, a timezone preference should be stored.

-

90.50 For a non-registered user a time zone preference +

90.50 For a non-registered user a timezone preference should be attached via a session or else UTC should be used to display every date and time.

-

90.60 The default if we can't determine a time zone is to -display all dates and times in some universal time zone such as +

90.60 The default if we can't determine a timezone is to +display all dates and times in some universal timezone such as GMT.

VI.H Database