On 10 Sep 2010, at 13:33, Aparajita Fishman wrote:
Amen! And I would include running 4D in compatibility mode with that.
I can see some of your dilemmas now.
It would have been more consistent with the new plugin behavior to
make the default value for 'output charset' = UTF-8, but this would
probably have caused havoc in legacy sites.
The amount of thinking that has gone into this kind of stuff is very
much appreciated.
We've managed to get our site up and running in v11 with 4D running in
unicode mode, Active4D serving in legacy mode and not much
modification to the site static/template content. At the same time I'm
able to cross the 'UTF-8' bridge in a systematic and measured manner.
Great stuff !
Peter
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
