Japanese localization of Hudson features use terms like "構築ジョブ" and "継続的構築", but these are literal translation
of the words that are hard to understand (see http://d.hatena.ne.jp/shin/20090509/p1 for a comment from another user,
I suggest the following changes:
構築ジョブ -> CIジョブ
継続的構築 -> 継続的インテグレーション or just "CI"
構築サーバー -> CIサーバ
I think we need to consider English labels too here.
It' not good idea to change just Japanese translations.
Actually it's hard to imagine Team->New Build Jobs... is
related with Hudson.
Create Build Job...
New Continuous Build
Jesse, any idea?
Actually it would be hard to understand English UI itself.
Users can not find the name of Hudson until they open the dialog
by Team > New Build Job... It looks "Build" and "Hudson" are
being used together. No word in "Continuous Integration" in UI,
I can see it just in module description.
I think just "Hudson" or "Continuous Integration" word should
be used consistently on UI instead of just "Build".
These English will be translated into several languages,
at least Japanese, Chinese and Brazilian Portuguese.
So it's not good idea to take such workaround in these
languages at translation process.
Could you evaluate please?
Changed the component back to hudson.
I'm just following the UI spec. No strong opinion on choice of terminology, though "Build Job" seems rather awkward.
Hudson itself uses "job" (or in a few cases "project") to represent what the menu item creates, whereas "build"
represents one numbered run of the job.
Can probably be considered a UI defect; not sure about priority.