-- replying to this below -- From: Andrea Pescetti [mailto:[email protected]] Sent: Friday, December 26, 2014 15:44 To: [email protected] Subject: Re: Explaining Java (was RE: Java 32)
On 25/12/2014 Dennis E. Hamilton wrote: > 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. In "xx" we try to avoid too many subdirectories. The Java file could find a place in the "product" directory, and be referenced from the leftnav in that directory (extended a few hours ago). > 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.) "xx" is generated from the English content, so steps are: write English page; copy to xx (structure, i.e., filenames and directories, may change); translators add it. <orcmid> How about this? Create an ooo-site/trunk/content/java/ *folder* where the index.htm will be the new version of the target file. This can be done in advance because and, after the text is considered OK, internationalization could proceed without pressure in anticipation of 4.2.0. there is no link to it from anywhere yet. The folder is both to allow the very short URL, <http://openoffice.org/java> in messages, and the possibility that there might be further more- technical detail in order to keep the main page straightforward. We'll know better in trying it out. </orcmid> > 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. Correct. > How am I doing? Well, except one detail: as I wrote earlier today, we cannot do it for 4.1.2 since strings in Pootle have already been updated and translators are already working on 4.2.0; so at the moment we have no way to add a string between 4.1.1 and 4.1.2 (also, 4.1.2 is not meant for string changes). <orcmid> I missed the message about timing and 4.1.2 versus 4.2.0 somehow. So, we can we discuss changes to the messages and maybe make bugzilla issues but changes should not be made to the trunk until 4.1.2 is out the door? Whenever the messages are adjusted, they can refer to web pages that are already waiting, even if not linked from anywhere else up until then. It looks like the redirect from download/common/java.html could happen at any time it is considered that java/index.html is ready. </orcmid> I'm also curious about the new mechanism Jan described... well, very likely I'll know more about it at FOSDEM next month! Regards, Andrea. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
