|
From: Brian W. <bw...@st...> - 2002-10-17 23:53:51
|
At 08:29 18/10/2002, Geoff Hutchison wrote: > > Other side projects like defaults.xml are great, but this seems to be > > shaping up to be a much bigger task that originally envisioned, what > >No offense to Gabriele, but I'd rather consider translations to the >documentation _after_ we switch to an XML documentation setup. I've been thinking about this one - and the more I do, the more I agree. The problem isn't creating translated versions of the attributes - the problem is creating translated versions of everything else and managing how that all fits together. I think at some point the documentation needs to be reviewed and part of that should be internationalisation (i18n) - but it doesn't sound like that time is now. Also - bolting a translation system onto the current (:-)!) defaults.xml will take very little retrofitting and reworking so it doesn't need to be specially taken into account. I vote we do the first step and get a basic defaults.xml up - small steps! >Personally, I'd consider switching to defaults.xml for 3.2.0b4 if I can >see a patch in the near future. I'm willing to handle the documentation >fixes by hand if I need to do it. > >-Geoff ------------------------- Brian White Step Two Designs Pty Ltd Knowledge Management Consultancy, SGML & XML Phone: +612-93197901 Web: http://www.steptwo.com.au/ Email: bw...@st... Content Management Requirements Toolkit 112 CMS requirements, ready to cut-and-paste |