Note to those creating language packs.

**sadek** · 2006-09-25, 02:49 AM

I have debugged a few issues with modules that were loaded via the module loader (specifically the Forums module) concurrently with a language pack, and all these issues ended up being caused by the same thing.

When defining language files, it seems that a lot of individuals are defining them as arrays, just like we have them defined in our application. For example, <sugarroot>/include/language/<your_lang>.lang.php, this is what it may look like.

Code:

  'moduleList' => array (
     'Home' => 'Accueil' ,
     'Dashboard' => 'Tableaux de bord' ,
     'Contacts' => 'Contacts' ,
     'Accounts' => 'Comptes' ,
     'Opportunities' => 'Affaires' ,
     'Cases' => 'Tickets' ,
     'Notes' => 'Notes' ,
     'Calls' => 'Appels' ,
     'Emails' => 'Emails' ,
     'Meetings' => 'Réunions' ,
     'Tasks' => 'Tâches' ,
     'Calendar' => 'Calendrier' ,
     'Leads' => 'Leads' ,
     'Quotes' => 'Devis' ,
     'Products' => 'Produits' ,
     'Reports' => 'Rapports' ,
     'Forecasts' => 'Prévisions' ,
      'ForecastSchedule'=>'Planification Prévision',
      'MergeRecords'=>'Fusionner Enregistrements',
     'Quotas' => 'Objectifs',
     'Teams' => 'Equipes' ,
     'Activities' => 'Activités' ,
     'Bugs' => 'Suivi Bugs' ,
     'Feeds' => 'Flux RSS' ,
     'iFrames' => 'Mon Portail' ,
     'TimePeriods' => 'Périodes' ,
     'Project' => 'Projets' ,
     'ProjectTask' => 'Tâches Projet' ,
     'Campaigns' => 'Campagnes' ,
     'Documents' => 'Documents' ,
     'Sync' => 'Sync' ,
     'ReportMaker' => 'SweetReports' ,
     'WorkFlow' => 'Work Flow' ,
     'Users' => 'Utilisateurs' ,
     'Releases' => 'Releases' ,
     'Prospects' => 'Prospects' ,
     'Queues' => 'Queues' ,
     'EmailMarketing' => 'Email Marketing' ,
     'EmailTemplates' => 'Email Modèles' ,
     'ProspectLists' => 'Listes des Prospects' ,
     'SavedSearch' => 'Recherches Sauvegardées',
     'Contracts' => 'Contrats'   ),

The problem with this is that it overrides the entire stock array, so if there are any additional array indexes, they are no longer a part of the array.

For example, when you load the Forums module, it adds the line below:

Code:

     'Forums' => 'Forums',

To avoid overriding this, and all the other custom array indexes, I'd suggest defining them as follows:

Code:

$app_list_strings['moduleList']['Home'] = 'Accueil';
$app_list_strings['moduleList']['Dashboard'] = 'Tableaux de bord';
$app_list_strings['moduleList']['Contacts'] = ''Contacts'';
...
...
$app_list_strings['moduleList']['Contracts'] = ''Contrats";

If anyone sees any reason why all arrays should not be defined as shown above, please feel free to let me know.

I've attached a script that will convert all array definitions from the first illustrated format to the second. Please place it in your webroot, access the script, type in the path to the language pack file, and execute!

Thanks,
-Sadek

**aserrano** · 2010-03-04, 10:01 PM

Hello Sadek,

I know I should have asked these questions before, but… better late than never:
1. Does sugar load en_us locale strings no matter which language is selected for the active locale?
2. If 1) is true, then, does your proposal allow for default en_us locale strings to be used like fallback strings for untranslated strings in the active locale?

Best regards,
Alberto.

**lobanw** · 2011-05-01, 03:27 AM

Just wanted to say thanks for your post because I am a new language pack developer and was running into the same issues as you were. Luckily there are true users that share information once they come across the problem! Thanks so much!