Translation Instructions

Aegir CMS supports multiple languages and welcomes translations from the community. This guide will help you contribute translations for your language.

Current Translations

Aegir CMS is currently available in the following languages:

• English (default)
• Finnish
• German
• Dutch
• Danish
• Russian
• Swedish
• Polish

How to Contribute a Translation

Step 1: Get the Source Files

Download the latest translation template from CVS:

cvs -d :pserver:[email protected]:/var/lib/cvs login
cvs -d :pserver:[email protected]:/var/lib/cvs co nadmin/locale

Step 2: Create Your Language File

Translation files are located in the locale/ directory. Each language has its own subdirectory using the two-letter ISO 639-1 language code.

1. Create a new directory for your language (e.g., locale/es/ for Spanish)
2. Copy the English translation files as a starting point
3. Edit the files to translate all strings into your language

Step 3: Translation File Format

Aegir CMS uses PHP arrays for translations. Here's an example format:

<?php
$GLOBALS['translation']['en'] = array(
    'Login' => 'Login',
    'Username' => 'Username',
    'Password' => 'Password',
    // ... more translations
);
?>

Step 4: Test Your Translation

1. Copy your translation files to your Aegir CMS installation
2. Change the language setting in your Aegir CMS preferences
3. Verify that all strings appear correctly
4. Check for any untranslated strings or formatting issues

Step 5: Submit Your Translation

Once your translation is complete and tested, submit it to the project:

• Email your translation files to [email protected]
• Include information about the language and your contact details
• If possible, provide the files as a unified diff against the current CVS

Translation Guidelines

• Consistency: Use consistent terminology throughout the translation
• Context: Consider the context where text appears (buttons, menus, messages)
• Length: Keep translations roughly the same length as the original to avoid layout issues
• Formality: Follow the formality level appropriate for your language and culture
• Special Characters: Ensure proper encoding (UTF-8) for special characters
• Variables: Don't translate variable placeholders like %s, %d, etc.

Maintaining Translations

As Aegir CMS develops, new strings are added and some are modified. Translation maintainers should:

• Subscribe to the nadmin-cvs mailing list to track changes
• Update translations when new releases are prepared
• Respond to bug reports about translation issues

Tools and Resources

• Text Editor: Use a UTF-8 capable text editor
• Reference: Keep the English version open for reference
• Testing: Test in a working Aegir CMS installation
• Community: Ask questions on the mailing list

Recognition

All translators are credited in the Aegir CMS documentation and release notes. Your contribution helps make Aegir CMS accessible to users worldwide!

Questions?

If you have questions about translating Aegir CMS, please contact the development team via:

• Mailing list: [email protected]
• IRC: #aegir on irc.freenode.net