Working code
Joergen W. Lang | 30. Dezember 2006We held our first perldoc 2.0 hackathon on Thursday before christmas.
You can find the first bits of working code in the sourceforge SVN repository.
Prerequisites:
As a result I have bumped the project status to 2. pre-alpha.
myspace layout generators myspace love quotes myspace music codes myspace clock widgets thomas myspace editor myspace player skins free myspace cursors cute myspace stuff cute myspace icons myspace login page myspace bulletin surveys how to unblock myspace myspace html codes myspace comment graphics free backgrounds funny myspace comments free layouts myspace com
hentai anime free moviessex toon moviepreteen moviesmovies pantyhose freemovies bustymovies sample musclemenmovie adult postmovies big cocktitty fucking moviesfarm movies alien ant
sucking movies nipplebeach old moviesmovies old scaryposter poster movie original movieparis porn movie hiltonssex paris moviepig sex moviestheme pokemon movieporn movies onlinepregnant porn movies
And the question is:
Why don’t use pootle and Pootle server?
http://www.wordforge.org/static/wordforge-functional_specificaions.html#pootle
Translation of Perl doc can be a big project for Wordforge…
Or… you can download pootle and run it in a server.
Then, we can to use po files or the new xliff files. And pootle can work with TBX glossary files and TMX translation memories files.
It definitely is closest to ideal. No offence meant, but:
* Pootle is *slooow*
* it does not use a database backend
* it is – like most TMSs around – made for the translation
of strings – not entire paragraphs
* it’s in Python, so it’d be tricky for a Perl hacker to
build in needed features. Everything has to be asked for…
More on this subject, soon.
Joergen
(hoping to be able to spent more time on the project in the near future)