Bug 135339

Summary: tamil translation in application is not using UTF-8 encoding
Product: [Fedora] Fedora Reporter: Lawrence Lim <llim>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED RAWHIDE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: nobody+pnasrat, qa-i18n-list, sarahs, tools-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: anaconda-10.1.1.5-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-11-26 04:03:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 123268    
Attachments:
Description Flags
Please find attached the latest copy of the po file. none

Description Lawrence Lim 2004-10-12 03:37:02 UTC
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:

Comment 1 Lawrence Lim 2004-10-12 04:02:17 UTC
Created attachment 105034 [details]
Please find attached the latest copy of the po file. 

I have been advised that the po file has been updated in the anaconda CVS.

Comment 2 Jeremy Katz 2004-10-12 20:40:26 UTC
If it's in CVS, it'll get picked up in my next build (if it's not, it
needs to be put there :)

Comment 3 Lawrence Lim 2004-11-14 14:10:47 UTC
Sarah,
Could you please verify if the po with the correct encoding has been
committed to the CVS?

Thanks.

Comment 4 Lawrence Lim 2004-11-26 04:03:17 UTC
anaconda now display tamil characters properly, so the po must have
not updated. Closing this bug.

Thanks.