6.0.0-beta1
9/24/25

[#3480] Input with special characters are dropped
Summary Input with special characters are dropped
Queue Horde Base
Queue Version 3.1-RC3
Type Bug
State Not A Bug
Priority 1. Low
Owners
Requester juliand (at) laneros (dot) com
Created 02/15/2006 (7161 days ago)
Due
Updated 03/10/2006 (7138 days ago)
Assigned 02/15/2006 (7161 days ago)
Resolved 03/10/2006 (7138 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
03/10/2006 09:37:35 AM Jan Schneider Comment #10
State ⇒ Not A Bug
Reply to this comment
Sorry, but we can't really help you then. It working for everybody 
else, so it doesn't seem to be a problem with Horde. If it's a 
configuration issue on your side and you are not able to fix it 
yourself, you might need to hire someone.
02/16/2006 06:14:07 PM juliand (at) laneros (dot) com Comment #9 Reply to this comment
Hi Jan, I'm sorry for not being able to understand a lot about 
programming and different charsets. I'm trying to do my best to figure 
out what's going on.



I  already told you the charsets sets on horde and the charsets for 
the mysql server. But I don't know what else to do in order to fix 
this...
02/16/2006 01:58:02 PM Jan Schneider Comment #8 Reply to this comment
Well, it's necessary to understand the different charsets if you want 
to debug this. And you have to debug this on your own, because it 
works for everybody else.
02/15/2006 04:37:08 PM juliand (at) laneros (dot) com Comment #7 Reply to this comment
According to phpMyAdmin, MySQL is working with the charset:  UTF-8 
Unicode (utf8). The collation of the tables in the horde database is 
'latin1_swedish_ci' but I really don't understand much about charsets 
and collations.
02/15/2006 03:39:16 PM Jan Schneider Comment #6 Reply to this comment
And are they stored in the correct charset, i.e. in the charset that 
your db server uses internally and that you configured in the database 
configuration of horde?

Or is it in the charset of the Horde interface, probably UTF-8?
02/15/2006 03:29:09 PM juliand (at) laneros (dot) com Comment #5 Reply to this comment
Oh yes... the value with special characters is actually stored on the 
database. I have configured a MySQL4.1 database. So, it seems like the 
problem is that horde isn't displaying the special characters but 
those values are actually stored on the database.
02/15/2006 03:02:35 PM Jan Schneider Comment #4 Reply to this comment
And is the information actually stored correctly in the preference 
backend (i suppose you configured the sql driver for preferences and 
use the default values there)?
02/15/2006 02:04:10 PM juliand (at) laneros (dot) com Comment #3 Reply to this comment
Hi Jan.



I'm sorry if I'm at the wrong configuration screen. The only section 
where I see a charset configuration is on the Database section.



Internally used charset: iso-8859-1



As far as I know i've always used that charset for my spanish sites. I 
don't know if I have to change another option somewhere else. I'm 
sorry about that :( If you can point me out to another location I can 
check that one for you.
02/15/2006 08:44:39 AM Jan Schneider Comment #2
State ⇒ Feedback
Priority ⇒ 1. Low
Reply to this comment
Did you specify the correct charset for your backend in the Preference 
System configuration?
02/15/2006 12:28:55 AM juliand (at) laneros (dot) com Comment #1
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Input with special characters are dropped
Queue ⇒ Horde Base
State ⇒ Unconfirmed
Reply to this comment
When I'm modyfing any field in the option page of horde or imp, and I 
enter a special character, for example 'ñ', it's dropped and the field 
is updated to an empty string.



Those characters are required for spanish people.



Thanks.

Saved Queries