On 25 December 2014 at 00:42, Dennis E. Hamilton <dennis.hamil...@acm.org> wrote:
> I finished checking on the Java-specific messages and the six messages > only have a single place where each is produced. > > It appears that a single (default en) page could provide the necessary > information for reference from any messages in the installed binaries. > > Andrea suggests > > The page could be included in the set of "standard pages" (the > "xx pages", see http://openoffice.apache.org/website-native.html > and then each translation team can decide whether to use the > English one or their translated one. > > A. Is this a potential way to do it? > > 1. Create an ooo-site/trunk/content/xx/java/ directory. > > 2. Create leftnav.mdtext and index.mdtext files there. > > 3. The content/xx/java/index.mdtext would become the English Language > version that > We adopt for the target. > > If further "breakout" is required, it can be handled in that directory at > a later time. > > B. Having done that, and having the message be agreeable, > internationalization can commence. > > C. At an appropriate time, the content/java/ directory is created and it > is arranged that this and content/xx/java/ are synchronized. (I have no > idea what order this has to be in and which is the master.) > > D. The current content/download/common/java.html can be redirected to > content/java/ > Or > > E. The adjusted default messages that link to the site will link to > http://openoffice.org/java and be in the build in time to test (4.1.2?) > developer builds with the new messages and the new site pages. > > > How am I doing? > Without being an expert, I can only say your suggestion looks pretty much like how I would have done it. Remark, Infra (==me) work on moving translations to a new service. This service will also offer webpage translation (through the same interface) so we can ask all our translators to translate relevant parts. We have to change every page slightly (add a special css and js) and the it just works. I hope to be able to present this at FOSDEM. rgds jan i. > > -----Original Message----- > From: Andrea Pescetti [mailto:pesce...@apache.org] > Sent: Monday, December 22, 2014 00:12 > To: dev@openoffice.apache.org > Subject: Re: Java 32 > > On 22/12/2014 Dennis E. Hamilton wrote: > > I am assuming that we can do the job with a single text. So I > > see no problem with where it is kept. > > One consideration might be the maintenance of the different-language > > versions and how browsers are routed to the correct one. > > The page could be included in the set of "standard pages" (the "xx > pages", see http://openoffice.apache.org/website-native.html and then > each translation team can decide whether to use the English one or their > translated one. > > Regards, > Andrea. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
