I was not refering to the html/xhtml/xml input. I was talking about the
charset parameter, for example. I don't want a chinese string passed as the
charset name (the libtidy API isn't localized yet :) ). The same applies for
the other functions.
Nuno
Are you sure want to generate a hard error if tidy_parse_string() doesn't
get an ASCII string?
-Andrei
On May 15, 2006, at 2:30 PM, Nuno Lopes wrote:
Looking only to the tidy extension:
tidy_parse_string
tidy_parse_file
tidy_repair_string
tidy_repair_file
tidy_getopt
tidy::__constructor
tidy::parseFile
tidy::parseString
I would say that others extensions will need too. Think in charset names,
options names, options values, etc..
Nuno
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
