Darn. I was hoping there was nothing underneath that particular rock. Thanks for turning it over.
--Mark On Wed, 2 Apr 2008, James Carlson wrote: > Date: Wed, 02 Apr 2008 18:13:44 -0400 > From: James Carlson <James.D.Carlson at Sun.COM> > To: Mark J. Nelson <Mark.J.Nelson at Sun.COM> > Cc: scm-migration-dev at opensolaris.org > Subject: Re: [scm-migration-dev] several messages > > Mark J. Nelson writes: >>> Given that I'd have to rewrite those ugly sed hacks to use them, I'm >>> somewhat inclined to stay with xgettext, and then complain if that >>> ever stops working with these no-so-shellish languages. >> >> My underlying point was twofold: first, that it's documented for C source. >> Second: that if the source is sufficiently C-like, it will likely work, >> but if "gettext" is changed to something more like "GetText," or otherwise >> manipulated, it could fail. >> >> So it would be nice to validate that the .py.po suffix rule actually works >> correctly, as you already have with the .pl.po one. > > Ah, ok. gettext in Perl is easy and familiar to people who write in > other languages. I mistakenly assumed that it'd be just as easy in > Python (why wouldn't it be?), but after reading the documentation: > > http://www.python.org/doc/current/lib/module-gettext.html > > ... it's clearly not. It uses _() as a wrapper instead of the > gettext() that everyone else uses. What good is a wheel if you can't > reinvent it at random? > > Given that, I'll just nuke the .py.po rule. If you need to translate > Python stuff, you'll need to wade through that documentation on your > own and figure out how pygetext.py works. > > -- > James Carlson, Solaris Networking <james.d.carlson at sun.com> > Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 > MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 > _______________________________________________ > scm-migration-dev mailing list > scm-migration-dev at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/scm-migration-dev >
