Created attachment 818893 [details] Notation of MB-KB-B Description of problem: if the usage is xx MB or KB shows in MB or KB. However, if the usage is 0, it shows 0 BYTE (バイト） Version-Release number of selected component (if applicable): 4.0 How reproducible: 100% Steps to Reproduce: 1.Click on Admin-System Panel-Resources Usage tab from the left side panel 2.In all the subtab, those MB/KB/BYTE is displayed 3. Actual results: MB/KB/0バイト Expected results: MB/KB/B Additional info:
Reported to the upstream ja-JP user group on 8 Nov and is currently under discussion.
In my opinion it would make more sense if they were all localised - e.g. in French Mb is Mo and this would need to be updated. However here, these values are actually already localised and translated. They come from the Django Japanese translations and choosing to translate it this way appears to be a choice from the Django Japanese community, see: https://github.com/django/django/blob/master/django/conf/locale/ja/LC_MESSAGES/django.po#L793 If we want this to change, we should see about submitting a patch to the Django project to make the translations more consistent. Coincidentally, Django also uses Transifex to manage their translations: https://docs.djangoproject.com/en/1.6/internals/contributing/localizing/#translations https://www.transifex.com/projects/p/django-core/
The final decision made by the upstream user group was to remove the unit for the value between 0-1023. This fix has been merged into the upstream Havana Stable Update. Moving the status to POST. @Julie With regard to your comment on Django, would you like me to ask Motoki-san whether we should make it consistent?
Yuko, Thank you for the update. Changing the target to async to reflect the translation update decision. I think it would be useful to discuss the Django translation status, though this should now be tracked separately.
(In reply to Julie Pichon from comment #5) > Yuko, > > Thank you for the update. Changing the target to async to reflect the > translation update decision. > > I think it would be useful to discuss the Django translation status, though > this should now be tracked separately. Hi Julie, Thank you for your comment. I shall discuss it and then file a separate bug, as you suggested.
Hi Julie, I found that the table which contains these values (and the units) in statistics is removed from Resource Usage tab. Motoki-san explained to me that the table will be removed for the Stable Update (2013.2.1) because it contained inaccurate information and misleading. When this change is applied, the bug to verify will not exist. Do you think I can close this bug now?
@Julie Additional note: - According to Motoki-san, the inconsistent notation for these units we reported is not caused by filters provided by Django, thus we do not need to bring this to the upstream discussion. - We fixed this in translation (but the page containing these values were removed as reported above). - Motoki-san filed this bug: https://bugs.launchpad.net/horizon/+bug/1261279
Thank you for the additional information and links! Since the bug is not valid anymore (cf. comment 7 - this was also backported to RHEL-OSP as part of bug 1038723) I will close it now.