From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marko Myllynen Subject: Re: [PATCH] iconv.1: New page for iconv(1) Date: Fri, 13 Jun 2014 12:15:02 +0300 Message-ID: <539AC116.4050803@redhat.com> References: <5396C41B.2040707@redhat.com> <53975C76.7060302@gmail.com> <53980EC4.2030508@redhat.com> <53982A56.2000509@gmail.com> <539859E9.8040306@redhat.com> <53986452.2030308@redhat.com> <5398AAE7.3090307@gmail.com> <5399E60D.8010607@redhat.com> Reply-To: myllynen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: Sender: linux-man-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org Cc: linux-man List-Id: linux-man@vger.kernel.org Hi, On 2014-06-12 21:44, Michael Kerrisk (man-pages) wrote: >> >>> ENVIRONMENT >>> Internally, the iconv program uses the iconv(3) function wh= ich >>> in turn uses gconv modules (dynamically loaded sha= red >>> libraries) to convert to and from a character set. Bef= ore >>> calling iconv(3), the iconv program must first allocate a c= on=E2=80=90 >>> version descriptor using iconv_open(3). The operation of = the >>> latter function is influenced by the setting of the GCONV_P= ATH >>> environment variable: >>> >>> * If GCONV_PATH is not set, iconv_open(3) loads the sys= tem >>> gconv cache file created by iconvconfig(8) and then, ba= sed >>> on the configuration, loads the gconv modules needed to p= er=E2=80=90 >>> form the conversion. >>> >>> * If GCONV_PATH is defined (as a colon-separated list of pa= th=E2=80=90 >>> names), the system gconv module configuration cache is = not >>> used. Instead, iconv_open(3) first tries to load the c= on=E2=80=90 >>> figuration files from one of the directories in GCONV_PA= TH, >>> followed by the system configuration file. If a direct= ory >>> does not contain a gconv module configuration file, = any >>> gconv modules that it may contain are ignored. If a dir= ec=E2=80=90 >>> 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 loa= ded >>> from that directory, the order being such that the fi= rst >>> suitable module found in GCONV_PATH is used. This all= ows >>> users to use custom modules and even replace system-provi= ded >>> modules by providing such modules in GCONV_PATH directori= es. >>> >>> iconv supports any character set for which a correspond= ing >>> 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? >=20 > 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, --=20 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