[Tickets #14199] Re: Decoding of base64 encoded Kolab (.xml) objects is broken

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/14199
------------------------------------------------------------------------------
  Ticket             | 14199
  Updated By         | Thomas Jarosch <thomas.jarosch at intra2net.com>
  Summary            | Decoding of base64 encoded Kolab (.xml) objects is
                     | broken
  Queue              | Kolab
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             | Thomas Jarosch
------------------------------------------------------------------------------


Thomas Jarosch <thomas.jarosch at intra2net.com> (2015-12-17 08:34) wrote:

> This sounds familiar, like something that was fixed previously -  
> though maybe the fix itself wasn't in the Kolab library.
>
> Thomas, do you remember this, or can you even reproduce it? With all  
> the torture testing we did recently, I'd be very surprised if this  
> somehow escaped our notice. I'm sure you have 8-bit characters in  
> your data ... :)

yes, even the automate test suite controlling the browser specifially  
uses umlauts in the Kolab data.

@Mike: Which IMAP backend are you using for Kolab? I've seen you sent  
a patch for the Pear backend in bug entry #14200.

The Horde Imap_Client backend is the only real maintained one, the  
others haven't been supported for years. In fact I don't see much  
point in keeping this extra maintenance burden in the future. IIRC  
Horde Imap_Client even outperforms the others...