Bug 68708 - Format string errors in translation-strings
Summary: Format string errors in translation-strings
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: rpm   
(Show other bugs)
Version: 1.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2002-07-12 17:43 UTC by Enrico Scholz
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-07-12 17:44:22 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch against recent CVS version (3.23 KB, patch)
2002-07-12 17:44 UTC, Enrico Scholz
no flags Details | Diff

Description Enrico Scholz 2002-07-12 17:43:11 UTC
I will attach a patch fixing several format-string errors in the po/*.po files.

In ko.po I removed two messages because I do not know how to fix them; in pl.po
and is.po I added format-elements but because I do not speak these languages I
do not know if these are the correct places.

A lot of .po files are having incorrect headers which are failing to work with
recent rawhide-gettext. Does it make sense to send patches (which are just
adding correct charsets and *removing* default strings) or are the .po files
maintained at another place?

Comment 1 Enrico Scholz 2002-07-12 17:44:17 UTC
Created attachment 65165 [details]
Patch against recent CVS version

Comment 2 Jeff Johnson 2002-07-12 20:35:49 UTC
The po files for rpm are maintained at cvs.rpm.org.
SInce that's a different location than all other
Red Hat sources, the po files often are not made
available for translation through "normal"

In general, patches with PO files are tricky,
so significant changes should include the
entire file, not a patch.

Thanks for noticing and sending the patch
however :-) Should be in rpm-4.1-0.47 when

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