Hi Yannick,
I'm afraid the situation is not quite *that* simplistic. A few things
need to be put in a more accurate reference frame:
* As documented in length way back in October 2010
(https://docs.google.com/viewer?a=v&pid=explorer&chrome=true&srcid=0B8n8rrWLColvNzAzNTBiNjUtMzNmYS00MzM4LWJhOTMtN2U3M2NiMDJiYTgy&hl=en_US)
we introduced namespaces in Chamilo 2. This also implicated
changing the format of our translations-files from the classic
php-format to an ini-based format.
* The filesystem was restructured for uniformity and to allow for an
even more modular approach. The classic "languages"-folder
approach no longer applies to Chamilo 2. On top of that languages
are now based on ISO codes, instead of their English names. (Also
explained in the document)
* The number of modules / packages has significantly increased
and/or diversified. What's on the translation-website for 2.0 is
no longer up-to-date or in some cases no longer relevant.
* The platform is in dire need of an upgrade to the most recent
codebase. This has been postponed more then once because we were
hoping the association would have had it's own technical
infrastructure by now. Right now the people at Hogeschool Gent are
as kind as to let us host the application on their own servers. I
personally do not automatically also expect them to do any and
every kind of upgrade as well.
* Holidays? I'll assume this is an attempt at humour. Migrating a
platform of more then 20.000 users from Chamilo 1.8 to Chamilo 2
is not exactly what I would call a holiday. Setting up pilot
projects is not exactly what I would call a holiday. Preparing for
a new academic year is not exactly a holiday. Virtualizing and
restructuring a complete set of L(C)MS applications is not exactly
a holiday. The end of an academic year does not automatically mean
we all get to go on vacation. That being said each and every (2.0)
developer has more then earned a 2 month break (even when they're
not really getting it) after what they've realized this last year.
So that leaves me wondering who should do this? Fixing a few lines of
code is the easy part (if you know where and how). Migrating all the
data from the old installation to the new installation is somewhat more
complex. It takes intimate knowledge of Chamilo 2, the CDA-application
and the way translations are structured in 2.0 right now. I guess the
list of possible volunteers is rather short ... I'll have to ask the man
in the mirror how to proceed. I have to warn you though that he tends to
not take it too well when asking these kinds of things on a Sunday.
It's not too clear from your mail, but is the system broken for
importing in general or just for 2.0?
Best regards,
*Hans De Bisschop*
Adviseur | Lead Developer Chamilo 2.0
Software Coordinator Chamilo Association
Erasmushogeschool Brussel
Nijverheidskaai 170 | B-1070 Brussel
T 02 559 02 54 | i 254
hans.de.bissc...@ehb.be <mailto:hans.de.bissc...@ehb.be> |
www.erasmushogeschool.be <http://www.erasmushogeschool.be/>
Kom eens langs: www.erasmushogeschool.be/infodagen
<http://www.erasmushogeschool.be/infodagen>
of lees onze elektronische nieuwsbrief: ehbrief.ehb.be
<http://ehbrief.ehb.be/>
P Before printing, think about the environment
On 2/07/2011 21:26, Yannick Warnier wrote:
Hi all,
Given you're all more familiar than me with the C2 code... I'm trying to
use this wonderful import feature for translate.chamilo.org and while
importing a file it just doesn't work, which makes me panic as a lot of
us are using phpLangEditor to edit the files at home as I suggested, for
improved translation speed. We also have a full C1 and C2 Arabic
translation coming in this way apparently in a matter of 10 days or so,
so I'm really worried.
Here is my test case:
- go to translate.chamilo.org
- login
- click "Chamilo Translation Application" tab
- click "Export translations"
- select "Futura (2.x)"
- click "Next"
- click "English" and "French"
- click "Next"
- click "Core"
- click "Applications"
- Click "Download"
- Download the zip
- Uncompress the zip
- Edit the files with phpLangEditor
- Save
- zip the "translations" directory as a new "translations.zip" file
Up until there, everything is fine. I can see my ew translations are in
the file (I'm testing with the TrackingStorageUnitCreationFailed
variable inside the french/common.inc.php).
Then I go back to the "Chamilo Translation Application" tab.
- click on "Import translations"
- select "Futura (2.x)"
- upload the translations.zip file
- click "Import"
You then get to the languages screen, which kindly tells you the import
worked, so I search for the TrackingStorageUnitCreationFailed variable
in French, and... oh... the import didn't work!
Could someone *please* look into this? I know that the server is
somewhere where nobody we know has access, that the translation
application version is old and everything, but come on... this is not a
way to offer a translation mechanism to people who would like to
translate.
If I have to do it myself, it's going to be much quicker to re-install
the DLTT application, which I'm not OK to do.
And please, let it not be Hans, somebody else can take responsibility as
much as he can (now you're on holiday and there's much less stressing
support calls and all that).
Thanks,
Yannick
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
