You are not logged in. Please login or register.
Is it possible that in the future, localizations could be with .po/.mo files? That way, translations would be easier to update. I thought that if we're going to switch to po/mo, it should be done as soon as possible. If GetSimple grows fast (and it IS growing fast), translations could be painful to edit & update in the future.
What’s the advantage with .po or .mo files? I can’t say I’ve ever used them.
For starters, it's easier to update those files. Developers update the .pot file (main translation file) and the translator opens his/her xx_XX.po file and loads the .pot file and the new entries show up immediately. The way we use, the updates would be WAY harder.
Plus, there are software like poEdit which can edit translation files so easily that we don't even need to use a mouse :). It may seem unimportant but with my experience I can say that I can translate a .po file twice as fast as the .php file we work with currently.
And another thing, we can use functions in the core files. For example, if tr_TR.php does not have the line where $i18n['TOTAL_FILES'], there would be nothing in the place that phrase is used (upload.php). With po/mo stuff, you just write the function <?php __('total files'); ?> and if tr_TR.po does not have a "total files" entry, it shows "total files" so there's at least the English description in upload.php.
It's a little bit hard for me to explain it in English. The page below is a nice & small article about the advantages of this system:
http://www.gnu.org/software/trans-coord … tages.html
And other articles:
http://www.google.com.tr/search?q=GNU+gettext
Last edited by baris (2010-03-08 17:28:31)
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 9 official extensions. Copyright © 2003–2009 PunBB.