50.20 Tcl page script files can be authored in any character set. The system must have a way to determine the character set before loading the files, probably from - the filename.
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.
50.35 The developer must be able to
@@ -251,17 +251,15 @@
given locale with ORDER BY clauses in
queries.
80.40 The system must handle full-text search in any supported language.
90.10 Provide API support for specifying -a time zone
90.20 Provide an API for computing time +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 +calendar from users in different timezones using their own local times.
90.30 Store all dates and times in -universal time zone, UTC.
90.40 For a registered users, a time -zone preference should be stored.
90.50 For a non-registered user a time -zone preference should be attached via a session or else UTC should +universal timezone, UTC.
90.40 For a registered users, a timezone preference should be stored.
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 GMT.
100.10 Since UTF8 strings can use up to +determine a timezone is to display all dates and times in some +universal timezone such as GMT.