Defect #10200

Unicode literals in wiki replaced by '?'

Added by Elmer de Looff almost 10 years ago. Updated almost 10 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Wiki
Target version:-
Resolution:Invalid Affected version:1.3.1

Description

When attempting to place a Unicode literal in the wiki, the preview looks fine, but after saving the page, the literal has been replaced by a single questionmark.

The odd thing is, it seems to go fine for "lower" Unicode characters, since greek literals (for instance: ยต (micro sign)) work fine. It's the ♥ (black heart suit) that's giving me a headache here.

Using HTML character entities is a suitable solution outside <code> blocks, but using Unicode literals inside these blocks is necessary, as HTML character entities get rendered differently (namely, you end up with &#x2665; and not ♥)

Redmine application environment:

Ruby version              1.8.7 (x86_64-linux)
RubyGems version          1.3.7
Rack version              1.1.3
Rails version             2.3.14
Active Record version     2.3.14
Active Resource version   2.3.14
Action Mailer version     2.3.14
Active Support version    2.3.14
Application root          /usr/share/redmine
Environment               production
Database adapter          mysql
Database schema version   20110902000000

History

#1 Updated by Etienne Massip almost 10 years ago

Are you sure that your database/tables/columns collations are well defined?

#2 Updated by Elmer de Looff almost 10 years ago

Etienne,

That is a good point, looking at those, they are all defined as latin_swedish_ci, which seems to explain a good bit. I'll be fixing that and if I still encounter the problem I will let you know.

It does seem wrong however that the character set for the database/tables is left to the default of the MySQL installation.

This particular Redmine installation is originally from the Debian Squeeze package tree (I seem to recall it was version 1.0.3), using HowTo_Install_Redmine_using_Debian_package. It has since been updated through repository updates to v1.1 and v1.3.

#3 Updated by Etienne Massip almost 10 years ago

  • Status changed from New to Closed
  • Resolution set to Invalid

Please reopen the issue if not solved.

Also available in: Atom PDF