db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "LocalizingDerbyMessages" by RichardHillegas
Date Fri, 01 Aug 2008 15:17:29 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by RichardHillegas:

New page:
== Localizing Derby Messages ==

The English message sources live in the following locations:

|| '''English Message File''' || '''Description''' ||
|| java/engine/org/apache/derby/loc/messages.xml || Diagnostic messages from the core Derby
engine. ||
|| java/drda/org/apache/derby/loc/drda/messages_en.properties || Diagnostic messages from
the Network Server. ||

Localizations for other languages live in the same directories as the English versions. Supported
languages include:

|| '''Language''' || '''Localized Message Source''' ||
|| Czech || messages_cs.properties ||
|| German || messages_de_DE.properties ||
|| Spanish || messages_es.properties ||
|| French || messages_fr.properties ||
|| Hungarian || messages_hu.properties ||
|| Italian || messages_it.properties ||
|| Japanese || messages_ja_JP.properties ||
|| Korean || messages_ko_KR.properties ||
|| Polish || messages_pl.properties ||
|| Portuguese || messages_pt_BR.properties ||
|| Russian || messages_ru.properties ||
|| Chinese (traditional) || messages_zh_CN.properties ||
|| Chinese (simplified) || messages_zh_TW.properties ||

Typically, as the community develops a new feature release, more messages accumulate in the
English message sources. Those English versions need to be localized. Those localizations,
in turn, typically turn up in follow-on maintenance releases. Localizations are more up-to-date
for some languages than for others.

Typically, localizations for several languages are provided by committers who work for large
companies and who have access to their companies' translation teams. Although this translating
work happens outside the Derby community, committers checkin this contribution by proxy, under
section 4 of their [http://www.apache.org/licenses/icla.txt ICLA]s.

This process reflects the consensus of two discussions which took place on the [http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200807.mbox/browser
legal-discuss] mailing list:

 * Blanket software grant
 * Question about handling external updates to contributed files

and a discussion which took place on the [http://www.nabble.com/-DISCUSS--Process-for-contribution-of-translated-message-files-td18762388.html#a18762388
derby-dev list].

The following [http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200807.mbox/%3c40D37BFE-4104-493D-91ED-63E181441F3C@gbiv.com%3e
post] sums up the consensus:

"If you have permission from your company, you can contribute them under your own ICLA.  However,
it is better for your sake (not Apache's) that you have a signed CCLA in place that formally
says you have permission to commit stuff that is copyright the company.  Only one CCLA is
needed for all such commits."

View raw message