Re: ANNOUNCE: DateTime 0.14

[Eric Cholet]

It isn't clear from the Changes files that the switch
from Language to Locale also means that day and month
names are now returned in utf8 instead of latin1, at
least that's what I see when using 'fr'. Am I correct
in assuming that this change cames about in 0.14?
(I have the self inflicted issue of having code that
must work with DateTime 0.10, 0.13 and 0.14)
--
Eric Cholet

Re: ANNOUNCE: DateTime 0.14

[Ben Bennett]

On Mon, Jul 28, 2003 at 07:04:12PM +0200, Eric Cholet wrote:
 Dave Rolsky wrote:
[...]
 But don't latin-1 and utf8 overlap for the first 255 chars anyway?
 
 No they don't. Common misconception it seems.

To clarify, UTF-8 and ASCII overlap, but any character with the high
bit set incicates that this is a multi-byte character in UTF-8 so the
extended characters in latin-1 can not match.

However, the first 255 characters in Unicode overlap with Latin-1, but
that is not really helpful since you are either using UTF-8 or a
constant multi-byte encoding and need to add the extra bytes...

-ben

ANNOUNCE: DateTime 0.14

[Dave Rolsky]

Well, here goes nothing ...

Still need to get to the root of the infinite number problems of Win32.
Volunteers wanted ...


0.14 2003-07-23

[ BACKWARDS INCOMPATIBILITIES ]

- The DateTime::Language modules are no longer being developed or
distributed as part of the DateTime.pm distribution.

Because of this, all language parameters should now be replaced by
locale parameter.  The language parameter is deprecated and will
be removed in a future release.

Also note that locales should be specified via ISO codes, not names
like English.  The old DateTime::Language names will continue to
work indefinitely, but they load DateTime::Locale objects instead.

- Similarly, the language and DefaultLanguage methods are now
deprecated in favor of locale and DefaultLocale.


[ IMPROVEMENTS ]

- DateTime::Duration now returns the object from mutator methods, in
order to make method chaining possible.  Suggested by Ben Bennett.

- If the value for second given to new() is 60 or 61, then it must be
a valid leap second.

- DateTime now uses DateTime::Locale for localization, which allows
for real language and territory based localization.  The locale code
is generated from the ICU project's data, and is much more complete
than the DateTime::Language modules.  However, we are losing
(hopefully only temporarily) support for the various African languages
contributed by Daniel Yacob.  Support for those languages should
return in a future release of DateTime::Locale.

- Support for the '%c', '%x', and '%X' strftime format specifiers,
which output localized date and time strings.

- Added the time_zone_long_name method, primarily for the benefit of
DateTime::Locale.

- Added a note to the DateTime::Infinite docs warning that it may not
work well on Win32.

[ BUG FIXES ]

- DateTime::Duration was not consistent in how it handled mixed
positive and negative constructor parameters.  Reported by Ben
Bennett.



-dave

/*===
House Absolute Consulting
www.houseabsolute.com
===*/