linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marko Myllynen <myllynen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] iconv.1: New page for iconv(1)
Date: Fri, 13 Jun 2014 12:15:02 +0300	[thread overview]
Message-ID: <539AC116.4050803@redhat.com> (raw)
In-Reply-To: <CAKgNAkgc4ASriZyv7bhjBJ-H17KYX0b4Pwb8175y++pCD1ZXbg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi,

On 2014-06-12 21:44, Michael Kerrisk (man-pages) wrote:
>>
>>> ENVIRONMENT
>>>        Internally, the iconv program uses the iconv(3) function  which
>>>        in   turn   uses   gconv  modules  (dynamically  loaded  shared
>>>        libraries) to convert to and  from  a  character  set.   Before
>>>        calling  iconv(3), the iconv program must first allocate a con‐
>>>        version descriptor using iconv_open(3).  The operation  of  the
>>>        latter  function is influenced by the setting of the GCONV_PATH
>>>        environment variable:
>>>
>>>        *  If GCONV_PATH is not set,  iconv_open(3)  loads  the  system
>>>           gconv  cache  file created by iconvconfig(8) and then, based
>>>           on the configuration, loads the gconv modules needed to per‐
>>>           form the conversion.
>>>
>>>        *  If GCONV_PATH is defined (as a colon-separated list of path‐
>>>           names), the system gconv module configuration cache  is  not
>>>           used.   Instead,  iconv_open(3) first tries to load the con‐
>>>           figuration files from one of the directories in  GCONV_PATH,
>>>           followed  by  the system configuration file.  If a directory
>>>           does not contain a  gconv  module  configuration  file,  any
>>>           gconv  modules that it may contain are ignored.  If a direc‐
>>>           tory contains a gconv module configuration file  and  it  is
>>>           determined  that  a  module  needed  for  this conversion is
>>>           available in the directory, then the needed module is loaded
>>>           from  that  directory,  the  order being such that the first
>>>           suitable module found in GCONV_PATH is  used.   This  allows
>>>           users to use custom modules and even replace system-provided
>>>           modules by providing such modules in GCONV_PATH directories.
>>>
>>>        iconv supports any character  set  for  which  a  corresponding
>>>        gconv configuration and module are provided.
>>>
>>> I have two doubts about the above text:
>>>
>>> * What is "the system configuration file"?
>>
>> It is listed in the FILES section, does that clarify enough?
> 
> I wondered about that. But the term "system configuration file" does
> not appear in FILES. Is it "Usual default gconv module configuration"?
> If so, that's not so obvious because the terms differ.

you're right, using "system default gconv module configuration" in both
places should make it obvious.

Thanks,

-- 
Marko Myllynen
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-06-13  9:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10  8:38 [PATCH] iconv.1: New page for iconv(1) Marko Myllynen
     [not found] ` <5396C41B.2040707-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-06-10 19:28   ` Michael Kerrisk (man-pages)
     [not found]     ` <53975C76.7060302-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-06-11  8:09       ` Marko Myllynen
     [not found]         ` <53980EC4.2030508-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-06-11 10:07           ` Michael Kerrisk (man-pages)
     [not found]             ` <53982A56.2000509-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-06-11 13:30               ` Marko Myllynen
     [not found]                 ` <539859E9.8040306-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-06-11 14:03                   ` Michael Kerrisk (man-pages)
     [not found]                     ` <CAKgNAkj=Y6P+C4SYegOejWJwGJQE96Jr6=Hej9PQFRiDXLzTDQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-11 14:14                       ` Marko Myllynen
     [not found]                         ` <53986452.2030308-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-06-11 19:15                           ` Michael Kerrisk (man-pages)
     [not found]                             ` <5398AAE7.3090307-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-06-12 17:40                               ` Marko Myllynen
     [not found]                                 ` <5399E60D.8010607-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-06-12 18:44                                   ` Michael Kerrisk (man-pages)
     [not found]                                     ` <CAKgNAkgc4ASriZyv7bhjBJ-H17KYX0b4Pwb8175y++pCD1ZXbg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-13  9:15                                       ` Marko Myllynen [this message]
     [not found]                                         ` <539AC116.4050803-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-06-13 11:45                                           ` Michael Kerrisk (man-pages)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=539AC116.4050803@redhat.com \
    --to=myllynen-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).