[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Not a c-format in localized msgid

From: Joel E. Denny
Subject: Re: Not a c-format in localized msgid
Date: Wed, 24 Feb 2010 10:27:22 -0500 (EST)
User-agent: Alpine 1.00 (DEB 882 2007-12-20)

On Tue, 23 Feb 2010, Jorma Karvonen wrote:

> A bison 2.4.1b msgid bug:
> #: src/muscle_tab.c:422
> #, fuzzy, c-format
> msgid "previous definition"
> It is not any c-format. Because of wrong definition a "fuzzy" mark is 
> generated.

Thanks for the report.  However, I don't know how to fix this on our end. 
In the po/bison.po included in the bison-2.4.1b tarball, it doesn't say 

  #: src/muscle_tab.c:422
  #, c-format
  msgid "previous definition"
  msgstr ""

Moreover, section "8.3.6 Fuzzy Entries" in the gettext 0.17 manual says:

     Fuzzy entries, even if they account for translated entries for most
  other purposes, usually call for revision by the translator.  Those may
  be produced by applying the program `msgmerge' to update an older
  translated PO files according to a new PO template file, when this tool
  hypothesises that some new `msgid' has been modified only slightly out
  of an older one, and chooses to pair what it thinks to be the old
  translation for the new modified entry.  The slight alteration in the
  original string (the `msgid' string) should often be reflected in the
  translated string, and this requires the intervention of the
  translator.  For this reason, `msgmerge' might mark some entries as
  being fuzzy.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]