6.0.0-beta1
7/26/25

[#1303] characters for browsing
Summary characters for browsing
Queue Turba
Queue Version 2.0
Type Bug
State Not A Bug
Priority 2. Medium
Owners Horde Developers (at)
Requester m.zdila (at) episoftware (dot) com
Created 02/03/2005 (7478 days ago)
Due
Updated 08/31/2005 (7269 days ago)
Assigned 08/10/2005 (7290 days ago)
Resolved 08/31/2005 (7269 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
08/31/2005 09:17:34 AM Jan Schneider Comment #10
State ⇒ Not A Bug
Reply to this comment
Closed until a proper solution was found.
08/10/2005 12:09:46 PM Jan Schneider Comment #9
State ⇒ Feedback
Reply to this comment
And when are you going to add the remaining of the currently 96000 
unicode characters? No, this won't work, period.



You could try to experiment with iconv and //TRANSLIT charsets, or the 
translit extension from PECL. That still doesn't solve the original 
issue, because you would transliterate all results before being able 
to select the correct entries for the character you selected. This 
would completely defeat the purpose of the pager.
08/08/2005 10:48:11 AM m (dot) zdila (at) episoftware (dot) com Comment #8
New Attachment: chars.php Download
Reply to this comment
hi



I've prepared character table with special characters substitution. 
Someone should be so kind to implement function to horde lib that 
removes diacritic characters from a string using this character table. 
Or give me a hints (considering various encodings, ...) how and I'll 
do it.



--

Martin Zdila
05/17/2005 05:36:33 AM sy1318 (at) yahoo (dot) com Comment #7 Reply to this comment
There is a problem like with Turkish Characters.



When I compose message that contains any Turkish characters like 
(ı, ç, ö,ğ) it display like  #&301; ... This is a good idea 
convert this symbols to this standards. But much of browser or e-mail 
application don't display this messages in HTML format. Most of e-mail 
application display this messages in Plain-text mode.



To setup character set to turkish-iso-8859-9 is not care...



I want to help you for solving this problem. I am a web developer. I 
use PHP+MySQL...
05/16/2005 07:49:06 PM Chuck Hagenbuch Comment #6 Reply to this comment
And do you have any suggestions on how to do that?
05/16/2005 06:38:37 PM m (dot) zdila (at) episoftware (dot) com Comment #5 Reply to this comment
It would be fine if existing characters include words beginning with 
non US-ASCII chars simillar to those US-ASCII, eg.:

R: R, Ř, Ŕ

O: O, Ó, Ô, Ö

S: S, Ś, Š, ß

...


05/16/2005 04:34:20 PM Jan Schneider Comment #4 Reply to this comment
"#"?
05/16/2005 04:31:11 PM Chuck Hagenbuch Comment #3 Reply to this comment
Any suggestions on what to include for this? * usually means all, 0-9 
still excludes some... ?
02/03/2005 04:43:23 PM Jan Schneider Assigned to Horde DevelopersHorde Developers
 
02/03/2005 04:43:06 PM Jan Schneider Comment #2
Type ⇒ Bug
State ⇒ Assigned
Priority ⇒ 2. Medium
Reply to this comment
I consider this a bug.
02/03/2005 02:42:20 PM m (dot) zdila (at) episoftware (dot) com Comment #1
Priority ⇒ 2. Medium
Type ⇒ Enhancement
Summary ⇒ characters for browsing
Queue ⇒ Turba
State ⇒ New
Reply to this comment
It is not possible to display names which start with non US character 
(e.g. Ž) because th the bottom in the browsing page there are only US 
A - Z characters.

Saved Queries