RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 661575 - [ja_JP] Help page has a missing Japanese word
Summary: [ja_JP] Help page has a missing Japanese word
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: system-config-date-docs
Version: 6.0
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Nils Philippsen
QA Contact: QE Internationalization Bugs
URL:
Whiteboard:
: 889460 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-09 02:23 UTC by Kenichi Takemura
Modified: 2014-08-04 22:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-19 12:36:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screen shots (247.18 KB, application/vnd.oasis.opendocument.spreadsheet)
2010-12-09 02:24 UTC, Kenichi Takemura
no flags Details

Description Kenichi Takemura 2010-12-09 02:23:29 UTC
Description of problem:

Japanese message in a help page description is not appropriate. 

Version-Release number of selected component (if applicable):
system-config-date-docs-1.0.9-1.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Open a terminal and run $ LANG=ja_JP.UTF-8 system-config-date
2. Click 'ヘルプ(H)' on the left bottom of the manual page
3. 
  
Actual results:
The first description starts with 'に示されるように、', but '図 1' is missing.

Expected results:
The first description starts with '図 1に示されるように、' as shown in Fedora14 screen shot of the attachment.

Additional info:

Comment 1 Kenichi Takemura 2010-12-09 02:24:53 UTC
Created attachment 467635 [details]
Screen shots

Comment 3 RHEL Program Management 2011-07-06 00:20:36 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 4 A S Alam 2012-12-24 06:45:12 UTC
*** Bug 889460 has been marked as a duplicate of this bug. ***

Comment 5 Jaromír Končický 2014-03-19 12:36:28 UTC
In RHEL-6.3 and later versions, there is system-config-date-docs version 1.0.11. The help page has slightly changed, the "Figure 1" statement is no longer there.
So this request became pointless, thus closing.


Note You need to log in before you can comment on or make changes to this bug.