Bug 432457 - [kn_IN] Translation Error in File
Summary: [kn_IN] Translation Error in File
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk2
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 432933
TreeView+ depends on / blocked
 
Reported: 2008-02-12 04:46 UTC by A S Alam
Modified: 2013-07-03 00:47 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-11 07:00:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description A S Alam 2008-02-12 04:46:21 UTC
Description of problem:
GTK's Translation is more than expected.
Error Message on Termianl 

"Gtk-WARNING **: Whoever translated default:LTR did so wrongly."

Version-Release number of selected component (if applicable):
gtk+-1.2.10-59.fc8.i386

How reproducible:
Everytime during runing GTK application (gedit, evince)

Steps to Reproduce:
1. run evince from Terminal for Language
2. check terminal
3.
  
Actual results:
error Message "Gtk-WARNING **: Whoever translated default:LTR did so wrongly."

Expected results:
should be clean Terminal
(Need to fix in translation)

Additional info:
http://l10n.gnome.org/POT/gtk+.gtk-2-12/gtk+.gtk-2-12.kn.po
Branches: gtk+2-12

Comment 1 A S Alam 2008-02-12 04:58:00 UTC
Please Make sure Commit also should be Trunk, it seems people don't commit to
trunk, which can revert back all fixed changes and Translation status is really
low for Trunk (<30%)

Comment 2 Ankit Patel 2008-02-12 04:59:33 UTC
Hi Shanky,

Can you please look into this bug?

Comment 3 Bug Zapper 2008-05-14 05:08:34 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Tony Fu 2008-09-10 03:09:09 UTC
requested by Jens Petersen (#27995)

Comment 5 Patrice Dumas 2008-10-01 22:20:21 UTC
Are you sure this is a gtk+ bug and not a gtk2 bug?

Comment 6 Shankar Prasad 2008-10-03 06:29:03 UTC
I have already corrected the error in the gtk+ and submitted to svn. I remember similar kind of error (gtk) was reported by Aman (I don't remember the exact bug no. and the module name) and I had corrected it.

Shanky

Comment 7 A S Alam 2008-12-11 06:59:42 UTC
yes, it was gtk2 only bug and it is fixed already.
Thanks

gtk2-2.21.12-1.fc9


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