update_french_translation_from_crm_experts
Merge request reports
Activity
E.g. in Vtiger.php :
'LBL_MERGE' => 'Fusionner', 'LBL_MERGE_RECORDS_DESCRIPTION' => 'Le premier enregistrement sera conservé après la copie. Vous pouvez sélectionner la colonne pour laquelle conserver la valeur.<br />Les autres enregistrements seront supprimés mais l\'information liée sera fusionnée.', 'LBL_MERGE_RECORDS_IN' => 'Fusionner les enregistrements dans', 'LBL_MERGE_SELECT' => 'Sélectionnez les enregistrements (max: 3)', 'LBL_ACTION' => 'Action', 'LBL_FIELDS' => 'Champs', 'LBL_RECORD' => 'Enregistrement', 'LBL_SERVER_CONFIG' => 'Configuration du serveur', 'LBL_QUICK_CREATE' => 'Création rapide', 'LBL_DELETE_USER_PERMANENT_CONFIRMATION' => 'Supprimer définitivement cet utilisateur ?',
Here you go, full additions list. I'll update this request if I find new missing translations.
The LBL_YES additions are needed but it's in fact, a bug, as module should take it from Vtiger.php translation file.
-
Calendar.php
-
$languageStrings 'LBL_ADD_CALENDAR_VIEW' => 'Ajout de calendrier', 'LBL_YES' => 'Oui',
-
$jsLanguageStrings 'JS_NO_CALENDAR_VIEWS_TO_ADD' => 'Aucun calendrier utilisateur disponible', 'JS_RECORD_DELETED' => 'Suppression effectuée', 'LBL_YES' => 'Oui', 'LBL_NO' => 'Non',
-
-
Invoice.php
- $languageStrings 'LBL_SUB_PRODUCTS' => "Sous-produits",
-
Settings/CustomerPortal.php
- $languageStrings 'LBL_YES' => 'Oui',
-
Settings/ExtensionStore.php
- $jsLanguageStrings 'JS_LBL_ARE_YOU_SURE_YOU_WANT_TO_INSTALL_THIS_EXTENSION' => 'Etes-vous certain de vouloir installer cette extension ?',
-
SMSNotifier.php
- $languageStrings 'LBL_YES' => 'Oui',
-
Users.php
- $languageStrings 'LBL_YES' => 'Oui', 'LBL_NO' => 'Non', 'LBL_ALL_FIELDS_BELOW_ARE_REQUIRED' => 'Il est nécessaire de compléter les champs ci-dessous', 'LBL_ALMOST_THERE' => 'SELECTIONNEZ', 'LBL_Space' => 'Espace',
-
Vtiger.php
- $languageStrings
'LBL_MERGE' => 'Fusionner',
'LBL_MERGE_RECORDS_DESCRIPTION' => 'Le premier enregistrement sera conservé après la copie. Vous pouvez sélectionner la colonne pour laquelle conserver la valeur.
Les autres enregistrements seront supprimés mais l'information liée sera fusionnée.', 'LBL_MERGE_RECORDS_IN' => 'Fusionner les enregistrements dans', 'LBL_MERGE_SELECT' => 'Sélectionnez les enregistrements (max: 3)', 'LBL_ACTION' => 'Action', 'LBL_FIELDS' => 'Champs', 'LBL_RECORD' => 'Enregistrement', 'LBL_SERVER_CONFIG' => 'Configuration du serveur', 'LBL_QUICK_CREATE' => 'Création rapide', 'LBL_DELETE_USER_PERMANENT_CONFIRMATION' => 'Supprimer définitivement cet utilisateur ?',
- $languageStrings
'LBL_MERGE' => 'Fusionner',
'LBL_MERGE_RECORDS_DESCRIPTION' => 'Le premier enregistrement sera conservé après la copie. Vous pouvez sélectionner la colonne pour laquelle conserver la valeur.
-
It would slow people who doesn't understand english from installing vTiger. An alternative choice would be to allow people to choose packages from marketplace during installation.
vTiger install package would be lighter but it could be installed in french (or another language). That or either a languages choice during install so all unneeded languages packs would be deleted.
@guillaume.hilt As we are giving a access for a each user to change the language as they need ,its very necessary to retain all the language packs.
@manu.k I understand that users may update their french language pack via Marketplace but I don't get why you prefer to keep a bad/incomplete/incorrect one by default. In other words, why not providing the best french language pack as possible in order to offer the best vtiger user experience ?
@dubwise The Language pack which are available in the marketplace can be easily accessible to all versions. There is no need to wait for the language patches for all changes. Users can easily install and upgrade the language pack by using the marketplace and the language pack extensions which are submitted for the marketplace will be under go to complete review process. Before each main release we will pull those changes to the main branch.
@manu.k AFAIK, default embedded french language pack has not been updated for a very very (very) long time while CRM Expert (AB Online) french translation had been published on marketplace in december, 2014. So, I've never seen what you've talking about, the work from CRM Expert (AB Online) on french language pack have not been pulled to vTiger. Another problem I see : users have to wait for AB Online to update the language pack while community users may help maintaining/improving it. What is the use of Gitlab if we can't contribute to such simple thing as translation ?