Community « Discussion forum « Localization support board «
Some questions and some corrections.
Hi,
first some correction on the pot files:
skins.pot: about this site ; About this site (they are both needed ?)
root.pot: About this server (used as title of the page "about this site", may be it's possible to cancel one of them?)
control.pot "You must set a title to this section" "%d directories have been scanned" "The server has been switched on" are duplicated with an end dot.
codes.pot why to make advertising of www.cisco.com and www.nortel.com ?
user.pot Remote user (has been) authenticated by %s" there are both version.
overlays.pot Persons to be served become People to be served: %s
Now just a question:
Is it really necessary to have multiple po files? As i see around all the application are using one single file. With one file it is really simplier to mantain the traduction without the need to copy 30 headers every time you have to update pot files. And it is simpler to remain uniform in the translation of the various sentence. Another problem that could be afforded by having one file is about same sentence in different files with slitly different translation in some language that become a problem when you use a unique vocabulary (database of YACS translated senteces). If you have one files you have to reduce duplicate and to differentiate some similar sentence only if you really need both of them. And if you make some kind of caching as YACS does, you can build multiple cache files from one single original file no?
I hope that i've explained my mind as i've really to improve my english.
Bye and good work
first some correction on the pot files:
Now just a question:
Is it really necessary to have multiple po files? As i see around all the application are using one single file. With one file it is really simplier to mantain the traduction without the need to copy 30 headers every time you have to update pot files. And it is simpler to remain uniform in the translation of the various sentence. Another problem that could be afforded by having one file is about same sentence in different files with slitly different translation in some language that become a problem when you use a unique vocabulary (database of YACS translated senteces). If you have one files you have to reduce duplicate and to differentiate some similar sentence only if you really need both of them. And if you make some kind of caching as YACS does, you can build multiple cache files from one single original file no?
I hope that i've explained my mind as i've really to improve my english.
Bye and good work
Comments
| Bernard from nearby-an-airport Associate, 6934 posts | I have integrated your corrections in the code, so the next set of .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... |
| Fw_crocodile 151 posts |
Bernard: I think it would be better to wait to have a "complete" traduction before to push it on the YACS server. There are a lot of correction to do at this time, and if i'm the only one to work on it, a lot of water have to pass under the bridges before i could say the traduction is complete. But may be i'm a little bit to perfectionist. |
| Bernard from nearby-an-airport Associate, 6934 posts |
Fw_crocodile: Don't worry, we all have the same issue... The French translation of YACS has suffered during some weeks of the change to i18n, and still, we are fixing errors progressively. It is likely that pushing the Italian interface will help to locate most evident errors and then, over time, errors will decrease to areas used less frequently. You will not be blamed for remaining errors but, on the contrary, you have to be rewarded for the hard work achieved... |
