[Bug manual/31029] New: A few paragraphs explaining 'catopen' actually belong in 'catgets'

[Bug manual/31029] New: A few paragraphs explaining 'catopen' actually belong in 'catgets'

[sebaaa1754 at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=31029

            Bug ID: 31029
           Summary: A few paragraphs explaining 'catopen' actually belong
                    in 'catgets'
           Product: glibc
           Version: 2.38
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: manual
          Assignee: unassigned at sourceware dot org
          Reporter: sebaaa1754 at gmail dot com
                CC: mtk.manpages at gmail dot com
  Target Milestone: ---

The following paragraphs in the body of the 'catopen' function seem to be
erroneously placed, as they actually refer to the following function,
'catgets'. Everything else in this document seems to be correct.

manual/message.texi lines 229 to 260:

> The return value of the function is in any case a valid string.  Either
> it is a translation from a message catalog or it is the same as the
> @var{string} parameter.  So a piece of code to decide whether a
> translation actually happened must look like this:
> 
> @smallexample
> @{
>   char *trans = catgets (desc, set, msg, input_string);
>   if (trans == input_string)
>     @{
>       /* Something went wrong.  */
>     @}
> @}
> @end smallexample
> 
> @noindent
> When an error occurs the global variable @code{errno} is set to
> 
> @table @var
> @item EBADF
> The catalog does not exist.
> @item ENOMSG
> The set/message tuple does not name an existing element in the
> message catalog.
> @end table
> 
> While it sometimes can be useful to test for errors programs normally
> will avoid any test.  If the translation is not available it is no big
> problem if the original, untranslated message is printed.  Either the
> user understands this as well or s/he will look for the reason why the
> messages are not translated.

Thanks!

-- 
You are receiving this mail because:
You are on the CC list for the bug.