Jian Wang wrote:
> 
> As Alan and I mentioned in previous messages, for multi-byte character set,
> &(xxx); is not quite equal to <? echo xxx;>, which means Chinese is properly
> displayed using the later one but not with &(xxx);
It is OK since February, 2000, with 
MidgardParser russian
in HTTPD's config.
May be we will rename this option to 'MidgardParser raw' in the final version though
not sure.

> Also, using htmlentities(string) causes the international chars not properly
> stored and displayed, but using htmlspecialchars(string) is OK. see PHP
> document:
> http://www.php.net/manual/function.htmlentities.php for htmlentities:
> " Note, that this function currently only escapes ISO-8859-1 (or
> ISO-latin-1) charset.
> Currently, if you don't know what you are really doing, you should try to
> avoid to use this function.
> You *cannot* rely on that the input an user sends you from his browser is
> ISO-latin-1.
> ....
> So it is *not quite correct* to use this function as a superior replacement
> for
> things, where HTMLSpecialChars(); is enough, cause you assume, that every
> instance uses ISO-latin-1. "
For each language Asgard internal API requires defined asgard_localized_name()
function which should be provided by language backend. For Latin-1-based languages
asgard_localized_name() is {return htmlentities($name);}, for Russian and Chinese it
will be just {return $name;} IIRC.

-- 
Sincerely yours, Alexander Bokovoy 
  The Midgard Project   | www.midgard-project.org |    Aurora R&D team 
Minsk Linux Users Group |    www.minsk-lug.net    |  www.aurora-linux.com  
   IPLabs Linux Team    |     linux.iplabs.ru     | Architecte Open Source
-- He who fears the unknown may one day flee from his own backside.
                -- Sinbad

--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org

To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]

Reply via email to