Comment: Some questions and some corrections.
| Next >> |
I have integrated your corrections in the code, so the next set of
Your point is very valid, and it would make sense to have one single file of strings ... if YACS were not so rich in text! Currently about 5,600 strings are split over 31 templates. This saves a lot of processing time on each page, believe me! The drawback, for translators, is that a number of strings are repeated across modules.
Maybe we could find a way to better use the gettext technology, and achieve one single mega-catalog for translation, to be split in several templates afterwards? Have you looked at the
Thank you very much for your contribution, once again. I will push this to this server, to give you the pleasure to have an Italian interface...
.pot will look better.Your point is very valid, and it would make sense to have one single file of strings ... if YACS were not so rich in text! Currently about 5,600 strings are split over 31 templates. This saves a lot of processing time on each page, believe me! The drawback, for translators, is that a number of strings are repeated across modules.
Maybe we could find a way to better use the gettext technology, and achieve one single mega-catalog for translation, to be split in several templates afterwards? Have you looked at the
msgmerge utility to combine all .pot files into only one?Thank you very much for your contribution, once again. I will push this to this server, to give you the pleasure to have an Italian interface...
This comment has inspired:
by Bernard on Mar. 25 2007
