Bug 723249 - [RFE]: Review and fix gfs2-utils strings and formats
Summary: [RFE]: Review and fix gfs2-utils strings and formats
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: gfs2-utils
Version: rawhide
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Carlos Maiolino
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-19 14:19 UTC by Carlos Maiolino
Modified: 2012-05-09 17:38 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-09 17:38:13 UTC
Type: ---


Attachments (Terms of Use)

Description Carlos Maiolino 2011-07-19 14:19:54 UTC
review and rewrite (if needed), all the strings and their formats.

Some things to do:

- Replace strings by calls to glibc whenever is possible (e.g: using calls to perror)
- Fix different strings with the same meaning, to avoid lots of translatable strings into .pot file.

Comment 1 Steve Whitehouse 2012-01-06 13:10:59 UTC
Carlos, how is this going? Have you got as far as you can with it?

Comment 2 Carlos Maiolino 2012-01-10 12:28:46 UTC
Hi Steve.

IMHO, I believe gfs2-utils is already done to receive translations. 

The gfs2-utils automake system is creating the .pot file on the fly during the compilation time, so, we just need to remove the .pot file from the git source.

There are some other things we can do, removing and merging some macros, but my first attempts to do this, broken many other subsystems into gfs2-utils, some of them (like mount.gfs2 for example) will be removed soon, so, I believe we can do these another changes later, and ensure we will be removing some macros without break any other subsystem into the package, without the need to commit patches to legacy subsystems.

Comment 3 Steve Whitehouse 2012-05-09 12:03:51 UTC
If this is now done, can we close this bug?

Comment 4 Carlos Maiolino 2012-05-09 17:38:13 UTC
Hi,

it's done for now, closing.


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