Reformatted excerpts from Fabio Riga's message of 2009-10-23: > Well, I finally read the code and I agree with Tero. I also think that > the use of gettext will be simpler for both developer and translator. > In this way, every time a developer add a new string he need to write > it twice, or another developer has to hack it. Instead with gettext > the developer write his string, surrounded with _() or n_() and he's > done (tell me, if I'm wrong).
Tero's comment wasn't about gettext, as far as I understand it. There are Ruby gettext bindings but they look like a pain in the ass to use, and it's pretty trivial to replace it a language like Ruby. > Furthermore people used to .po files (like me) will know what to do > and are already provided with tools for that purpose (i.e. Vim :-) ). That is a downside, definitely. > Can anyone explain me where and why a translated string in the UI should be > searchable with a regular expression? (Maybe this question is due to the > fact that I still don't understand sup internals...) I believe he was thinking about something like git grep. You see a weird message displayed by Sup, you want to find the code that's generating it, you can git grep the source for the message directly. -- William <wmorgan-...@masanjin.net> _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
