Bug 524529 - No translation can been observed
Summary: No translation can been observed
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-httpd
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Phil Knirsch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 525052
TreeView+ depends on / blocked
 
Reported: 2009-09-21 04:59 UTC by Noriko Mizumoto
Modified: 2015-03-05 01:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-02 13:15:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Noriko Mizumoto 2009-09-21 04:59:52 UTC
Issuing command "system-config-http" prints output in English. No strings translated in PO file can be found.
https://translate.fedoraproject.org/projects/system-config-httpd/tip/

Comment 1 Noriko Mizumoto 2009-09-23 05:16:33 UTC
This is feedback from Fedora 12 software translation review.

Version-Release number of selected component (if applicable):
Live for Fedora 12 Software Translation Review
http://people.redhat.com/petersen/f12-l10n/

- Po file doesn't match the command output 
Observed by it-IT and pt-BR

-  *** Buffer overflow detected ***: /usr/bin/python terminated 
Observed by zh-TW

Comment 2 Noriko Mizumoto 2009-09-29 02:55:42 UTC
(In reply to comment #0)
> Issuing command "system-config-http" prints output in English. No strings
> translated in PO file can be found.
> https://translate.fedoraproject.org/projects/system-config-httpd/tip/  

It should say 'issuing command system-config-httpd prints output in English. No strings translated in PO file can be found.

Comment 3 Phil Knirsch 2009-10-02 13:15:35 UTC
No it_IT po file exists in the translations, so that one is expected.
Just tried it with pt_BR.UTF-8 and that worked without problems.
Same with zh_TW.UTF-8, no failures here.

Comment 4 Piotr Drąg 2009-10-02 13:27:49 UTC
There should be no it_IT.po file. I'm sure Noriko meant the translation team, not a locale. However with new build this issue should be solved.


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