> [snip] finally, we are interested in the new online .po editor you have
> launched with your last version, but quite a few of our projects
> easily have (many) more than 100 strings, which I understand is your
> current cut-off point.
The current code in the development branch fixes this limitation,
thanks to some great work done by Diego! I'm not sure if you've given
the Transifex appliance a shot yet, but basically it is a software
appliance that you can download (or launch on EC2 for instance) with
all the pieces needed to run Transifex. I maintain the appliance and
have a development branch (as well as a stable version) that is in
sync with Transifex main code line. It is, in my humble opinion, a
great way to test drive Transifex in a pristine environment.
I'll let the Transifex guys chime in on the other points of your
email, but I'm really excited that you're enjoying your experience and
if you're interested in trying out the Transifex appliance, I'll be
more than glad to lend you a hand:
http://www.rpath.org/ui/#/appliances?id=http://www.rpath.org/api/products/transifex
Cheers,
--
Og B. Maciel
oma...@foresightlinux.org
ogma...@gnome.org
ogma...@ubuntu.com
GPG Keys: D5CFC202
http://www.ogmaciel.com (en_US)
http://blog.ogmaciel.com (pt_BR)
Hello everybody,
I am a software engineer at Mozilla and am working on the "Verbatim"
project, Mozilla's L10n project for websites. We've been investigating
Transifex as an option for centralizing our web site localization, and
we like it a lot.
We were wondering if someone would be willing to help us out a little
at getting a Transifex instance up and running for us. I noticed that
out of the box, I was able to point Transifex at a .po-based website
of ours and it worked great.
However, there are a few things we'd need to get into Transifex to
make it usable with our current projects.
- we have a localizable Tikiwiki instance and would like to either use
some sort of pre-checkout and pre-commit "hook" in Transifex to
convert the Tikiwiki strings into .po and back, or we could write a
new "i18n model" handler, whichever is easier.
- second, we would like our SVN history to show proper author
information even if committed through Transifex. During the course of
the Verbatim project, we've solved this problem before, and were
interested in getting this included in Transifex (as an option, not
requirement): http://micropipes.com/blog/2008/09/19/committing-to-svn-securely-from-a-web-application/
- finally, we are interested in the new online .po editor you have
launched with your last version, but quite a few of our projects
easily have (many) more than 100 strings, which I understand is your
current cut-off point.
I can file appropriate bugs and am also willing to contribute code,
but I am sure I'll have a handful of questions along the way and could
use some guidance on finding my way around the code etc.
How does this sound?