As far as what's returned by convert() in the case of codepoint errors, I thought that was explained in the usage sections, but I'll put some content into the error handling section as well (and link to the existing intl functions related to error surfacing,
As to determining how many invalid codepoints were encountered, no. There's not an API to surface that at ICU's level. I could add a counter to the callback and always enable it, even when not subclassing, but that's adding complexity where it in all likelihood won't be used for something which can be done in userspace, so I'm inclined against it. -Sara On Tue, Nov 6, 2012 at 12:48 AM, Lester Caine <les...@lsces.co.uk> wrote: > Sara Golemon wrote: >> >> There doesn't seem to be any further discussion. I figured if someone >> has more objections during the week this stays open for voting they >> can be addressed, and if need be the voting can be reset and resumed. > > > This may already be covered elsewhere, but is there a return from the class > that indicates easily the number of codepoint errors? > It would be helpful if the likes of the error handling single line linked > through to the relevant material? I've got back to the intl documentation, > but it's not clear there what is returned if a codepoint error is detected. > > -- > Lester Caine - G8HFL > ----------------------------- > Contact - http://lsces.co.uk/wiki/?page=contact > L.S.Caine Electronic Services - http://lsces.co.uk > EnquirySolve - http://enquirysolve.com/ > Model Engineers Digital Workshop - http://medw.co.uk > Rainbow Digital Media - http://rainbowdigitalmedia.co.uk > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
