[Tickets #6621] Re: Category handling
bugs at horde.org
bugs at horde.org
Thu Apr 24 19:23:51 UTC 2008
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/6621
-----------------------------------------------------------------------
Ticket | 6621
Updated By | Gunnar Wrobel <p at rdus.de>
Summary | Category handling
Queue | Kolab
Type | Bug
State | Resolved
Priority | 1. Low
Milestone |
Patch |
Owners | Gunnar Wrobel
-----------------------------------------------------------------------
Gunnar Wrobel <p at rdus.de> (2008-04-24 15:23) wrote:
> Hello Gunnar,
>
>> Rewriting the semicolon unconditionally to a comma seemed a little
>> bit too limited to me. If it is really desired to support the broken
>> notation we could probably do this depending on the product ID in the
>> XML text.
>>
>> Even if we would support the broken client notation I wonder if it
>> makes much sense to rewrite the category entry within Horde then.
>> Once the user connects with the broken client it would not understand
>> the new category information, right?
>
> Ok, that change is fine with me. I added the code to convert (old)
> broken data once the Horde client sees it. This would be useful if
> you restore old data from backups etc. Maybe I'll just leave it in my
> local copy, have to think about it a bit.
Yes, it makes sense if you know your user base and can judge what they are
doing. I just think that for the general case having one Kolab client
correcting data from another client might not be the best idea.
>
> btw: Speaking of broken data, I'm in contact with Niko Berger who
> develops the Thunderbird Kolab plugin, looks like he fixed parsing
> umlauts generated from Horde which are XML-entities instead of utf-8
> :-) Will test it soon.
Is that a Horde bug? I had some utf-8 problems in XML myself lately. Maybe
you can open another bug report or send a mail to kolab-dev.
Cheers,
Gunnar
>
> Thomas
>
More information about the bugs
mailing list