CLDR drop or call for help

1 view
Skip to first unread message

Maciej Piechotka

unread,
Jan 28, 2009, 6:47:21 PM1/28/09
to Merb Global Mailing List
Every time I try to write a parser of CLDR data (or rather LDML parser)
I feel that the format was written to be write by humans not to be read
by machines - there is removed all of the redundant informations. As a
result there can be relatively many files which can be involved. The
data can be fetched from relatively arbitrary points via alias.

Itself it does not seem to be something hard - rather long and boring. I
feel that it is the point which stops me from pushing further MG.

If anybody want to take over the CLDR maintenance - please do so[1].
Otherwise I propose to publish 0.0.7 immediately and push further the
project dropping cldr support from the schedule. The cldr branch would
not be deleted in this case - it would be probably not developed.

Best regards

[1] Especially the first part would be hard - with writing LDML parser.
Then it should be relatively easy.

signature.asc

Alex Coles

unread,
Feb 14, 2009, 5:59:14 AM2/14/09
to Maciej Piechotka, Merb Global Mailing List

Sorry for the slow response. I think if its too time-consuming to
maintain, then you should leave development for the time-being. I
think CLDR is really interesting work -- I would love to have the time
to invest in this (I just don't, alas, at this moment).

Have you looked at http://github.com/joshmh/cldr ? There are obviously
others who are interested in this (even though the particular project
I mentioned has not been developed very far.

Alex

Maciej Piechotka

unread,
Feb 14, 2009, 10:39:36 PM2/14/09
to Alex Coles, Merb Global Mailing List

Yes. However most of the projects is unmaintained.

Regards

signature.asc
Reply all
Reply to author
Forward
0 new messages