[Typo3-dev] forcing the (BE) encoding to UTF-8

["Kasper Skårhøj"]

I expect that TYPO3 will soon support UTF-8 like you describe. But I don't use the mb_* functions. For conversion between charsets I have created my own class. Also to support "windows-*" charsets and not only ISO-* sets.

God bless

- kasper

*********** REPLY SEPARATOR  ***********

On 25-08-2003 at 14:57 Martin Kutschker wrote:

>Hi!
>
>Currently it seems that the BE uses the encoding that's appropriate *) for
>the current language. Where does Typo3 get the informattion which encoding
>to use? I thought about tweaking the "database" to make all language
>entries contain UTF-8 as their value.
>
>I am not sure if this and using the PHP module Multi-Byte String Functions
>(mbstring) and it's setting mbstring.func_overload = 1 is enough to make
>Typo3 UTF-8 compliant. mbstring cobers only a small subset of the stanard
>String module. Though I think one could emulate some of them with pue PHP
>functions, requiring the app to be changed.
>
>Has anybody tried this approach? The idea is to have all data stored and
>delivered in UTF-8. This is fine for newer browsers and works ok with
>different languages.
>
>Regards,
>Masi
>
>*) AFAIK there are some languages with more than one encoding. 
>
>_______________________________________________
>Typo3-dev mailing list
>Typo3-dev at lists.netfielders.de
>http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev



God bless

- kasper


- kasper
-------------------- o ---------------------
>>>    In God I trust - others pay cash!     <<<
Check www.typo3.com