Answers.Body: <p>Thanks. Please open an issue on <a href="http://issues.civicrm.org/" rel="nofollow">http://issues.civicrm.org/</a>
  There you can also add a diff file to an issue.</p>
  
  <p>If you're really hardcore you can fork <a href="https://github.com/civicrm/civicrm-core" rel="nofollow">https://github.com/civicrm/civicrm-core</a>, add your changes to the git project and do a pull request.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-27T17:59:48.047Z
Answers.LastActivityDate: 2016-01-27T17:59:48.047Z
Answers.UserDisplayName: Catorghans
Body: <p>I'm localizing (Italian) some parts of CiviCRM, but I noticed how some terms are not sensible to be translated.
  I had a look on the code and I found that these terms are written without the ts() call.</p>
  
  <p>I correct the code, using ts() function, and the problem was solved.</p>
  
  <p>Now I have a little list of these bugs, and my question is: what is the procedure to signal them to the community?</p>
  
  <p>Thanks</p>
  
Tags: <issues><localisation>
Title: Bugs in localization
ThreadText: # Bugs in localization
  
  (Asked by: username_0 on 2016-01-27)
  
  I'm localizing (Italian) some parts of CiviCRM, but I noticed how some terms are not sensible to be translated.
  I had a look on the code and I found that these terms are written without the ts() call.
  
  I correct the code, using ts() function, and the problem was solved.
  
  Now I have a little list of these bugs, and my question is: what is the procedure to signal them to the community?
  
  Thanks
  
  **Tags:** issues, localisation
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-01-27. Score: 3
  
  Thanks. Please open an issue on <http://issues.civicrm.org/>
  There you can also add a diff file to an issue.
  
  If you're really hardcore you can fork <https://github.com/civicrm/civicrm-core>, add your changes to the git project and do a pull request.
  
  
  ---
  
  