Red Hat Bugzilla – Bug 453511
RHEL 4.7 release notes are not translated to ja-JP (Japanese) and pa-IN (Punjabi)
Last modified: 2008-07-24 16:24:11 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
How many hours will it take to translate the JP 4.7 release notes?
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.
Yes, we need to have this translated as priority 1. I will inform Nakai san of
the change in the JP schedule for NTT.
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)
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).
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).
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)
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.
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.