The exact question is on : which is the best way to work for translators ?
* Whould you like to use both ( XML export / import and LinguaPlone translation interface ? ) * Which XML format is needed to be usefull for i18n team ? * It's ok webdav interface for editing it ? * Can we define the exact workflow to use on translations ? On this part we will probably need some new code to adapt and I would like to know how much work is needed to estimate how many help we will need. /Ramon En/na Quim Gil ha escrit: > The requirements are here: > > Multilingual CMS > http://mail.gnome.org/archives/marketing-list/2006-October/msg00112.html > > Also interesting: > > Re: CMS selected: Plone > http://mail.gnome.org/archives/marketing-list/2006-October/msg00142.html > > I know you have read these two emails so... what is exactly the > question? :) > > > On Mon, 2006-11-06 at 00:44 +0100, Ramon Navarro Bosch wrote: > >> hi ! >> >> i18n it's a really important part of this project, for that reason I >> would like to know what would you like to do : >> >> * we can use LinguaPlone translation system that generates translations >> for all the systems. It manages all translations and you can see >> original version while you are editing new translated version on the web. >> >> * we can use xml2po ?? how is the process to use it ?? as I understand >> it's a software that translate xml to po and after editing with your >> po-editor you transform again to xml. One great thing of Plone is that >> there is a webdav interface , so you can obtain the content by >> webdav/ftp and edit it using emacs ( or your preferit editor ) and >> automaticaly upload it after editing. >> > > _______________________________________________ gnome-web-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-web-list
