-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 19 December 2004 1:23 pm, Munzir Taha wrote:
On Yaum al-Ahad 07 Thu al-Qi`dah 1425 11:08 am, Mohamed Eldesoky
wrote:
> > Ghoneim, Desokey! If you can make some lines of code that demonstrate
> > it, it will be great! (Home Work ;))
>
> Shouldn't Mamboo use a default charcode ??
> if it unicode, then everything will be fine !!
Desokey, mambo use a default encoding, let's say it's unicode(utf-8). Like
any other utf-8 encoded page: if you go to View -> Set encoding ->
Arabic(cp 1256), the Arabic text would not render properly since utf-8 and
cp1256 have different code points for the Arabic characters. This is normal
and what I used to encounter. Now, our glossary page would render properly
however you try to mess it. Actually, you can't! Isn't this nice? The
question is how?
It uses HTML encoding, which is readable regardless of the encoding you
choose.
If you looked at it in the database it will look like
أخى يحيى
So now, it is not a good idea to store it that way. Normally, it is expected
that when the page loads in utf-8, the user wouldn't change the encoding from
the browser to cp-1256, or it would become an intentional call for
headache :)
- --
Mohamed Eldesoky
Systems Engineer
RedHat Certified Engineer
TE Data
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBxWwO2FHsOWMJBKMRAol+AJ9Hd2JYqHnSjctDB+t8e5qJNPTINwCePHfb
1k7OtWAHhV+aSj66l7bGycU=
=gPeA
-----END PGP SIGNATURE-----