Unicode is so broken in 5.6.x ...
0.1401 2003-07-24
[ BUG FIXES ]
- Fix a test failure in 13strftime.t under Perl 5.6.1 (and probably
5.6.0).
-dave
/*===
House Absolute Consulting
www.houseabsolute.com
===*/
On Wed, 23 Jul 2003, Ricardo SIGNES wrote:
> Is there a good way to determine whether to not to return Unicode
> strings? That's what I'm doing now, but obviously it's not so nice at
> the console. I don't do much serious work with Unicode in Perl, and
> there might be an obvious solution I don'
On Wed, 23 Jul 2003, Ben Bennett wrote:
> I hate to say this but the language stuff may be deprecated in favor
> of locales...
>
> But if you are willing to convert this to a locale definition I would
> like to ask you about some extra stuff for my DateTime::Format::Common
> parser. But I am not
Again, test results on non-UNIX platforms are appreciated.
1.07_93 2003-07-23
- Henrik's code explicitly didn't work with negative epoch values,
which is not good. Now we assume that they are allowed, except on
MacOS, which is known to use an unsigned int for time_t.
- Document that dates befo
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.
Not terribly exciting by itself, but look for DateTime.pm 0.14 coming
soon, which will make use of this.
-dave
/*===
House Absolute Consulting
www.houseabsolute.com
===*/
On Wed, 23 Jul 2003, Joshua Hoblitt wrote:
> You'll have to generate the locale files from the icu-xml descriptions
> (instructions are in the dist). Or if you wait about a week DT::Locale
> will hopefully be released to CPAN (crosses arms, looks at Dave).
Poof, done.
/*===
For those of you that don't track DT CVS commits I added ./docs/datetime-namespace.pod
to the website about a week ago along with some other minor changes to the developer
docs.
I'd already updated the pod version to reflect the changes coming in '0.14' but I
hadn't synced this with the html ve
> I hate to say this but the language stuff may be deprecated in favor
> of locales...
Maybe eq 'is' in what will soon be released as DateTime '0.14'.
> But if you are willing to convert this to a locale definition I would
> like to ask you about some extra stuff for my DateTime::Format::Common
>
Hi All,
I need to bring everyone up to date on the status of the Astro
stuff. I have been in contact with Tim Jenness on moonrise
issues and here is what has transpired:
On Tue, 22 Jul 2003, Hill, Ronald wrote:
> > Hi Tim,
>
> >
> > > Sure - I can't guarantee to be able to find the time since
> I wanted to use the timezone long names for users to indicate their current
> timezone/DST but many of the major cities are missing from the list. How
> does somebody from say, America/Dallas, indicate their timezone? I'm
> assuming that they would select the nearest city to their current locatio
I wanted to use the timezone long names for users to indicate their current
timezone/DST but many of the major cities are missing from the list. How
does somebody from say, America/Dallas, indicate their timezone? I'm
assuming that they would select the nearest city to their current location
which
> For the rest of the list: I have a question about the use and implementation
> of TimeZone names. Can I ask it here or is there another list where it would
> be more OT. Not sure if this list is just for the development of the
> package.
Have you looked at the FAQ? If so and it didn't answer yo
Rod, Ron sent the attachment direct to my email addr and I have just
forwarded it on to yours. I believe you need Perl v5.8. I installed the
packages using PPM3. As I mentioned in my previous post one of the modules
DateTime depends on wasn't installed automatically by PPM3 and croaked the
process.
14 matches
Mail list logo