From: Alexander L. <li...@pl...> - 2002-11-20 08:40:27
|
On Tue, 19 Nov 2002 22:18:54 -0800, Andy McKay <an...@ag...> wrote: > Upon reading it further Im actually going to say lets hold horses our > here > for a second. This mostly covers installing i18n and I think we need to > do a > few things before this goes in the book but 1.0. Yes, amongst others the CVS step should be omitted. This is also probably better suited as an appendix than a chapter in itself. > What goes in the book should be "best practice" for installing i18n, is > this > Plone's best practice? If this is the best practice then it needs to be: > - a lot simpler > - the patches should be included > - in the Windows Installer This is correct, the installers should come with all the necessary steps taken, and i18n enabled out-of-the-box. The user shouldn't have to do anything, it should Just Work. The performance loss is negligible, the installers are not optimized for performance anyway, as this is mostly done by Apache/Squid caching etc. > I dont know much about i18n, so I'd rather someone in the know would tell > me... this is a great how to, but actually probably shouldn't be in the > book > as is. Agreed. I'll look into minimizing the steps, there's a lot we can do to make this easier. Thanks for the Howto, David - great job. We also need to figure out whether UTF-8 is sufficient for our Japanese, Chinese and Korean friends. If anyone know more about this, please respond to this message. -- Alexander Limi http://limi.net |