Posted by Anonymous (not verified) on April 29, 2003 at 10:02am
In order to fully localize Drupal+contrib modules I have to translate nearly 900 strings. The problem is that in future versions or db reinstallations the whole translation is lost.
Any ideas how to create a translation db or file that will be kept separately and used by Drupal regardless of version / db changes?
Comments
Are you using the locale module?
I'm not sure I understand your question correctly, but I'll give it a try.
The locale module produces translations, and saves them in the locales table in the db.
Currently I have 860 strings in my Danish translation on fabulatoria.langemark.com.
This can be exported using PhpMyAdmin.
If you have access to PhpMyAdmin you can select the database you run drupal on, then select the locales table and then export by Going View dump (schema) of table. Here you mark "Structure and Data", "Add drop table", "Send" and "Complete inserts". This will enable you to save a complete copy of the table.
By marking the "Add drop table" you will be able to drop an existing table of same name - also in a newer installation if anything changed - before you install your data. Then if you run the update script on installation of new version - this update will change the table to the new format.
I apologize if you knew all of this allready.
Note that there is work underway to enable cross site sharing of translations by way of XML feeding! This cool feature will enable export and import of translation without any database work.
Gunnar Langemark
http://www.langemark.com
hmm..
no, I didn't know that sql technic. thanks for the info.
if some new strings in new version?
what will u do?
the most serious problem is how can u know what r new strings added in the new version!