Re: How should PEAR packages support multiple character sets?

On Tue, Mar 25, 2008 at 10:07 PM, Christian Schmidt <lists@chsc.dk> wrote: > till wrote: > > I mean most email clients send UTF-8 today, most websites are UTF-8 (all > > browsers support it), most APIs expect it as well. > Yes, with the noticeable exception of PHP's string functions :-( Yeah, and it will all change in PHP6. :-) You can always use mb_* to replace (almost) all the regular str-calls. > > Non-UTF-8 charsets are really a pain to deal with. So why not just use > > this standard and document it like - "you will need to pass UTF-8 in". > So is this a vote in favor of solution 1? I vote for documentation. ;-) In your case, I'd also favour UTF-8 above anything else. But my favours aside, I'd accept what the API "demands". If that is ISO-8895-1, then so be it. Till