Alan Knowles wrote:
>
> The site we did with chinese and english used 2 seperate content tree's and
> totally different templates, It just crosslinked on the URL and check to see
> if a matching article existed in the second language.
>
> The problem we did find was that as chinese is a double byte language the
> &(content:h) - did a htmlentities rather than a htmlspecialchars() - I think -
> anyway it obliteratied the double byte code. ended up just doing a <? echo
> $content ?>....
Midgard 1.x does not support multi-byte encodings, sorry. The default
internal encoding for Midgard 2.0 probably (with very high level of
probability :-) will be one of Unicode's (UTF-8, UTF-16, UCS2, UCS4) and
there will be filters for conventional encodings (from/to Unicode, for
exchange with other apps).
--
Alexander Bokovoy
No use getting too involved in life -- you're only here for a limited
time.
--
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]
