Bug 479574 - xgettext does not know the language of anaconda (patch included)
Summary: xgettext does not know the language of anaconda (patch included)
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-11 16:06 UTC by Muayyad Alsadi
Modified: 2009-01-12 20:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-01-12 15:48:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
fix generating anaconda.pot (-p0 patch) (1.02 KB, patch)
2009-01-11 16:06 UTC, Muayyad Alsadi
no flags Details | Diff

Description Muayyad Alsadi 2009-01-11 16:06:55 UTC
Created attachment 328663 [details]
fix generating anaconda.pot (-p0 patch)

Description of problem:
xgettext does not know the language of anaconda because it has no extension 

Version-Release number of selected component (if applicable):
anaconda-11.4.1.63-1

How reproducible:
always

Steps to Reproduce:
1. cd po
2. make anaconda.pot
  
Actual results:
xgettext complains about unclosed quotes

Expected results:
no errors

Additional info:
patch is included

Comment 1 Chris Lumens 2009-01-12 15:48:19 UTC
Actually we now have to run xgettext twice - once for the python files and once for the C files.  It doesn't look like you can pass --lang=python <some files> --lang=c <other files>.  With that one modification, I'll apply this.  Thanks for the patch.

Comment 2 Muayyad Alsadi 2009-01-12 17:04:14 UTC
yes your changes are better

one last thing, the man/info page said it should be --language not the short --lang
I'm not sure if --lang is correct

Comment 3 Muayyad Alsadi 2009-01-12 20:32:59 UTC
I noticed a warning in the second xgettext saying it does not like charset=CHARSET so should we put

sed -i -e 's!^"Content-Type: text/plain; charset=CHARSET!"Content-Type: text/plain; charset=UTF-8!' $(NLSPACKAGE).po

between them ?


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