Bug 453511 - RHEL 4.7 release notes are not translated to ja-JP (Japanese) and pa-IN (Punjabi)
RHEL 4.7 release notes are not translated to ja-JP (Japanese) and pa-IN (Punj...
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: redhat-release (Show other bugs)
All Linux
high Severity high
: rc
: ---
Assigned To: Mike McLean
Content Services Development
: ZStream
Depends On:
  Show dependency treegraph
Reported: 2008-07-01 01:14 EDT by Don Domingo
Modified: 2008-07-24 16:24 EDT (History)
7 users (show)

See Also:
Fixed In Version: RHBA-2008-0624
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-07-24 16:24:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2008:0624 normal SHIPPED_LIVE redhat-release bug fix update 2008-07-24 16:24:08 EDT

  None (edit)
Description Don Domingo 2008-07-01 01:14:25 EDT
Description of problem:
RHEL4.7 release notes are currently not translated to Japanese (ja-JP) and
Punjabi (pa-IN). L10n did not have enough bandwidth for this task during the
translation cycle.
Comment 1 Michael Hideo 2008-07-01 01:23:43 EDT

How many hours will it take to translate the JP 4.7 release notes?


Comment 2 Manuel Ospina 2008-07-01 01:41:31 EDT

The statistics are:

total: 1988/75900 fuzzy words (2.62%),  69539/75900 translated words (91.62%)
total: 3.98 fuzzy hours, 17.49 untranslated hours, 21.47 remaining hours 

This is around 4 days including translation and proofreading. Please let me know
if you want me to put resources into this translation and delay one of the
translations for the JBoss project.
Comment 3 Michael Hideo 2008-07-01 19:45:50 EDT
Thanks, Manuel.

Yes, we need to have this translated as priority 1. I will inform Nakai san of
the change in the JP schedule for NTT.

Comment 4 Michael Hideo 2008-07-01 19:56:29 EDT
Hi Ludek,

We have 2 options here:

1. Wait for Translation to complete and respin package (eta would be Tues, July 8)
2. Day 0-errata
3. Web release of translation on GA (recommend)

- Mike
Comment 5 Mike McLean 2008-07-02 01:27:19 EDT
Please note that the release notes are also located in the top directory of the
install media. The installer can display them. Also some folks might browse the
disc contents. A day-0 errata will not help folks that browse the release notes
this way (though of course, neither will a web release).
Comment 6 Ludek Smid 2008-07-02 07:36:36 EDT
I would like to have package in today's Release Candidate compose.

As for JP translation -- we are going to re-spin RC compose due to some security
issue July 10. So, if you have translation ready at that date, we can include
updated package into compose. If not, I would pursue your recommended solution
(web release of translation on GA).
Comment 7 James Laska 2008-07-02 12:13:12 EDT
It either makes the RC deadline or misses, or we move the RC deadline for this
content.  The optional RC#2 milestone is intended for *critical* customer facing
issues uncovered after the RC.

I agree with Michael's recommendation in comment#4. 
> 3. Web release of translation on GA (recommend)
Comment 13 Don Domingo 2008-07-10 20:21:06 EDT
ja-JP RHEL4.7 release notes pushed to web staging:

they should be available in the public site within the next 24 hours or so.
Comment 23 errata-xmlrpc 2008-07-24 16:24:11 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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