Answers.Body: <p>Although not an ideal solution, if we add the following line in the .htaccess the reports are printed well.</p>
  
  <pre><code>AddDefaultCharset utf-8
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-12-31T17:23:12.477Z
Answers.LastActivityDate: 2015-12-31T17:23:12.477Z
Answers.UserDisplayName: Francesc Bassas i Bullich
Answers.Body: <p>This is probably caused by the settings for your database? We had the same problem with Norwegian special characters because their CiviCRM database was set to Latin-1. It has to be UTF-8 general-ci for CiviCRM. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-08T12:11:23.320Z
Answers.Text: Not in our case. All database tables are set to UTF-8.
Answers.UserDisplayName: Francesc Bassas i Bullich
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-08T13:54:20.173Z
Answers.Text: I know the special chars problem in 2 scenario's: the database one I mentioned and when importing or exporting with csv with the wrong encoding. You solution also suggests something somewhere with encoding:-)
Answers.UserDisplayName: ErikH - CiviCooP
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-08T13:55:54.393Z
Answers.Text: it might well be you default charset is not utf-8 as you have to change it?
Answers.UserDisplayName: ErikH - CiviCooP
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-03T10:12:19.873Z
Answers.LastActivityDate: 2016-01-03T10:12:19.873Z
Answers.UserDisplayName: ErikH - CiviCooP
Body: <p>We have instances of CiviCRM in Spanish and Catalan. When we try to print some reports the Spanish and Catalan specific characters (accents, 
  umlauts, etc.) are printed with a wrong charset. E.g. It prints <strong>RelaciÃ³</strong> instead of <strong>Relació</strong></p>
  
  <p>It is a bug or we're missing something?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-12-31T21:37:09.727Z
Comments.Text: It seems from your response that you are using Apache, but could you provide more information about the type of web server you are using? (version, operating system, etc). This should normally work by default. It could also be related to the theme of your CMS (drupal/wp/joomla?), that might be missing the "meta encoding" tag.
Comments.UserDisplayName: bgm
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-01-08T12:14:48.943Z
Comments.Text: We use:
      apache 2.2.22-13+deb7u6
      php 5.4.45-0+deb7u2
      mysql 5.5.46-0+deb7u1
  We run also
      drupal 7 over garland theme
      civicrm 4.6.8 over garland theme
Comments.UserDisplayName: Francesc Bassas i Bullich
Tags: <civireport><localisation><reports>
Title: How to print reports with non-English characters like accents?
ThreadText: # How to print reports with non-English characters like accents?
  
  (Asked by: username_0 on 2015-12-31)
  
  We have instances of CiviCRM in Spanish and Catalan. When we try to print some reports the Spanish and Catalan specific characters (accents,
  umlauts, etc.) are printed with a wrong charset. E.g. It prints **RelaciÃ³** instead of **Relació**
  
  It is a bug or we're missing something?
  
  **Tags:** civireport, localisation, reports
  
  > **Comments:**
  > **username_1**: It seems from your response that you are using Apache, but could you provide more information about the type of web server you are using? (version, operating system, etc). This should normally work by default. It could also be related to the theme of your CMS (drupal/wp/joomla?), that might be missing the "meta encoding" tag.  
  > **username_0**: We use:     apache 2.2.22-13+deb7u6     php 5.4.45-0+deb7u2     mysql 5.5.46-0+deb7u1 We run also     drupal 7 over garland theme     civicrm 4.6.8 over garland theme  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2015-12-31. Score: 3
  
  Although not an ideal solution, if we add the following line in the .htaccess the reports are printed well.
  AddDefaultCharset utf-8
  
  
  ---
  
  ### Answer by username_2 on 2016-01-03. Score: 3
  
  This is probably caused by the settings for your database? We had the same problem with Norwegian special characters because their CiviCRM database was set to Latin-1. It has to be UTF-8 general-ci for CiviCRM.
  
  > **Comments:**
  > **username_0**: Not in our case. All database tables are set to UTF-8.  
  > **username_2**: I know the special chars problem in 2 scenario's: the database one I mentioned and when importing or exporting with csv with the wrong encoding. You solution also suggests something somewhere with encoding:-)  
  > **username_2**: it might well be you default charset is not utf-8 as you have to change it?  
  
  ---
  
  