bugGNU gettext - Bugs: bug #20707, gettext documentation only makes...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #20707: gettext documentation only makes two passing references to TRANSLATORS magic string

Submitter:  None
Submitted:  Tue 07 Aug 2007 12:23:31 AM UTC
   
 
Category:  Doc Severity:  3 - Normal
Item Group:  None Status:  Fix Released
Privacy:  Public Assigned to:  haible
Open/Closed:  Closed

Sun 01 Dec 2024 04:31:10 PM UTC, comment #4: 

The fix is contained in gettext 0.23.

Bruno Haible <haible>
Group administrator
Fri 04 Oct 2024 12:24:46 AM UTC, comment #3: 
Bruno Haible <haible>
Group administrator
Mon 04 Mar 2013 12:13:44 PM UTC, comment #2: 

I am almost sure It is not a magic string, It is a convention, because you have to pass "--add-comments=TRANSLATORS:" to xgettext in order to get them in the POT file (or only --add-comments).

I could get this bug report and patch the manual to clarify it if I am blessed by Bruno Haible, because already I have stealed him another bug report :)

Miguel Ángel Arruga Vivas <m1gu3l>
Group Member
Wed 05 Mar 2008 09:24:49 AM UTC, comment #1: 

Section "4.8 Letting Users Report Translation Bugs" in 0.17 seems to describe it pretty well (I didn't know about this and about --add-comments, but I understand it after reading that page).

Vaclav Slavik <vslavik>
Tue 07 Aug 2007 12:23:31 AM UTC, original submission:  

The gettext documentation does not properly mention the TRANSLATORS magic string that is used to give messages to translators.

Only two passing references are made but it is never properly explained.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by m1gu3l (Posted a comment)
  • -email is unavailable- added by haible (Updated the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2024-12-01 haible StatusFixed Fix Released
    2024-10-04 haible StatusConfirmed Fixed
        Open/ClosedOpen Closed
    2016-11-26 haible CategoryNone Doc
    2007-08-29 haible StatusNone Confirmed
    2007-08-29 haible Assigned toNone haible

    Back to the top

    Powered by Savane 3.14-f13d.
    Corresponding source code