Bug #33316 Insufficient E-J translation on Service Adviser.
Submitted: 18 Dec 2007 5:27 Modified: 11 Feb 2008 16:58
Reporter: Mikiya Okuno Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Localization Severity:S3 (Non-critical)
Version:1.3.0.8528 OS:Any
Assigned to: Andy Bang CPU Architecture:Any

[18 Dec 2007 5:27] Mikiya Okuno 
Description:
"CPU I/O数が多すぎます" is not appropriate. The original sentence is "CPU I/O Usage Excessive". Please correct it as "I/Oに対するCPU使用率が高すぎます".

How to repeat:
See the adviser for "CPU I/O Usage Excessive" in Japanese.
[18 Dec 2007 5:41] MySQL Verification Team 
Advisor screen.

Attachment: Picture 3.png (image/png, text), 178.40 KiB.
[2 Jan 2008 23:03] Sloan Childers 
r8695 development-advisors
[2 Feb 2008 12:10] Toru Sugihara 
It is not fixed in 8891.
[6 Feb 2008 22:46] Andy Bang 
Toru,

Can you please check this again?  If the text is changed to "I/Oに対するCPU使用率が高すぎます", as requested at the top, then I think this bug is fully fixed.

If you marked it as "not fixed" after Sloan's checkin because you're still seeing "%server.0" in the text, that's OK.  The context of the screenshot attached to this bug report is of a generic rule, not a specific alert associated with a specific server.  In other words, if you click on a rule definition you will see %server.0 because at that point the rule doesn't know what server the problem might be associated with and that's a placeholder for the server's name.  The %server.0 should be gone and replaced by a server's name when you look at the same rule on the Events tab.
[10 Feb 2008 10:41] Toru Sugihara 
Then, I think it is OK. The advisor rule name is fixed.
[11 Feb 2008 16:58] Peter Lavin 
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.
Added to the changelog for version 1.3.