Skip Menu |

This queue is for tickets about the Date-Manip CPAN distribution.

Report information
The Basics
Id: 37596
Status: resolved
Priority: 0/
Queue: Date-Manip

People
Owner: Nobody in particular
Requestors: melazyboy [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: PATCH (M:I, failed test, YAML Translations)
Has three large components: * YAML Translations, making the Manip.pm thousands of lines shorter * Failed test for bug 37573 * New build system for 35728
Subject: diff.patch

Message body is not shown because it is too large.

Thanks for the patch. I'll definitely make sure that the bugs are fixed. As far as the YAML conversion, I'm going to have to think about that for a while. One of the problems with Date::Manip is that it's language handling is very crude. An english syntax is used in all cases with foreign words substituted for their english equivalent. That's not really the correct way to do things, since they may have significantly different syntaxes. I am almost done with a complete overhaul of Date::Manip, separating it into several modules. As soon as that is done, and a new version released, I'm going to redo the parsing to be more flexible. As I'm doing that, I can see if YAML is a good option for what I want to do.
From: melazyboy [...] gmail.com
On Thu Jul 10 15:43:57 2008, SBECK wrote: Show quoted text
> I can see if YAML is a good option for what I want to do.
Yea, and this is already set up with M:I:S and F:SD. My suggestion would be to keep the YAML conversion (obviously). It makes the module much more maintainable and eliminates the sore ideas like marking up unicode characters in ASCII and such. This way a German author can maintain the YAML file. I could externalize the translations entirely if you are interested in adopting M:Ito a new API. It would also permit interoperability with DateTime.
From: melazyboy [...] gmail.com
On Thu Jul 10 15:53:19 2008, EvanCarroll wrote: Show quoted text
> On Thu Jul 10 15:43:57 2008, SBECK wrote:
> > I can see if YAML is a good option for what I want to do.
> Yea, and this is already set up with M:I:S and F:SD. My suggestion would > be to keep the YAML conversion (obviously). It makes the module much > more maintainable and eliminates the sore ideas like marking up unicode > characters in ASCII and such. This way a German author can maintain the > YAML file. I could externalize the translations entirely if you are > interested in adopting Date:Manip to a new API. It would also permit > interoperability with DateTime.
Languages were stored in YAML as of 6.00.