Description of problem: Some of the tamil strings in ta.po is using the wrong encoding (TSCII instead of UTF-8) Version-Release number of selected component (if applicable): How reproducible: everytime Steps to Reproduce: 1. Run application in LANG=ta_IN.UTF-8 Actual results: some strings are broken because of the encoding Expected results: should display all of the strings in UTF-8 Additional info:
Created attachment 105050 [details] Please find attached the latest copy of the po file.
Just wanted to follow up if you have any timeframe on rebuilding the package for RHEL4. It would be great to include the fixed tamil translation in because tamil is one of our official supported languages. Thanks!
Hi Lawrence and Leon. Did this bug never get addressed or did the bug just not get closed? Should i push out an erratum for RHEL4? Did these fixes make their way upstream?
Hi Ray, I converted the mo file for libbonoboui-2.0.mo from libbonoboui-2.8.0.99cvs20040929-2 to po and noticed that there are some string indeed were broken due to the encoding. This has been address in the po file from Comment #1.
Created attachment 112841 [details] the po file generated from the libbonoboui package in RHEL4
Hi Lawrence, Thanks for looking into this. I'll see what I can do about getting this pushed for U2.
I commited this for fc4 today. Hopefully it will make test3.
I think this should be moved to RHEL4U2CanFix. I believe that tamil is a RHEL-4 supported language, so we should ship as complete a translation as we can. This is a very low risk change, too--no functionality is going to break by replacing a po file. The only thing that could potentially happen is the tamil translation getting more broken, but that's not likely.
This package was never assigned a QA slot for RHEL4 U2: http://intranet.corp.redhat.com/ic/intranet/U2Packages.html QA capacity is already oversubscribed for RHEL4 U2. Moving forward from RHEL4U2CanFix to RHEL4U3Proposed.
The component this request has been filed against is not planned for inclusion in the next update. The decision is based on weighting the priority and number of requests for a component as well as the impact on the Red Hat Enterprise Linux user-base: other components are considered having higher priority and the number of changes we intend to include in update cycles is limited.
Product Management has reviewed and declined this request. You may appeal this decision by reopening this request.