Bug 133724 - specspo lacks arabic translation
Summary: specspo lacks arabic translation
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: specspo
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bernd Groh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: FC3Target FC4Target
TreeView+ depends on / blocked
 
Reported: 2004-09-26 20:36 UTC by Hicham AMAOUI
Modified: 2014-06-18 08:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-08-11 18:54:23 UTC


Attachments (Terms of Use)

Description Hicham AMAOUI 2004-09-26 20:36:13 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Gecko/20040808 Firefox/0.9.3

Description of problem:
although specspo is fully translated to arabic, the rpm
doesn't include the arabic translation.

Version-Release number of selected component (if applicable):
specspo-9.0.92-1.1

How reproducible:
Always

Steps to Reproduce:
1.choose an arabic locale
2.do a qurey on an rpm
3.rpm description is in english
    

Actual Results:  rpm description is in english

Expected Results:  should appear in arabic

Additional info:

Comment 1 Sherif Abdelgawad 2005-08-19 17:13:19 UTC
Hicham, Module: desc , CVS Path: specspo/desc is being worked on to add the
Arabic  translation. Current status is:

Total strings: 1845 	
Fuzzy: 752 	
Untranslated: 653

You may wish to give a hand and join the translation team, please check and
subscribe to the following mailing list if you wish to join:

https://listman.redhat.com/mailman/listinfo/fedora-trans-ar


Comment 2 Matthew Miller 2006-07-10 20:21:00 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!



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