Re: [commits] Horde branch master updated. 7fb00276bde050f0d815a9a4fcea4d55834defa7

Jan Schneider <[email protected]>
Newsgroups gmane.comp.horde.devel
Message-ID <[email protected]>
Zitat von Jan Schneider <[email protected]>:

> Zitat von Michael J Rubinsky <[email protected]>:
>
>> Quoting Jan Schneider <[email protected]>:
>>
>>
>>> -----------------------------------------------------------------------
>>>
>>> commit eddb3852c05c5ee3c1d565dd592cb0c185f81d43
>>> Author: Jan Schneider <[email protected]>
>>> Date:   Thu Apr 16 15:51:29 2015 +0200
>>>
>>>   Was this supposed to be used later?
>>>
>>>   At the moment, it's not. Do the other changes fix the charset  
>>> issue? Using the
>>>   Horde configuration is not a good solution anyway.
>>
>>
>> Yes, the change was stashed locally for some reason.
>>
>> If using the Horde config isn't a good solution, what's the  
>> alternative to getting the existing charset? For a new install, the  
>> charset config might be non-existent but that's why I default it to  
>> utf-8. Can this be obtained directly from the db adapter?
>
> Yes, via getConfig('charset'). But I wonder why the conversion is  
> necessary at all? I know, it was me who complained about incorrectly  
> converted resource names, but why does it require reading the  
> database adapter's charset?

Ah, nevermind, I see it now. You query the kronolith database directly  
(which returns the configured charset), but write to the share API  
(which uses the interface charset - utf-8).

-- 
Jan Schneider
The Horde Project
http://www.horde.org/
https://www.facebook.com/hordeproject

-- 
dev mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.