MODX Evolution 1.0 - Language files update progress

We’re working on one last pass through the installer and the manager today and tomorrow, then we’ll be ready for a lock-down on language-girations. Mostly it was about making the language more succinct and inline with what’s in Revo.

OK, time for an update on what has been done with the language files. Primarily, we’re going for concise descriptions where possible (that are hopefully easier to translate too). For example, the following hypothetical that’s not actually in the language translations:
[*] Here you can set the title of your site. → Set the website title.

We’re also transitioning to the terminology used in Revo, and note all proper MODx terms should be updated and capitalized including:
[*] resources → Elements (Snippets, Chunks, etc.)
[*] documents → Resources (as in Universal Resource Indicator / URI)
[*] resource browser → File Browser
[*] folder (on the MODx Site Tree) → Container
[*] folder (on the filesystem) → Directory
[*] tree → Site Tree

Note also that both the Manager and the Installer should support both RTL and LTR languages from the main theme. There should be no dedicated themes needed for RTL users.

Please run the language checking tool again on your language to see an left over or missing languages. If they’re not in your local language file the Manager will fall back to English. http://www.modx.wangba.fr/index.php?id=316

When cleaning up the English file I found it helpful to use bulk find and replace for the capitalization and corrections, and it actually should be relatively pain free to update your languages.

We should be releasing RC2 early next week, and final this month. Let’s get those Installer and Manager translations in tip-top shape. We promise not to touch them again without absolute necessity.

Hey,

Just a quick question, currently fixing the dutch translation to comply with the rc3 release,

But I see that the following RSS urls have been taken in the translation files:
$_lang["rss_url_news_default"] = ’http://feeds.feedburner.com/modx-announce’;
$_lang["rss_url_security_default"] = ’http://feeds.feedburner.com/modxsecurity’;

Are you gonna provide a translated feed version in the future or?
And I guess I don’t need to change this right now?

Grz,
Stefan

I’m thinking that for now it’s got to stay in English. If you have a native support site or use the MODx subforums, that offers translations of those feeds then it may make sense to use those.

Ok another thing I noticed when translating the $_lang["charset_message"] string,
you can no longer influence the manager character set the manager uses and it’s always utf-8 (atleast it is in the tests I did changing it).

Doesn’t that mean we can now drop the non utf8 manager translation files and thus only have to change / manager 1 file from now on?

Grz,
Stefan

Stefan, if that’s the direction you’d like to go then yes ... BUT for non-UTF8 databases, there may be some issues. Lots of people have Latin1 databases, etc. I’m no expert on this so ymmv, but the reality is everyone really should be on UTF8.

Alright folks, the countdown is on! Any language updates that will make it in time for Evo 1.0 need to be submitted over the next 72 hours or so. Please make the last updates and get them attached to this thread. Thanks!

Somebody might want to consider that in header.inc.php on line 98 there is a reference to $_lang[’ajax_loader’], which does not exist in the language files, so the loader popup is blank. In previous versions it was $lang[’loading_page’].

Quote from: sottwell at Jul 25, 2009, 11:34 AM

Somebody might want to consider that in header.inc.php on line 98 there is a reference to $_lang[’ajax_loader’], which does not exist in the language files, so the loader popup is blank. In previous versions it was $lang[’loading_page’].

No. $_lang[’ajax_loader’] must be $_style[’ajax_loader’]

Yes, that works. I suppose I should make a bug report on that.