[Tickets #7022] Re: Encode problem in full name

Top Page

Reply to this message
Author: bugs
Date:  
To: bugs
Subject: [Tickets #7022] Re: Encode problem in full name
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7022
------------------------------------------------------------------------------
  Ticket             | 7022
  Updated By         | voyager@???
  Summary            | Encode problem in full name
  Queue              | Horde Base
  Version            | 3.2.1
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------



voyager@??? (2008-07-07 07:55) wrote:

> So, are you saying the charset conversion works with any other
> non-ascii character? I have no idea how we could help you in this
> case, because we don't do the charset conversion ourselves, of course.


Yes, any other characters show fine. I see below in my first post that
this character display wrong. So, again by words it is 'n' with
caron(Unicode: 02C7) above. I don´t understand why this is do only
with this one character :(




-- 
You are subscribed to this list as: lurker@???
To unsubscribe, mail: bugs-unsubscribe@???