Hi Joe,
I see. This is not part of automated translation process. Let me see
what I can do.
thanks,
-michael
On 06/18/13 10:07, huizhe wang wrote:
Hi Michael,
The English came from Apache, a header was added there. So we'll need
to add the Apache header when we update (which we plan to do in the
next project).
The other language files were added by Oracle, reflecting the
internationalization effort by Oracle. I think those Oracle copyright
headers shouldn't have been removed.
Thanks,
Joe
On 6/18/2013 9:50 AM, Michael Fang wrote:
Hi Joe,
The translation team uses the English file as template and updated
the l10n files to match. So, in these cases, the corresponding
English resource files do not have these copyright headers, the l10n
files were updated accordingly. Is this a problem?
thanks,
-michael
On 06/17/13 23:41, huizhe wang wrote:
Hi Michael,
Thanks for translating the new messages.
I noticed that except XMLMessages, XMLSchemaMessages, and new
language resources for XPath, others are mostly removing the Oracle
copyright header. Should the header be removed? Other than the
original English source file, others were added by Oracle.
-Joe
On 6/17/2013 10:56 PM, Michael Fang wrote:
Hi Joe,
Please help to review the changes for the following CR:
http://bugs.sun.com/view_bug.do?bug_id=8016824
A list of English resource files are sent to translation group for
translation update periodically that's why these l10n resource
files have been updated.
You do not need to review the translation content at this time. We
just need to make sure they do not break the build (which has been
ensured with full test builds). Follow up i18n/l10n testing will be
performed in promotion builds and i18n/l10n bugs will be reported
and addressed.
The webrev is available here:
http://cr.openjdk.java.net/~mfang/8016824/
thanks,
-michael
