Tickets :: [#6221] UTF-8 in signatures.

6.0.0-alpha12

6/8/25

Summary	UTF-8 in signatures.
Queue	IMP
Queue Version	4.1.5
Type	Bug
State	Not A Bug
Priority	2. Medium
Owners
Requester	micha (at) kovoks (dot) nl
Created	02/06/2008 (6332 days ago)
Due
Updated	02/07/2008 (6331 days ago)
Assigned	02/06/2008 (6332 days ago)
Resolved	02/07/2008 (6331 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

02/07/2008 10:13:06 AM	Jan Schneider	State ⇒ Not A Bug

02/07/2008 09:36:11 AM	micha (at) kovoks (dot) nl	Comment #5	Reply to this comment
But what about the DB charset that you configured in Horde? Yay.... That was the missing link. So it is not a bug in the software, but a bug in my understanding how it works.. Thanks a lot.

02/06/2008 10:31:51 PM	Jan Schneider	Comment #4	Reply to this comment
But what about the DB charset that you configured in Horde?

02/06/2008 08:42:01 PM	micha (at) kovoks (dot) nl	Comment #3	Reply to this comment
Did you configure the database settings to use utf-8 for storage, and did you create the horde_prefs table with the utf-8 charset? The mysql server runs with a UTF-8 charset, the tables are created with UTF-8 charset and even the collation is utf8_unicode_ci

02/06/2008 06:43:24 PM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
Did you configure the database settings to use utf-8 for storage, and did you create the horde_prefs table with the utf-8 charset?

02/06/2008 03:53:48 PM	micha (at) kovoks (dot) nl	Comment #1 Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ UTF-8 in signatures. Queue ⇒ IMP State ⇒ Unconfirmed	Reply to this comment
Seems that it is impossible to use UTF-8 in signatures. It just doesn't got saved and even when submitted directly to the database with PhpMyAdmin it comes out as a lot of questionmarks. Example: Cнаилучшимипожеланиями/ Знайлепшымiпажаданнямi Translates to: C ?????????? ??????????? / ? ?????????i ??????????i