On 27/12/2014 Dennis E. Hamilton wrote:
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.
This would be OK. then java/index.html becomes, for translations,
xx/product/java.html ; we already do this for other files.
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?
Code and translations follow separate paths. The current trunk can be
freely modified and it will lead to, say, 4.2.0 (exact numbering still
undecided). For a bugfix release (like 4.1.2) we will have a separate
line based on "AOO410", the one that was used for 4.1.0 and 4.1.1. So
code is OK.
Translations, instead, currently have only one version available: in our
example, it can be set to trunk or to the 4.1.2 branch. And it is
currently aligned with trunk. So if we created (for code) a 4.1.2 branch
and you pushed the new English string to it, translators wouldn't find
it in Pootle and wouldn't be able to localize it.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
