Answers.Body: <p>Case statuses are user-defined option values (configurations). If you have installed CiviCRM initially in English, then switched the language, you will have to edit/translate the case statuses manually in: Administer > Case > Case statuses (/civicrm/admin/options/case_status?reset=1).</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-30T07:12:04.253Z
Answers.Text: Actually my problem isn't on Case statuses but most likely Activity statuses. So I did the same on Activity statuses and everything's good ! Thank's a lot bgm for taking the time to answer me !!
Answers.UserDisplayName: matthias de mauroy
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-29T16:06:34.693Z
Answers.LastActivityDate: 2015-04-29T16:06:34.693Z
Answers.UserDisplayName: bgm
Body: <p>Some translations are missing in non-english language (french in my case), because of the fact that localize's parameter is set to FALSE by default with no way to change it via configuration.</p>
  
  <p>So my question is why that ? And not the opposite ? And best of all why not when the language is not english set localize to TRUE.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-27T14:08:42.460Z
Comments.Text: I suspect it's because of old legacy reasons. Can you give an example of a form/page where the translation was missing?
Comments.UserDisplayName: bgm
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-28T08:10:38.127Z
Comments.Text: When you manage a client case, the url should be like "/civicrm/contact/view/case?action=view". The status isn't translated by default and when you click to select another value it is the same
Comments.UserDisplayName: matthias de mauroy
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-28T08:17:59.033Z
Comments.Text: The functions are called in CRM_Core_PseudoConstant line 221 and 1520 on civicrm 4.6.0
Comments.UserDisplayName: matthias de mauroy
Tags: <best-practice><localisation>
Title: Shouldn't CRM_Core_PseudoConstant::get localize parameter be setted to TRUE by default?
ThreadText: # Shouldn't CRM_Core_PseudoConstant::get localize parameter be setted to TRUE by default?
  
  (Asked by: username_0 on 2015-04-27)
  
  Some translations are missing in non-english language (french in my case), because of the fact that localize's parameter is set to FALSE by default with no way to change it via configuration.
  
  So my question is why that ? And not the opposite ? And best of all why not when the language is not english set localize to TRUE.
  
  **Tags:** best-practice, localisation
  
  > **Comments:**
  > **username_1**: I suspect it's because of old legacy reasons. Can you give an example of a form/page where the translation was missing?  
  > **username_0**: When you manage a client case, the url should be like "/civicrm/contact/view/case?action=view". The status isn't translated by default and when you click to select another value it is the same  
  > **username_0**: The functions are called in CRM_Core_PseudoConstant line 221 and 1520 on civicrm 4.6.0  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-04-29. Score: 2 | Accepted answer
  
  Case statuses are user-defined option values (configurations). If you have installed CiviCRM initially in English, then switched the language, you will have to edit/translate the case statuses manually in: Administer > Case > Case statuses (/civicrm/admin/options/case\_status?reset=1).
  
  > **Comments:**
  > **username_0**: Actually my problem isn't on Case statuses but most likely Activity statuses. So I did the same on Activity statuses and everything's good ! Thank's a lot username_1 for taking the time to answer me !!  
  
  ---
  
  