|
History
| Log In
|
|
|
|
Hi Mathieu,
I'm not a developer and didn't understand lot of code. I saw your last files and wondered about two points: 1. I understood there is a new import process for importing language files directly from TinyCME cvs system in the language system of Moodle. They are added to the moodle language system but overwritten by an external process. It will be confusing - only for translators- if they change the strings in the main version of their language and upload it to moodle, because the changes are overwritten by automatic import from Tinycme. If lnaguage files are in lang/mylanguage/ folder translators will try to translate them. But if there is an automatic process to update from external source it will be confusing. Most translator not only tranlate missing strings but also try to optimize language strings 2. Are the paths correct here in create_langfiles.php? // this should be the path to a checkout of the translations tree // the english file will need to be separately committed to all // relevant cvs checkouts (2.0 and up) -define('MOODLE_LANG_PATH', '/home/mathieu/workspace/moodle_langs'); +define('MOODLE_LANG_PATH', '/home/mathieu/workspace/lang'); // this should be the path to the unzipped tinymce langpacks define('LANGPACK_PATH', '/home/mathieu/workspace/tinymce_langs'); +// this should be the path to your HEAD checkout - the english translation +// will be saved there. +define('MOODLE_CVSHEAD_PATH', '/home/mathieu/workspace/head'); + I don't quite know how to answer question #1 ... Either translators have to redo all the translations (which is a waste for those that already exists), or the strings are imported from TinyMCE. When I import new strings, I don't quite know how (not speaking most of these languages) to decide which strings need to be replaced and which one need to be kept (I'm sure the TinyMCE translation team does "optimize strings" too). We need to be able to update the files, to upgrade when a new version comes out.. Any suggestion?
As for #2, they're right for me :) .. which is probably wrong for everybody else. But nobody has the same setup, and this script should only be used by the developer upgrading to a newer TinyMCE version. No idea what to put in there except for blatantly obviously wrong paths (like "/PATH/TO/YOUR/MOODLE/HEAD/REPO"). |
||||||||||||||||||||||||||||||||||||||||||||
 |
|
Sub-task
Closed
Major
I'm keeping this issue opened, as I still need to add some documentation on how to upgrade TinyMCE to include the patch that is necessary to fix this.