localedef man page on HP-UX

Man page or keyword search:  
man Server   10987 pages
apropos Keyword Search (all sections)
Output format
HP-UX logo
[printable version]

localedef(1M)							 localedef(1M)

       localedef - generate a locale environment

       compiler_options]     loader_options]	 method_file]	 charmap_file]
	      locale_definition] code_set_name] locale_name

       The command sets up the language environment for the named locale.  The
       command reads a file (see localedef(4) for a detailed description) from
       standard input (default) or  from  locale_definition  file,  creates  a
       locale file with the same name as specified for the locale_name parame‐
       ter, and optionally installs this locale in the appropriate  directory.
       Installation of public locales (those accessible to all users) requires
       appropriate privileges.	Creation of locales (both private and  public)
       requires access to the ANSI C compiler.

       The command recognizes the following options:

       Create permanent output even if warning messages have been generated.

       Generate 64-bit locale in addition to the 32-bit locale. This is the
		      default  on a 64-bit operating system (and hence on Ita‐
		      nium(R)-based systems) and is included  to  allow	 cross
		      platform development.

       (noinstall) Create the locale file in the current directory.

       (verbose) Generate as many diagnostic messages as possible.

       Generate	 additional  warning  messages	for  duplicate definitions and
		      use in the category.

       If	      file  contains  symbolic	names  (of  the	 form  )   use
		      charmap_file.   See  charmap(4) for a description of the
		      format of a charmap_file.

       Use	      locale_definition file as	 input,	 instead  of  standard
		      input (default).

       Use the specified
		      method_file  to overwrite use of default methods in pro‐
		      cessing the

       Specify the name of a codeset used as the target mapping of character
		      symbols and collating  element  symbols  whose  encoding
		      values  are  defined  in	terms  of the Unicode (ISO/IEC
		      10646-1:2000) scalar values.

       Specify additional compiler options to  be  applied  in	compiling  the
		      See  cc_bundled(1)  for  a complete list of options. Use
		      with care on a 64-bit operating system since  the	 addi‐
		      tional  default  option  includes +DA2.0W on PA-RISC and
		      +DD64 on Itanium-based systems.

       Specify additional loader options to be applied in linking the locale.
		      See ld(1) for a complete list of options.

       locale_name    This argument is required, and identifies	 the  name  of
		      the  language  following	the  naming  convention of the
		      environment variable (see environ(5)):


       The following is a brief description of the components that make	 up  a
       locale.	 For  a complete description of the form and syntax of a file,
       see localedef(4).  For a complete description of the form  and  effects
       of a charmap file, see charmap(4).

       Six categories of data in the file are recognized by and make up a lan‐
       guage definition:

	      Information in this category affects behavior
				  of regular-expressions and NLS string-colla‐
				  tion functions.

	      Information in this category affects behavior
				  of  character	 classification and conversion

	      Information in this category affects behavior
				  of functions that handle monetary values.

	      Information in this category affects handling of the radix char‐
				  in formatted-input/output and string-conver‐
				  sion functions.

	      Information in this category affects behavior
				  of time-conversion functions.

	      This category contains information
				  affecting    interpretation	 of	yes/no

       A file also consists of six categories.	The beginning of each category
       is identified by a having the form where category is one of the follow‐
       ing:  or	 The end of each category is identified by a tag consisting of
       the word followed by a space and the category identifier; for  example,
       Categories  can appear in any order in the file.	 At least one category
       specifications is required.  If a category is not  specified,  sets  up
       the  default  "C"  locale  for  that  category  (see  setlocale(3C) and

       Each category is composed of one or more	 statements.   Each  statement
       begins  with a keyword followed by one or more expressions.  An expres‐
       sion is a set of well-formed metacharacters,  strings,  and  constants.
       The command also recognizes comments and separators.

       More than one definition specified for each category constitutes a hard
       error (causes the command to exit without generating  a	locale).   Any
       category	 can  be  specified  by	 the keyword followed by the name of a
       valid locale.  This causes the information for the category to be iden‐
       tical  to that in the named locale.  Note that the keyword, if used for
       a category, must be the first and only keyword following	 the  category

       A  methods  file	 is used to create locales for user-specific character
       encoding schemes.

   Operating System Requirements
       For cross platform development and development on  a  64-bit  operating
       system  several	requirements  must  be	observed.  Both the 32-bit and
       64-bit method libraries must exist. In the case of  the	64-bit	shared
       library	it  must  be in the directory ( or in case of PA-RISC systems)
       under the location where the 32-bit library is located. When the option
       is  specified,  or  when	 executing  on	a 64-bit operating system, the
       resulting locale is placed in the directory in case of PA-RISC systems)
       under  the current working directory unless the install option has been

       A locale built for one system cannot be used on other systems.

       Users will not be able to generate PA-RISC locales on systems.

       When the option is used, the code_set_name option  argument  is	inter‐
       preted  as  a name of a codeset to which the ISO/IEC 10646-1:2000 stan‐
       dard position constant values (Unicode scalar  values)  are  converted.
       Both  the  Unicode scalar values (via the "\u" character constants) and
       other formats (decimal, hexadecimal, or octal) are  valid  as  encoding
       values within the charmap file.	The codeset can be any codeset that is
       supported by the function on the system.

       When conflicts occur between the charmap specification of  or  and  the
       corresponding  value for the codeset represented by the option argument
       code_set_name, the command fails with an error.

       If the keywords and are not specified in the locale source, the	values
       of  the	keywords and will be used respectively for formatting monetary
       quantities with international currency symbols.

   Environment Variables
       determines the locale to use when neither or the other  category	 vari‐
       ables specify a locale.

       determines  locale to be used.  It overrides any values specified by or
       any other variables.

       and have no effect on the processing of the  localedef  command,	 which
       behaves as if these two variables were set to the C locale.

       determines the language in which messages are displayed.

   International Code Set Support
       Single and multi-byte character codesets are supported.

       The command returns the following values:

	      No errors occurred and the locale was successfully created.
	      Warnings occurred and the locale was successfully created.
	      The locale specification exceeded implementation limits or the
		    coded character set used is not supported.
	      Warnings or errors occurred, and no output was generated.

       The command was developed by OSF and HP.

       In  addition  to	 the PA-RISC files, the following files are present on
       Itanium-based systems.

       locale(1), setlocale(3C), charmap(4), localedef(4), environ(5).


List of man pages available for HP-UX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
Vote for polarhome
Free Shell Accounts :: the biggest list on the net