I didn't only want to ask this question in the developers area because I think all translators and programmers could have an idea to solve the following problem:
How can we add a check of changed language file message contents if an upgrade is done or later???
I had the problem to change the content of an english message from lang.en.php.
It was -> $pgv_lang["privacy_write_error"]
Later I saw that the message was included in some other language files. (da, it, sv)
As I didn't know how to translate the changes into those languages I just deleted that variable from those language files :-( in the hope that the translators will check the additions and translate this message again into their languages.
But I'm not so happy with this solution... Sorry to the translators...
Does anyone of you have a better idea how to solve such problems for the future???
First I thought to include it into the upgrade tool. This tool could rename ALL old language files of the user into "lang.en.php.oldversion" etc. and the language editor could check the real changes inside of the language files after the upgrade of ALL new language files from a release is done.
But I think the most important thing is the content of the english language files. Or better the checking of a change between the old english language files and the new one from the newest release. With that check the language editor could show the old english message, the new one and the content of message from the selected language. This would only need the english files (and not ALL lang files) on the server to be renamed to xxx.en.php.original while an upgrade is done.
But this solution would require that the users do use the upgrade function of PGV. It would be of any use if the user just downloads the new release and copies the files over the old ones.
But maybe only the translators would need to do this steps and we don't need to think about what a "normal" user of PGV does...
So please write if you have a better or different solution...
bye, Kurt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2004-01-02
My thoughts on this are as follows:
I do think we should include it in the upgrade tool as it is clearly part of an upgrade. What I can add to the upgrade tool is a comparison of the old english language file with the new english language file and show all the variables that have changed. This will be printed on screen but can also be put in a report of course :) for future reference.
How about that?
Regards,
Roland
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I didn't only want to ask this question in the developers area because I think all translators and programmers could have an idea to solve the following problem:
How can we add a check of changed language file message contents if an upgrade is done or later???
I had the problem to change the content of an english message from lang.en.php.
It was -> $pgv_lang["privacy_write_error"]
Later I saw that the message was included in some other language files. (da, it, sv)
As I didn't know how to translate the changes into those languages I just deleted that variable from those language files :-( in the hope that the translators will check the additions and translate this message again into their languages.
But I'm not so happy with this solution... Sorry to the translators...
Does anyone of you have a better idea how to solve such problems for the future???
First I thought to include it into the upgrade tool. This tool could rename ALL old language files of the user into "lang.en.php.oldversion" etc. and the language editor could check the real changes inside of the language files after the upgrade of ALL new language files from a release is done.
But I think the most important thing is the content of the english language files. Or better the checking of a change between the old english language files and the new one from the newest release. With that check the language editor could show the old english message, the new one and the content of message from the selected language. This would only need the english files (and not ALL lang files) on the server to be renamed to xxx.en.php.original while an upgrade is done.
But this solution would require that the users do use the upgrade function of PGV. It would be of any use if the user just downloads the new release and copies the files over the old ones.
But maybe only the translators would need to do this steps and we don't need to think about what a "normal" user of PGV does...
So please write if you have a better or different solution...
bye, Kurt
My thoughts on this are as follows:
I do think we should include it in the upgrade tool as it is clearly part of an upgrade. What I can add to the upgrade tool is a comparison of the old english language file with the new english language file and show all the variables that have changed. This will be printed on screen but can also be put in a report of course :) for future reference.
How about that?
Regards,
Roland