+2012-01-26 Bruno Haible <bruno@clisp.org>
+
+ Modernize quoting.
+ * NEWS: Quote 'like this', not `like this', as per the recent change
+ to the GNU coding standards.
+ * INSTALL: Process through sed -e "s/\`\([^']*\)'/‘\1’/g"
+
2011-10-18 Bruno Haible <bruno@clisp.org>
* m4/libtool.m4: Update from libtool-2.4.2, with modifications.
=============
This package depends on a few other packages. They are listed in
-the file `DEPENDENCIES'. It is recommended to install the listed
+the file ‘DEPENDENCIES’. It is recommended to install the listed
packages before installing this package.
Basic Installation
==================
- The `configure' shell script attempts to guess correct values for
+ The ‘configure’ shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
-those values to create a `Makefile' in each directory of the package.
-It may also create one or more `.h' files containing system-dependent
-definitions. Finally, it creates a shell script `config.status' that
+those values to create a ‘Makefile’ in each directory of the package.
+It may also create one or more ‘.h’ files containing system-dependent
+definitions. Finally, it creates a shell script ‘config.status’ that
you can run in the future to recreate the current configuration, a file
-`config.cache' that saves the results of its tests to speed up
-reconfiguring, and a file `config.log' containing compiler output
-(useful mainly for debugging `configure').
+‘config.cache’ that saves the results of its tests to speed up
+reconfiguring, and a file ‘config.log’ containing compiler output
+(useful mainly for debugging ‘configure’).
If you need to do unusual things to compile the package, please try
-to figure out how `configure' could check whether to do them, and mail
-diffs or instructions to the address given in the `README' so they can
-be considered for the next release. If at some point `config.cache'
+to figure out how ‘configure’ could check whether to do them, and mail
+diffs or instructions to the address given in the ‘README’ so they can
+be considered for the next release. If at some point ‘config.cache’
contains results you don't want to keep, you may remove or edit it.
- The file `configure.ac' is used to create `configure' by a program
-called `autoconf'. You only need `configure.ac' if you want to change
-it or regenerate `configure' using a newer version of `autoconf'.
+ The file ‘configure.ac’ is used to create ‘configure’ by a program
+called ‘autoconf’. You only need ‘configure.ac’ if you want to change
+it or regenerate ‘configure’ using a newer version of ‘autoconf’.
The simplest way to compile this package is:
- 1. `cd' to the directory containing the package's source code and type
- `./configure' to configure the package for your system. If you're
- using `csh' on an old version of System V, you might need to type
- `sh ./configure' instead to prevent `csh' from trying to execute
- `configure' itself.
+ 1. ‘cd’ to the directory containing the package's source code and type
+ ‘./configure’ to configure the package for your system. If you're
+ using ‘csh’ on an old version of System V, you might need to type
+ ‘sh ./configure’ instead to prevent ‘csh’ from trying to execute
+ ‘configure’ itself.
- Running `configure' takes awhile. While running, it prints some
+ Running ‘configure’ takes awhile. While running, it prints some
messages telling which features it is checking for.
- 2. Type `make' to compile the package.
+ 2. Type ‘make’ to compile the package.
- 3. Optionally, type `make check' to run any self-tests that come with
+ 3. Optionally, type ‘make check’ to run any self-tests that come with
the package.
- 4. Type `make install' to install the programs and any data files and
+ 4. Type ‘make install’ to install the programs and any data files and
documentation.
5. You can remove the program binaries and object files from the
- source code directory by typing `make clean'. To also remove the
- files that `configure' created (so you can compile the package for
- a different kind of computer), type `make distclean'. There is
- also a `make maintainer-clean' target, but that is intended mainly
+ source code directory by typing ‘make clean’. To also remove the
+ files that ‘configure’ created (so you can compile the package for
+ a different kind of computer), type ‘make distclean’. There is
+ also a ‘make maintainer-clean’ target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
=====================
Some systems require unusual options for compilation or linking that
-the `configure' script does not know about. You can give `configure'
+the ‘configure’ script does not know about. You can give ‘configure’
initial values for variables as arguments. You can do it like this:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
-own directory. To do this, you must use a version of `make' that
-supports the `VPATH' variable, such as GNU `make'. `cd' to the
+own directory. To do this, you must use a version of ‘make’ that
+supports the ‘VPATH’ variable, such as GNU ‘make’. ‘cd’ to the
directory where you want the object files and executables to go and run
-the `configure' script. `configure' automatically checks for the
-source code in the directory that `configure' is in and in `..'.
+the ‘configure’ script. ‘configure’ automatically checks for the
+source code in the directory that ‘configure’ is in and in ‘..’.
- If you have to use a `make' that does not supports the `VPATH'
+ If you have to use a ‘make’ that does not supports the ‘VPATH’
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
-one architecture, use `make distclean' before reconfiguring for another
+one architecture, use ‘make distclean’ before reconfiguring for another
architecture.
On MacOS X 10.5 and later systems, you can create libraries and
Installation Names
==================
- By default, `make install' will install the package's files in
-`/usr/local/bin', `/usr/local/man', etc. You can specify an
-installation prefix other than `/usr/local' by giving `configure' the
-option `--prefix=PATH'.
+ By default, ‘make install’ will install the package's files in
+‘/usr/local/bin’, ‘/usr/local/man’, etc. You can specify an
+installation prefix other than ‘/usr/local’ by giving ‘configure’ the
+option ‘--prefix=PATH’.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
-give `configure' the option `--exec-prefix=PATH', the package will use
+give ‘configure’ the option ‘--exec-prefix=PATH’, the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
In addition, if you use an unusual directory layout you can give
-options like `--bindir=PATH' to specify different values for particular
-kinds of files. Run `configure --help' for a list of the directories
+options like ‘--bindir=PATH’ to specify different values for particular
+kinds of files. Run ‘configure --help’ for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
-with an extra prefix or suffix on their names by giving `configure' the
-option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+with an extra prefix or suffix on their names by giving ‘configure’ the
+option ‘--program-prefix=PREFIX’ or ‘--program-suffix=SUFFIX’.
Enabling Relocatability
=======================
that packages are not relocatable. It means a user cannot copy a
program, installed by another user on the same machine, to his home
directory, and have it work correctly (including i18n). So many users
-need to go through `configure; make; make install' with all its
+need to go through ‘configure; make; make install’ with all its
dependencies, options, and hurdles.
Red Hat, Debian, and similar package systems solve the "ease of
-installation" problem, but they hardwire path names, usually to `/usr'
-or `/usr/local'. This means that users need root privileges to install
+installation" problem, but they hardwire path names, usually to ‘/usr’
+or ‘/usr/local’. This means that users need root privileges to install
a binary package, and prevents installing two different versions of the
same binary package.
to do the same thing with a hard link _only_ if the hard link file is
in the same directory as the real program.
- To configure a program to be relocatable, add `--enable-relocatable'
-to the `configure' command line.
+ To configure a program to be relocatable, add ‘--enable-relocatable’
+to the ‘configure’ command line.
On some OSes the executables remember the location of shared
libraries and prefer them over any other search path. Therefore, such
an executable will look for its shared libraries first in the original
installation directory and only then in the current installation
-directory. Thus, for reliability, it is best to also give a `--prefix'
+directory. Thus, for reliability, it is best to also give a ‘--prefix’
option pointing to a directory that does not exist now and which never
-will be created, e.g. `--prefix=/nonexistent'. You may use
-`DESTDIR=DEST-DIR' on the `make' command line to avoid installing into
+will be created, e.g. ‘--prefix=/nonexistent’. You may use
+‘DESTDIR=DEST-DIR’ on the ‘make’ command line to avoid installing into
that directory.
We do not recommend using a prefix writable by unprivileged users
-(e.g. `/tmp/inst$$') because such a directory can be recreated by an
+(e.g. ‘/tmp/inst$$’) because such a directory can be recreated by an
unprivileged user after the original directory has been removed. We
also do not recommend prefixes that might be behind an automounter
-(e.g. `$HOME/inst$$') because of the performance impact of directory
+(e.g. ‘$HOME/inst$$’) because of the performance impact of directory
searching.
Here's a sample installation run that takes into account all these
make
make install DESTDIR=/tmp/inst$$
- Installation with `--enable-relocatable' will not work for setuid or
+ Installation with ‘--enable-relocatable’ will not work for setuid or
setgid executables, because such executables search only system library
paths for security reasons. Also, installation with
-`--enable-relocatable' might not work on OpenBSD, when the package
+‘--enable-relocatable’ might not work on OpenBSD, when the package
contains shared libraries and libtool versions 1.5.xx are used.
The runtime penalty and size penalty are negligible on GNU/Linux
Optional Features
=================
- Some packages pay attention to `--enable-FEATURE' options to
-`configure', where FEATURE indicates an optional part of the package.
-They may also pay attention to `--with-PACKAGE' options, where PACKAGE
-is something like `gnu-as' or `x' (for the X Window System). The
-`README' should mention any `--enable-' and `--with-' options that the
+ Some packages pay attention to ‘--enable-FEATURE’ options to
+‘configure’, where FEATURE indicates an optional part of the package.
+They may also pay attention to ‘--with-PACKAGE’ options, where PACKAGE
+is something like ‘gnu-as’ or ‘x’ (for the X Window System). The
+‘README’ should mention any ‘--enable-’ and ‘--with-’ options that the
package recognizes.
- For packages that use the X Window System, `configure' can usually
+ For packages that use the X Window System, ‘configure’ can usually
find the X include and library files automatically, but if it doesn't,
-you can use the `configure' options `--x-includes=DIR' and
-`--x-libraries=DIR' to specify their locations.
+you can use the ‘configure’ options ‘--x-includes=DIR’ and
+‘--x-libraries=DIR’ to specify their locations.
For packages that use the GNU libiconv library, you can use the
-`configure' option `--with-libiconv-prefix' to specify the prefix you
+‘configure’ option ‘--with-libiconv-prefix’ to specify the prefix you
used while installing GNU libiconv. This option is not necessary if
that other prefix is the same as the one now specified through --prefix.
For packages that use the GNU libintl library, you can use the
-`configure' option `--with-libintl-prefix' to specify the prefix you
+‘configure’ option ‘--with-libintl-prefix’ to specify the prefix you
used while installing GNU gettext-runtime. This option is not necessary if
that other prefix is the same as the one now specified through --prefix.
and if that doesn't work, install pre-built binaries of GCC for HP-UX.
On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
-parse its `<wchar.h>' header file. The option `-nodtk' can be used as
+parse its ‘<wchar.h>’ header file. The option ‘-nodtk’ can be used as
a workaround. If GNU CC is not installed, it is therefore recommended
to try
Specifying the System Type
==========================
- There may be some features `configure' can not figure out
+ There may be some features ‘configure’ can not figure out
automatically, but needs to determine by the type of host the package
-will run on. Usually `configure' can figure that out, but if it prints
+will run on. Usually ‘configure’ can figure that out, but if it prints
a message saying it can not guess the host type, give it the
-`--host=TYPE' option. TYPE can either be a short name for the system
-type, such as `sun4', or a canonical name with three fields:
+‘--host=TYPE’ option. TYPE can either be a short name for the system
+type, such as ‘sun4’, or a canonical name with three fields:
CPU-COMPANY-SYSTEM
-See the file `config.sub' for the possible values of each field. If
-`config.sub' isn't included in this package, then this package doesn't
+See the file ‘config.sub’ for the possible values of each field. If
+‘config.sub’ isn't included in this package, then this package doesn't
need to know the host type.
If you are building compiler tools for cross-compiling, you can also
-use the `--target=TYPE' option to select the type of system they will
-produce code for and the `--build=TYPE' option to select the type of
+use the ‘--target=TYPE’ option to select the type of system they will
+produce code for and the ‘--build=TYPE’ option to select the type of
system on which you are compiling the package.
Sharing Defaults
================
- If you want to set default values for `configure' scripts to share,
-you can create a site shell script called `config.site' that gives
-default values for variables like `CC', `cache_file', and `prefix'.
-`configure' looks for `PREFIX/share/config.site' if it exists, then
-`PREFIX/etc/config.site' if it exists. Or, you can set the
-`CONFIG_SITE' environment variable to the location of the site script.
-A warning: not all `configure' scripts look for a site script.
+ If you want to set default values for ‘configure’ scripts to share,
+you can create a site shell script called ‘config.site’ that gives
+default values for variables like ‘CC’, ‘cache_file’, and ‘prefix’.
+‘configure’ looks for ‘PREFIX/share/config.site’ if it exists, then
+‘PREFIX/etc/config.site’ if it exists. Or, you can set the
+‘CONFIG_SITE’ environment variable to the location of the site script.
+A warning: not all ‘configure’ scripts look for a site script.
Operation Controls
==================
- `configure' recognizes the following options to control how it
+ ‘configure’ recognizes the following options to control how it
operates.
-`--cache-file=FILE'
+‘--cache-file=FILE’
Use and save the results of the tests in FILE instead of
- `./config.cache'. Set FILE to `/dev/null' to disable caching, for
- debugging `configure'.
+ ‘./config.cache’. Set FILE to ‘/dev/null’ to disable caching, for
+ debugging ‘configure’.
-`--help'
- Print a summary of the options to `configure', and exit.
+‘--help’
+ Print a summary of the options to ‘configure’, and exit.
-`--quiet'
-`--silent'
-`-q'
+‘--quiet’
+‘--silent’
+‘-q’
Do not print messages saying which checks are being made. To
- suppress all normal output, redirect it to `/dev/null' (any error
+ suppress all normal output, redirect it to ‘/dev/null’ (any error
messages will still be shown).
-`--srcdir=DIR'
+‘--srcdir=DIR’
Look for the package's source code in directory DIR. Usually
- `configure' can determine that directory automatically.
+ ‘configure’ can determine that directory automatically.
-`--version'
- Print the version of Autoconf used to generate the `configure'
+‘--version’
+ Print the version of Autoconf used to generate the ‘configure’
script, and exit.
-`configure' also accepts some other, not widely useful, options.
+‘configure’ also accepts some other, not widely useful, options.
* better C format string implementation. The xgettext will classify
strings as being a format string, or not, in the .po file. The
programmer can override the decision explicitly for each string
- by specifying `xgettext:c-format' and `xgettext:no-c-format'
+ by specifying 'xgettext:c-format' and 'xgettext:no-c-format'
respectively in a C comment preceding the string.
* msgmerge program now always produces output. Fuzzy or non-existing
* Norwegian translation by Karl Anders �gard
-* Configure command line option `--with-gnu-gettext' is renamed to
- `--with-included-gettext'
+* Configure command line option '--with-gnu-gettext' is renamed to
+ '--with-included-gettext'
* gettextize now can determine whether the aclocal.m4 of the project
is sufficent
+2012-01-26 Bruno Haible <bruno@clisp.org>
+
+ Modernize quoting.
+ * INSTALL: Process through sed -e "s/\`\([^']*\)'/‘\1’/g"
+ * Makefile.am (ABOUT-NLS): Likewise. Use --plaintext instead of
+ --no-header.
+
2011-06-03 Bruno Haible <bruno@clisp.org>
Copyright: Use LGPL 2.1 instead of LGPL 2.0.
=============
This package depends on a few other packages. They are listed in
-the file `DEPENDENCIES'. It is recommended to install the listed
+the file ‘DEPENDENCIES’. It is recommended to install the listed
packages before installing this package.
Basic Installation
==================
- The `configure' shell script attempts to guess correct values for
+ The ‘configure’ shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
-those values to create a `Makefile' in each directory of the package.
-It may also create one or more `.h' files containing system-dependent
-definitions. Finally, it creates a shell script `config.status' that
+those values to create a ‘Makefile’ in each directory of the package.
+It may also create one or more ‘.h’ files containing system-dependent
+definitions. Finally, it creates a shell script ‘config.status’ that
you can run in the future to recreate the current configuration, a file
-`config.cache' that saves the results of its tests to speed up
-reconfiguring, and a file `config.log' containing compiler output
-(useful mainly for debugging `configure').
+‘config.cache’ that saves the results of its tests to speed up
+reconfiguring, and a file ‘config.log’ containing compiler output
+(useful mainly for debugging ‘configure’).
If you need to do unusual things to compile the package, please try
-to figure out how `configure' could check whether to do them, and mail
-diffs or instructions to the address given in the `README' so they can
-be considered for the next release. If at some point `config.cache'
+to figure out how ‘configure’ could check whether to do them, and mail
+diffs or instructions to the address given in the ‘README’ so they can
+be considered for the next release. If at some point ‘config.cache’
contains results you don't want to keep, you may remove or edit it.
- The file `configure.ac' is used to create `configure' by a program
-called `autoconf'. You only need `configure.ac' if you want to change
-it or regenerate `configure' using a newer version of `autoconf'.
+ The file ‘configure.ac’ is used to create ‘configure’ by a program
+called ‘autoconf’. You only need ‘configure.ac’ if you want to change
+it or regenerate ‘configure’ using a newer version of ‘autoconf’.
The simplest way to compile this package is:
- 1. `cd' to the directory containing the package's source code and type
- `./configure' to configure the package for your system. If you're
- using `csh' on an old version of System V, you might need to type
- `sh ./configure' instead to prevent `csh' from trying to execute
- `configure' itself.
+ 1. ‘cd’ to the directory containing the package's source code and type
+ ‘./configure’ to configure the package for your system. If you're
+ using ‘csh’ on an old version of System V, you might need to type
+ ‘sh ./configure’ instead to prevent ‘csh’ from trying to execute
+ ‘configure’ itself.
- Running `configure' takes awhile. While running, it prints some
+ Running ‘configure’ takes awhile. While running, it prints some
messages telling which features it is checking for.
- 2. Type `make' to compile the package.
+ 2. Type ‘make’ to compile the package.
- 3. Optionally, type `make check' to run any self-tests that come with
+ 3. Optionally, type ‘make check’ to run any self-tests that come with
the package.
- 4. Type `make install' to install the programs and any data files and
+ 4. Type ‘make install’ to install the programs and any data files and
documentation.
5. You can remove the program binaries and object files from the
- source code directory by typing `make clean'. To also remove the
- files that `configure' created (so you can compile the package for
- a different kind of computer), type `make distclean'. There is
- also a `make maintainer-clean' target, but that is intended mainly
+ source code directory by typing ‘make clean’. To also remove the
+ files that ‘configure’ created (so you can compile the package for
+ a different kind of computer), type ‘make distclean’. There is
+ also a ‘make maintainer-clean’ target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
=====================
Some systems require unusual options for compilation or linking that
-the `configure' script does not know about. You can give `configure'
+the ‘configure’ script does not know about. You can give ‘configure’
initial values for variables as arguments. You can do it like this:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
-own directory. To do this, you must use a version of `make' that
-supports the `VPATH' variable, such as GNU `make'. `cd' to the
+own directory. To do this, you must use a version of ‘make’ that
+supports the ‘VPATH’ variable, such as GNU ‘make’. ‘cd’ to the
directory where you want the object files and executables to go and run
-the `configure' script. `configure' automatically checks for the
-source code in the directory that `configure' is in and in `..'.
+the ‘configure’ script. ‘configure’ automatically checks for the
+source code in the directory that ‘configure’ is in and in ‘..’.
- If you have to use a `make' that does not supports the `VPATH'
+ If you have to use a ‘make’ that does not supports the ‘VPATH’
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
-one architecture, use `make distclean' before reconfiguring for another
+one architecture, use ‘make distclean’ before reconfiguring for another
architecture.
On MacOS X 10.5 and later systems, you can create libraries and
Installation Names
==================
- By default, `make install' will install the package's files in
-`/usr/local/bin', `/usr/local/man', etc. You can specify an
-installation prefix other than `/usr/local' by giving `configure' the
-option `--prefix=PATH'.
+ By default, ‘make install’ will install the package's files in
+‘/usr/local/bin’, ‘/usr/local/man’, etc. You can specify an
+installation prefix other than ‘/usr/local’ by giving ‘configure’ the
+option ‘--prefix=PATH’.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
-give `configure' the option `--exec-prefix=PATH', the package will use
+give ‘configure’ the option ‘--exec-prefix=PATH’, the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
In addition, if you use an unusual directory layout you can give
-options like `--bindir=PATH' to specify different values for particular
-kinds of files. Run `configure --help' for a list of the directories
+options like ‘--bindir=PATH’ to specify different values for particular
+kinds of files. Run ‘configure --help’ for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
-with an extra prefix or suffix on their names by giving `configure' the
-option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+with an extra prefix or suffix on their names by giving ‘configure’ the
+option ‘--program-prefix=PREFIX’ or ‘--program-suffix=SUFFIX’.
Enabling Relocatability
=======================
that packages are not relocatable. It means a user cannot copy a
program, installed by another user on the same machine, to his home
directory, and have it work correctly (including i18n). So many users
-need to go through `configure; make; make install' with all its
+need to go through ‘configure; make; make install’ with all its
dependencies, options, and hurdles.
Red Hat, Debian, and similar package systems solve the "ease of
-installation" problem, but they hardwire path names, usually to `/usr'
-or `/usr/local'. This means that users need root privileges to install
+installation" problem, but they hardwire path names, usually to ‘/usr’
+or ‘/usr/local’. This means that users need root privileges to install
a binary package, and prevents installing two different versions of the
same binary package.
to do the same thing with a hard link _only_ if the hard link file is
in the same directory as the real program.
- To configure a program to be relocatable, add `--enable-relocatable'
-to the `configure' command line.
+ To configure a program to be relocatable, add ‘--enable-relocatable’
+to the ‘configure’ command line.
On some OSes the executables remember the location of shared
libraries and prefer them over any other search path. Therefore, such
an executable will look for its shared libraries first in the original
installation directory and only then in the current installation
-directory. Thus, for reliability, it is best to also give a `--prefix'
+directory. Thus, for reliability, it is best to also give a ‘--prefix’
option pointing to a directory that does not exist now and which never
-will be created, e.g. `--prefix=/nonexistent'. You may use
-`DESTDIR=DEST-DIR' on the `make' command line to avoid installing into
+will be created, e.g. ‘--prefix=/nonexistent’. You may use
+‘DESTDIR=DEST-DIR’ on the ‘make’ command line to avoid installing into
that directory.
We do not recommend using a prefix writable by unprivileged users
-(e.g. `/tmp/inst$$') because such a directory can be recreated by an
+(e.g. ‘/tmp/inst$$’) because such a directory can be recreated by an
unprivileged user after the original directory has been removed. We
also do not recommend prefixes that might be behind an automounter
-(e.g. `$HOME/inst$$') because of the performance impact of directory
+(e.g. ‘$HOME/inst$$’) because of the performance impact of directory
searching.
Here's a sample installation run that takes into account all these
make
make install DESTDIR=/tmp/inst$$
- Installation with `--enable-relocatable' will not work for setuid or
+ Installation with ‘--enable-relocatable’ will not work for setuid or
setgid executables, because such executables search only system library
paths for security reasons. Also, installation with
-`--enable-relocatable' might not work on OpenBSD, when the package
+‘--enable-relocatable’ might not work on OpenBSD, when the package
contains shared libraries and libtool versions 1.5.xx are used.
The runtime penalty and size penalty are negligible on GNU/Linux
Optional Features
=================
- Some packages pay attention to `--enable-FEATURE' options to
-`configure', where FEATURE indicates an optional part of the package.
-They may also pay attention to `--with-PACKAGE' options, where PACKAGE
-is something like `gnu-as' or `x' (for the X Window System). The
-`README' should mention any `--enable-' and `--with-' options that the
+ Some packages pay attention to ‘--enable-FEATURE’ options to
+‘configure’, where FEATURE indicates an optional part of the package.
+They may also pay attention to ‘--with-PACKAGE’ options, where PACKAGE
+is something like ‘gnu-as’ or ‘x’ (for the X Window System). The
+‘README’ should mention any ‘--enable-’ and ‘--with-’ options that the
package recognizes.
- For packages that use the X Window System, `configure' can usually
+ For packages that use the X Window System, ‘configure’ can usually
find the X include and library files automatically, but if it doesn't,
-you can use the `configure' options `--x-includes=DIR' and
-`--x-libraries=DIR' to specify their locations.
+you can use the ‘configure’ options ‘--x-includes=DIR’ and
+‘--x-libraries=DIR’ to specify their locations.
For packages that use the GNU libiconv library, you can use the
-`configure' option `--with-libiconv-prefix' to specify the prefix you
+‘configure’ option ‘--with-libiconv-prefix’ to specify the prefix you
used while installing GNU libiconv. This option is not necessary if
that other prefix is the same as the one now specified through --prefix.
For packages that use the GNU libintl library, you can use the
-`configure' option `--with-libintl-prefix' to specify the prefix you
+‘configure’ option ‘--with-libintl-prefix’ to specify the prefix you
used while installing GNU gettext-runtime. This option is not necessary if
that other prefix is the same as the one now specified through --prefix.
and if that doesn't work, install pre-built binaries of GCC for HP-UX.
On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
-parse its `<wchar.h>' header file. The option `-nodtk' can be used as
+parse its ‘<wchar.h>’ header file. The option ‘-nodtk’ can be used as
a workaround. If GNU CC is not installed, it is therefore recommended
to try
Specifying the System Type
==========================
- There may be some features `configure' can not figure out
+ There may be some features ‘configure’ can not figure out
automatically, but needs to determine by the type of host the package
-will run on. Usually `configure' can figure that out, but if it prints
+will run on. Usually ‘configure’ can figure that out, but if it prints
a message saying it can not guess the host type, give it the
-`--host=TYPE' option. TYPE can either be a short name for the system
-type, such as `sun4', or a canonical name with three fields:
+‘--host=TYPE’ option. TYPE can either be a short name for the system
+type, such as ‘sun4’, or a canonical name with three fields:
CPU-COMPANY-SYSTEM
-See the file `config.sub' for the possible values of each field. If
-`config.sub' isn't included in this package, then this package doesn't
+See the file ‘config.sub’ for the possible values of each field. If
+‘config.sub’ isn't included in this package, then this package doesn't
need to know the host type.
If you are building compiler tools for cross-compiling, you can also
-use the `--target=TYPE' option to select the type of system they will
-produce code for and the `--build=TYPE' option to select the type of
+use the ‘--target=TYPE’ option to select the type of system they will
+produce code for and the ‘--build=TYPE’ option to select the type of
system on which you are compiling the package.
Sharing Defaults
================
- If you want to set default values for `configure' scripts to share,
-you can create a site shell script called `config.site' that gives
-default values for variables like `CC', `cache_file', and `prefix'.
-`configure' looks for `PREFIX/share/config.site' if it exists, then
-`PREFIX/etc/config.site' if it exists. Or, you can set the
-`CONFIG_SITE' environment variable to the location of the site script.
-A warning: not all `configure' scripts look for a site script.
+ If you want to set default values for ‘configure’ scripts to share,
+you can create a site shell script called ‘config.site’ that gives
+default values for variables like ‘CC’, ‘cache_file’, and ‘prefix’.
+‘configure’ looks for ‘PREFIX/share/config.site’ if it exists, then
+‘PREFIX/etc/config.site’ if it exists. Or, you can set the
+‘CONFIG_SITE’ environment variable to the location of the site script.
+A warning: not all ‘configure’ scripts look for a site script.
Operation Controls
==================
- `configure' recognizes the following options to control how it
+ ‘configure’ recognizes the following options to control how it
operates.
-`--cache-file=FILE'
+‘--cache-file=FILE’
Use and save the results of the tests in FILE instead of
- `./config.cache'. Set FILE to `/dev/null' to disable caching, for
- debugging `configure'.
+ ‘./config.cache’. Set FILE to ‘/dev/null’ to disable caching, for
+ debugging ‘configure’.
-`--help'
- Print a summary of the options to `configure', and exit.
+‘--help’
+ Print a summary of the options to ‘configure’, and exit.
-`--quiet'
-`--silent'
-`-q'
+‘--quiet’
+‘--silent’
+‘-q’
Do not print messages saying which checks are being made. To
- suppress all normal output, redirect it to `/dev/null' (any error
+ suppress all normal output, redirect it to ‘/dev/null’ (any error
messages will still be shown).
-`--srcdir=DIR'
+‘--srcdir=DIR’
Look for the package's source code in directory DIR. Usually
- `configure' can determine that directory automatically.
+ ‘configure’ can determine that directory automatically.
-`--version'
- Print the version of Autoconf used to generate the `configure'
+‘--version’
+ Print the version of Autoconf used to generate the ‘configure’
script, and exit.
-`configure' also accepts some other, not widely useful, options.
+‘configure’ also accepts some other, not widely useful, options.
## Makefile for the gettext-runtime directory of GNU gettext
-## Copyright (C) 1995-1999, 2000-2006, 2010 Free Software Foundation, Inc.
+## Copyright (C) 1995-1999, 2000-2006, 2010, 2012 Free Software Foundation, Inc.
##
## This program is free software: you can redistribute it and/or modify
## it under the terms of the GNU General Public License as published by
ABOUT-NLS: $(srcdir)/doc/nls.texi $(srcdir)/doc/matrix.texi
rm -f $(srcdir)/ABOUT-NLS \
- && $(MAKEINFO) --output=$(srcdir)/ABOUT-NLS --no-header \
- -I $(srcdir)/doc --no-validate nls.texi
+ && $(MAKEINFO) --plaintext --no-validate -I $(srcdir)/doc nls.texi \
+ | sed -e "s/\`\([^']*\)'/‘\1’/g" > $(srcdir)/ABOUT-NLS
# Allow users to use "gnulib-tool --update".
+2012-01-26 Bruno Haible <bruno@clisp.org>
+
+ Modernize quoting.
+ * Makefile.in: Quote 'like this', not `like this', as per the recent
+ change to the GNU coding standards.
+ * libgnuintl.in.h: Likewise.
+ * vasnprintf.h: Likewise.
+
2012-01-06 Paul Eggert <eggert@cs.ucla.edu>
doc: C11 and C++11 are now official
# Makefile for directory with message catalog handling library of GNU gettext
-# Copyright (C) 1995-1998, 2000-2007, 2009-2011 Free Software Foundation, Inc.
+# Copyright (C) 1995-1998, 2000-2007, 2009-2012 Free Software Foundation, Inc.
#
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# system which has the GNU gettext() function in its C library or in a
# separate library.
# If you want to use the one which comes with this version of the
-# package, you have to use `configure --with-included-gettext'.
+# package, you have to use "configure --with-included-gettext".
install: install-exec install-data
install-exec: all
if { test "$(PACKAGE)" = "gettext-runtime" || test "$(PACKAGE)" = "gettext-tools"; } \
@echo "it deletes files that may require special tools to rebuild."
-# GNU gettext needs not contain the file `VERSION' but contains some
+# GNU gettext needs not contain the file 'VERSION' but contains some
# other files which should not be distributed in other packages.
distdir = ../$(PACKAGE)-$(VERSION)/$(subdir)
dist distdir: Makefile
/* Message catalogs for internationalization.
- Copyright (C) 1995-1997, 2000-2011 Free Software Foundation, Inc.
+ Copyright (C) 1995-1997, 2000-2012 Free Software Foundation, Inc.
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU Lesser General Public License as published by
#endif
-/* Similar to `gettext' but select the plural form corresponding to the
+/* Similar to 'gettext' but select the plural form corresponding to the
number N. */
#ifdef _INTL_REDIRECT_INLINE
extern char *libintl_ngettext (const char *__msgid1, const char *__msgid2,
_INTL_MAY_RETURN_STRING_ARG (1) _INTL_MAY_RETURN_STRING_ARG (2);
#endif
-/* Similar to `dgettext' but select the plural form corresponding to the
+/* Similar to 'dgettext' but select the plural form corresponding to the
number N. */
#ifdef _INTL_REDIRECT_INLINE
extern char *libintl_dngettext (const char *__domainname, const char *__msgid1,
_INTL_MAY_RETURN_STRING_ARG (2) _INTL_MAY_RETURN_STRING_ARG (3);
#endif
-/* Similar to `dcgettext' but select the plural form corresponding to the
+/* Similar to 'dcgettext' but select the plural form corresponding to the
number N. */
#ifdef _INTL_REDIRECT_INLINE
extern char *libintl_dcngettext (const char *__domainname,
/* vsprintf with automatic memory allocation.
- Copyright (C) 2002-2004 Free Software Foundation, Inc.
+ Copyright (C) 2002-2004, 2012 Free Software Foundation, Inc.
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU Lesser General Public License as published by
# if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 5) || __STRICT_ANSI__
# define __attribute__(Spec) /* empty */
# endif
-/* The __-protected variants of `format' and `printf' attributes
+/* The __-protected variants of 'format' and 'printf' attributes
are accepted by gcc versions 2.6.4 (effectively 2.7) and later. */
# if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 7)
# define __format__ format
+2012-01-26 Bruno Haible <bruno@clisp.org>
+
+ Modernize quoting.
+ * autosprintf.in.h: Quote 'like this', not `like this', as per the
+ recent change to the GNU coding standards.
+ * vasnprintf.h: Likewise.
+ * vasprintf.h: Likewise.
+ * INSTALL: Process through sed -e "s/\`\([^']*\)'/‘\1’/g"
+
2012-01-04 Bruno Haible <bruno@clisp.org>
Talk about "native Windows API", not "Win32".
=============
This package depends on a few other packages. They are listed in
-the file `DEPENDENCIES'. It is recommended to install the listed
+the file ‘DEPENDENCIES’. It is recommended to install the listed
packages before installing this package.
Basic Installation
==================
- The `configure' shell script attempts to guess correct values for
+ The ‘configure’ shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
-those values to create a `Makefile' in each directory of the package.
-It may also create one or more `.h' files containing system-dependent
-definitions. Finally, it creates a shell script `config.status' that
+those values to create a ‘Makefile’ in each directory of the package.
+It may also create one or more ‘.h’ files containing system-dependent
+definitions. Finally, it creates a shell script ‘config.status’ that
you can run in the future to recreate the current configuration, a file
-`config.cache' that saves the results of its tests to speed up
-reconfiguring, and a file `config.log' containing compiler output
-(useful mainly for debugging `configure').
+‘config.cache’ that saves the results of its tests to speed up
+reconfiguring, and a file ‘config.log’ containing compiler output
+(useful mainly for debugging ‘configure’).
If you need to do unusual things to compile the package, please try
-to figure out how `configure' could check whether to do them, and mail
-diffs or instructions to the address given in the `README' so they can
-be considered for the next release. If at some point `config.cache'
+to figure out how ‘configure’ could check whether to do them, and mail
+diffs or instructions to the address given in the ‘README’ so they can
+be considered for the next release. If at some point ‘config.cache’
contains results you don't want to keep, you may remove or edit it.
- The file `configure.ac' is used to create `configure' by a program
-called `autoconf'. You only need `configure.ac' if you want to change
-it or regenerate `configure' using a newer version of `autoconf'.
+ The file ‘configure.ac’ is used to create ‘configure’ by a program
+called ‘autoconf’. You only need ‘configure.ac’ if you want to change
+it or regenerate ‘configure’ using a newer version of ‘autoconf’.
The simplest way to compile this package is:
- 1. `cd' to the directory containing the package's source code and type
- `./configure' to configure the package for your system. If you're
- using `csh' on an old version of System V, you might need to type
- `sh ./configure' instead to prevent `csh' from trying to execute
- `configure' itself.
+ 1. ‘cd’ to the directory containing the package's source code and type
+ ‘./configure’ to configure the package for your system. If you're
+ using ‘csh’ on an old version of System V, you might need to type
+ ‘sh ./configure’ instead to prevent ‘csh’ from trying to execute
+ ‘configure’ itself.
- Running `configure' takes awhile. While running, it prints some
+ Running ‘configure’ takes awhile. While running, it prints some
messages telling which features it is checking for.
- 2. Type `make' to compile the package.
+ 2. Type ‘make’ to compile the package.
- 3. Optionally, type `make check' to run any self-tests that come with
+ 3. Optionally, type ‘make check’ to run any self-tests that come with
the package.
- 4. Type `make install' to install the programs and any data files and
+ 4. Type ‘make install’ to install the programs and any data files and
documentation.
5. You can remove the program binaries and object files from the
- source code directory by typing `make clean'. To also remove the
- files that `configure' created (so you can compile the package for
- a different kind of computer), type `make distclean'. There is
- also a `make maintainer-clean' target, but that is intended mainly
+ source code directory by typing ‘make clean’. To also remove the
+ files that ‘configure’ created (so you can compile the package for
+ a different kind of computer), type ‘make distclean’. There is
+ also a ‘make maintainer-clean’ target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
=====================
Some systems require unusual options for compilation or linking that
-the `configure' script does not know about. You can give `configure'
+the ‘configure’ script does not know about. You can give ‘configure’
initial values for variables as arguments. You can do it like this:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
-own directory. To do this, you must use a version of `make' that
-supports the `VPATH' variable, such as GNU `make'. `cd' to the
+own directory. To do this, you must use a version of ‘make’ that
+supports the ‘VPATH’ variable, such as GNU ‘make’. ‘cd’ to the
directory where you want the object files and executables to go and run
-the `configure' script. `configure' automatically checks for the
-source code in the directory that `configure' is in and in `..'.
+the ‘configure’ script. ‘configure’ automatically checks for the
+source code in the directory that ‘configure’ is in and in ‘..’.
- If you have to use a `make' that does not supports the `VPATH'
+ If you have to use a ‘make’ that does not supports the ‘VPATH’
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
-one architecture, use `make distclean' before reconfiguring for another
+one architecture, use ‘make distclean’ before reconfiguring for another
architecture.
On MacOS X 10.5 and later systems, you can create libraries and
Installation Names
==================
- By default, `make install' will install the package's files in
-`/usr/local/bin', `/usr/local/man', etc. You can specify an
-installation prefix other than `/usr/local' by giving `configure' the
-option `--prefix=PATH'.
+ By default, ‘make install’ will install the package's files in
+‘/usr/local/bin’, ‘/usr/local/man’, etc. You can specify an
+installation prefix other than ‘/usr/local’ by giving ‘configure’ the
+option ‘--prefix=PATH’.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
-give `configure' the option `--exec-prefix=PATH', the package will use
+give ‘configure’ the option ‘--exec-prefix=PATH’, the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
In addition, if you use an unusual directory layout you can give
-options like `--bindir=PATH' to specify different values for particular
-kinds of files. Run `configure --help' for a list of the directories
+options like ‘--bindir=PATH’ to specify different values for particular
+kinds of files. Run ‘configure --help’ for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
-with an extra prefix or suffix on their names by giving `configure' the
-option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+with an extra prefix or suffix on their names by giving ‘configure’ the
+option ‘--program-prefix=PREFIX’ or ‘--program-suffix=SUFFIX’.
Enabling Relocatability
=======================
that packages are not relocatable. It means a user cannot copy a
program, installed by another user on the same machine, to his home
directory, and have it work correctly (including i18n). So many users
-need to go through `configure; make; make install' with all its
+need to go through ‘configure; make; make install’ with all its
dependencies, options, and hurdles.
Red Hat, Debian, and similar package systems solve the "ease of
-installation" problem, but they hardwire path names, usually to `/usr'
-or `/usr/local'. This means that users need root privileges to install
+installation" problem, but they hardwire path names, usually to ‘/usr’
+or ‘/usr/local’. This means that users need root privileges to install
a binary package, and prevents installing two different versions of the
same binary package.
to do the same thing with a hard link _only_ if the hard link file is
in the same directory as the real program.
- To configure a program to be relocatable, add `--enable-relocatable'
-to the `configure' command line.
+ To configure a program to be relocatable, add ‘--enable-relocatable’
+to the ‘configure’ command line.
On some OSes the executables remember the location of shared
libraries and prefer them over any other search path. Therefore, such
an executable will look for its shared libraries first in the original
installation directory and only then in the current installation
-directory. Thus, for reliability, it is best to also give a `--prefix'
+directory. Thus, for reliability, it is best to also give a ‘--prefix’
option pointing to a directory that does not exist now and which never
-will be created, e.g. `--prefix=/nonexistent'. You may use
-`DESTDIR=DEST-DIR' on the `make' command line to avoid installing into
+will be created, e.g. ‘--prefix=/nonexistent’. You may use
+‘DESTDIR=DEST-DIR’ on the ‘make’ command line to avoid installing into
that directory.
We do not recommend using a prefix writable by unprivileged users
-(e.g. `/tmp/inst$$') because such a directory can be recreated by an
+(e.g. ‘/tmp/inst$$’) because such a directory can be recreated by an
unprivileged user after the original directory has been removed. We
also do not recommend prefixes that might be behind an automounter
-(e.g. `$HOME/inst$$') because of the performance impact of directory
+(e.g. ‘$HOME/inst$$’) because of the performance impact of directory
searching.
Here's a sample installation run that takes into account all these
make
make install DESTDIR=/tmp/inst$$
- Installation with `--enable-relocatable' will not work for setuid or
+ Installation with ‘--enable-relocatable’ will not work for setuid or
setgid executables, because such executables search only system library
paths for security reasons. Also, installation with
-`--enable-relocatable' might not work on OpenBSD, when the package
+‘--enable-relocatable’ might not work on OpenBSD, when the package
contains shared libraries and libtool versions 1.5.xx are used.
The runtime penalty and size penalty are negligible on GNU/Linux
Optional Features
=================
- Some packages pay attention to `--enable-FEATURE' options to
-`configure', where FEATURE indicates an optional part of the package.
-They may also pay attention to `--with-PACKAGE' options, where PACKAGE
-is something like `gnu-as' or `x' (for the X Window System). The
-`README' should mention any `--enable-' and `--with-' options that the
+ Some packages pay attention to ‘--enable-FEATURE’ options to
+‘configure’, where FEATURE indicates an optional part of the package.
+They may also pay attention to ‘--with-PACKAGE’ options, where PACKAGE
+is something like ‘gnu-as’ or ‘x’ (for the X Window System). The
+‘README’ should mention any ‘--enable-’ and ‘--with-’ options that the
package recognizes.
- For packages that use the X Window System, `configure' can usually
+ For packages that use the X Window System, ‘configure’ can usually
find the X include and library files automatically, but if it doesn't,
-you can use the `configure' options `--x-includes=DIR' and
-`--x-libraries=DIR' to specify their locations.
+you can use the ‘configure’ options ‘--x-includes=DIR’ and
+‘--x-libraries=DIR’ to specify their locations.
For packages that use the GNU libiconv library, you can use the
-`configure' option `--with-libiconv-prefix' to specify the prefix you
+‘configure’ option ‘--with-libiconv-prefix’ to specify the prefix you
used while installing GNU libiconv. This option is not necessary if
that other prefix is the same as the one now specified through --prefix.
For packages that use the GNU libintl library, you can use the
-`configure' option `--with-libintl-prefix' to specify the prefix you
+‘configure’ option ‘--with-libintl-prefix’ to specify the prefix you
used while installing GNU gettext-runtime. This option is not necessary if
that other prefix is the same as the one now specified through --prefix.
and if that doesn't work, install pre-built binaries of GCC for HP-UX.
On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
-parse its `<wchar.h>' header file. The option `-nodtk' can be used as
+parse its ‘<wchar.h>’ header file. The option ‘-nodtk’ can be used as
a workaround. If GNU CC is not installed, it is therefore recommended
to try
Specifying the System Type
==========================
- There may be some features `configure' can not figure out
+ There may be some features ‘configure’ can not figure out
automatically, but needs to determine by the type of host the package
-will run on. Usually `configure' can figure that out, but if it prints
+will run on. Usually ‘configure’ can figure that out, but if it prints
a message saying it can not guess the host type, give it the
-`--host=TYPE' option. TYPE can either be a short name for the system
-type, such as `sun4', or a canonical name with three fields:
+‘--host=TYPE’ option. TYPE can either be a short name for the system
+type, such as ‘sun4’, or a canonical name with three fields:
CPU-COMPANY-SYSTEM
-See the file `config.sub' for the possible values of each field. If
-`config.sub' isn't included in this package, then this package doesn't
+See the file ‘config.sub’ for the possible values of each field. If
+‘config.sub’ isn't included in this package, then this package doesn't
need to know the host type.
If you are building compiler tools for cross-compiling, you can also
-use the `--target=TYPE' option to select the type of system they will
-produce code for and the `--build=TYPE' option to select the type of
+use the ‘--target=TYPE’ option to select the type of system they will
+produce code for and the ‘--build=TYPE’ option to select the type of
system on which you are compiling the package.
Sharing Defaults
================
- If you want to set default values for `configure' scripts to share,
-you can create a site shell script called `config.site' that gives
-default values for variables like `CC', `cache_file', and `prefix'.
-`configure' looks for `PREFIX/share/config.site' if it exists, then
-`PREFIX/etc/config.site' if it exists. Or, you can set the
-`CONFIG_SITE' environment variable to the location of the site script.
-A warning: not all `configure' scripts look for a site script.
+ If you want to set default values for ‘configure’ scripts to share,
+you can create a site shell script called ‘config.site’ that gives
+default values for variables like ‘CC’, ‘cache_file’, and ‘prefix’.
+‘configure’ looks for ‘PREFIX/share/config.site’ if it exists, then
+‘PREFIX/etc/config.site’ if it exists. Or, you can set the
+‘CONFIG_SITE’ environment variable to the location of the site script.
+A warning: not all ‘configure’ scripts look for a site script.
Operation Controls
==================
- `configure' recognizes the following options to control how it
+ ‘configure’ recognizes the following options to control how it
operates.
-`--cache-file=FILE'
+‘--cache-file=FILE’
Use and save the results of the tests in FILE instead of
- `./config.cache'. Set FILE to `/dev/null' to disable caching, for
- debugging `configure'.
+ ‘./config.cache’. Set FILE to ‘/dev/null’ to disable caching, for
+ debugging ‘configure’.
-`--help'
- Print a summary of the options to `configure', and exit.
+‘--help’
+ Print a summary of the options to ‘configure’, and exit.
-`--quiet'
-`--silent'
-`-q'
+‘--quiet’
+‘--silent’
+‘-q’
Do not print messages saying which checks are being made. To
- suppress all normal output, redirect it to `/dev/null' (any error
+ suppress all normal output, redirect it to ‘/dev/null’ (any error
messages will still be shown).
-`--srcdir=DIR'
+‘--srcdir=DIR’
Look for the package's source code in directory DIR. Usually
- `configure' can determine that directory automatically.
+ ‘configure’ can determine that directory automatically.
-`--version'
- Print the version of Autoconf used to generate the `configure'
+‘--version’
+ Print the version of Autoconf used to generate the ‘configure’
script, and exit.
-`configure' also accepts some other, not widely useful, options.
+‘configure’ also accepts some other, not widely useful, options.
/* Class autosprintf - formatted output to an ostream.
- Copyright (C) 2002 Free Software Foundation, Inc.
+ Copyright (C) 2002, 2012 Free Software Foundation, Inc.
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU Lesser General Public License as published by
# if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 5) || __STRICT_ANSI__
# define __attribute__(Spec) /* empty */
# endif
-/* The __-protected variants of `format' and `printf' attributes
+/* The __-protected variants of 'format' and 'printf' attributes
are accepted by gcc versions 2.6.4 (effectively 2.7) and later. */
# if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 7)
# define __format__ format
/* vsprintf with automatic memory allocation.
- Copyright (C) 2002-2004 Free Software Foundation, Inc.
+ Copyright (C) 2002-2004, 2012 Free Software Foundation, Inc.
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU Lesser General Public License as published by
# if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 5) || __STRICT_ANSI__
# define __attribute__(Spec) /* empty */
# endif
-/* The __-protected variants of `format' and `printf' attributes
+/* The __-protected variants of 'format' and 'printf' attributes
are accepted by gcc versions 2.6.4 (effectively 2.7) and later. */
# if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 7)
# define __format__ format
/* vsprintf with automatic memory allocation.
- Copyright (C) 2002-2003 Free Software Foundation, Inc.
+ Copyright (C) 2002-2003, 2012 Free Software Foundation, Inc.
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU Lesser General Public License as published by
# if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 5) || __STRICT_ANSI__
# define __attribute__(Spec) /* empty */
# endif
-/* The __-protected variants of `format' and `printf' attributes
+/* The __-protected variants of 'format' and 'printf' attributes
are accepted by gcc versions 2.6.4 (effectively 2.7) and later. */
# if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 7)
# define __format__ format
+2012-01-26 Bruno Haible <bruno@clisp.org>
+
+ Modernize quoting.
+ * envsubst.c (usage): Quote 'like this', not `like this', as per the
+ recent change to the GNU coding standards.
+ * gettext.c (usage): Likewise.
+ * ngettext.c (usage): Likewise.
+
2011-06-03 Bruno Haible <bruno@clisp.org>
Copyright: Use LGPL 2.1 instead of LGPL 2.0.
/* Substitution of environment variables in shell format strings.
- Copyright (C) 2003-2007 Free Software Foundation, Inc.
+ Copyright (C) 2003-2007, 2012 Free Software Foundation, Inc.
Written by Bruno Haible <bruno@clisp.org>, 2003.
This program is free software: you can redistribute it and/or modify
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
/* gettext - retrieve text string from message catalog and print it.
- Copyright (C) 1995-1997, 2000-2007 Free Software Foundation, Inc.
+ Copyright (C) 1995-1997, 2000-2007, 2012 Free Software Foundation, Inc.
Written by Ulrich Drepper <drepper@gnu.ai.mit.edu>, May 1995.
This program is free software: you can redistribute it and/or modify
#define _(str) gettext (str)
/* If true, add newline after last string. This makes only sense in
- the `echo' emulation mode. */
+ the 'echo' emulation mode. */
static bool add_newline;
/* If true, expand escape sequences in strings before looking in the
usage (EXIT_SUCCESS);
/* We have two major modes: use following Uniforum spec and as
- internationalized `echo' program. */
+ internationalized 'echo' program. */
if (!do_shell)
{
/* We have to write a single strings translation to stdout. */
if (domaindir != NULL && domaindir[0] != '\0')
bindtextdomain (domain, domaindir);
- /* We have to simulate `echo'. All arguments are strings. */
+ /* We have to simulate 'echo'. All arguments are strings. */
do
{
msgid = argv[optind++];
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
environment variable TEXTDOMAIN. If the message catalog is not found in the\n\
regular directory, another location can be specified with the environment\n\
variable TEXTDOMAINDIR.\n\
-When used with the -s option the program behaves like the `echo' command.\n\
+When used with the -s option the program behaves like the 'echo' command.\n\
But it does not simply copy its arguments to stdout. Instead those messages\n\
found in the selected catalog are translated.\n\
Standard search directory: %s\n"),
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
+2012-01-26 Bruno Haible <bruno@clisp.org>
+
+ Modernize quoting.
+ * INSTALL: Process through sed -e "s/\`\([^']*\)'/‘\1’/g"
+
2012-01-15 Bruno Haible <bruno@clisp.org>
Support for MSVC 9.
=============
This package depends on a few other packages. They are listed in
-the file `DEPENDENCIES'. It is recommended to install the listed
+the file ‘DEPENDENCIES’. It is recommended to install the listed
packages before installing this package.
Basic Installation
==================
- The `configure' shell script attempts to guess correct values for
+ The ‘configure’ shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
-those values to create a `Makefile' in each directory of the package.
-It may also create one or more `.h' files containing system-dependent
-definitions. Finally, it creates a shell script `config.status' that
+those values to create a ‘Makefile’ in each directory of the package.
+It may also create one or more ‘.h’ files containing system-dependent
+definitions. Finally, it creates a shell script ‘config.status’ that
you can run in the future to recreate the current configuration, a file
-`config.cache' that saves the results of its tests to speed up
-reconfiguring, and a file `config.log' containing compiler output
-(useful mainly for debugging `configure').
+‘config.cache’ that saves the results of its tests to speed up
+reconfiguring, and a file ‘config.log’ containing compiler output
+(useful mainly for debugging ‘configure’).
If you need to do unusual things to compile the package, please try
-to figure out how `configure' could check whether to do them, and mail
-diffs or instructions to the address given in the `README' so they can
-be considered for the next release. If at some point `config.cache'
+to figure out how ‘configure’ could check whether to do them, and mail
+diffs or instructions to the address given in the ‘README’ so they can
+be considered for the next release. If at some point ‘config.cache’
contains results you don't want to keep, you may remove or edit it.
- The file `configure.ac' is used to create `configure' by a program
-called `autoconf'. You only need `configure.ac' if you want to change
-it or regenerate `configure' using a newer version of `autoconf'.
+ The file ‘configure.ac’ is used to create ‘configure’ by a program
+called ‘autoconf’. You only need ‘configure.ac’ if you want to change
+it or regenerate ‘configure’ using a newer version of ‘autoconf’.
The simplest way to compile this package is:
- 1. `cd' to the directory containing the package's source code and type
- `./configure' to configure the package for your system. If you're
- using `csh' on an old version of System V, you might need to type
- `sh ./configure' instead to prevent `csh' from trying to execute
- `configure' itself.
+ 1. ‘cd’ to the directory containing the package's source code and type
+ ‘./configure’ to configure the package for your system. If you're
+ using ‘csh’ on an old version of System V, you might need to type
+ ‘sh ./configure’ instead to prevent ‘csh’ from trying to execute
+ ‘configure’ itself.
- Running `configure' takes awhile. While running, it prints some
+ Running ‘configure’ takes awhile. While running, it prints some
messages telling which features it is checking for.
- 2. Type `make' to compile the package.
+ 2. Type ‘make’ to compile the package.
- 3. Optionally, type `make check' to run any self-tests that come with
+ 3. Optionally, type ‘make check’ to run any self-tests that come with
the package.
- 4. Type `make install' to install the programs and any data files and
+ 4. Type ‘make install’ to install the programs and any data files and
documentation.
5. You can remove the program binaries and object files from the
- source code directory by typing `make clean'. To also remove the
- files that `configure' created (so you can compile the package for
- a different kind of computer), type `make distclean'. There is
- also a `make maintainer-clean' target, but that is intended mainly
+ source code directory by typing ‘make clean’. To also remove the
+ files that ‘configure’ created (so you can compile the package for
+ a different kind of computer), type ‘make distclean’. There is
+ also a ‘make maintainer-clean’ target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
=====================
Some systems require unusual options for compilation or linking that
-the `configure' script does not know about. You can give `configure'
+the ‘configure’ script does not know about. You can give ‘configure’
initial values for variables as arguments. You can do it like this:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
-own directory. To do this, you must use a version of `make' that
-supports the `VPATH' variable, such as GNU `make'. `cd' to the
+own directory. To do this, you must use a version of ‘make’ that
+supports the ‘VPATH’ variable, such as GNU ‘make’. ‘cd’ to the
directory where you want the object files and executables to go and run
-the `configure' script. `configure' automatically checks for the
-source code in the directory that `configure' is in and in `..'.
+the ‘configure’ script. ‘configure’ automatically checks for the
+source code in the directory that ‘configure’ is in and in ‘..’.
- If you have to use a `make' that does not supports the `VPATH'
+ If you have to use a ‘make’ that does not supports the ‘VPATH’
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
-one architecture, use `make distclean' before reconfiguring for another
+one architecture, use ‘make distclean’ before reconfiguring for another
architecture.
On MacOS X 10.5 and later systems, you can create libraries and
Installation Names
==================
- By default, `make install' will install the package's files in
-`/usr/local/bin', `/usr/local/man', etc. You can specify an
-installation prefix other than `/usr/local' by giving `configure' the
-option `--prefix=PATH'.
+ By default, ‘make install’ will install the package's files in
+‘/usr/local/bin’, ‘/usr/local/man’, etc. You can specify an
+installation prefix other than ‘/usr/local’ by giving ‘configure’ the
+option ‘--prefix=PATH’.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
-give `configure' the option `--exec-prefix=PATH', the package will use
+give ‘configure’ the option ‘--exec-prefix=PATH’, the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
In addition, if you use an unusual directory layout you can give
-options like `--bindir=PATH' to specify different values for particular
-kinds of files. Run `configure --help' for a list of the directories
+options like ‘--bindir=PATH’ to specify different values for particular
+kinds of files. Run ‘configure --help’ for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
-with an extra prefix or suffix on their names by giving `configure' the
-option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+with an extra prefix or suffix on their names by giving ‘configure’ the
+option ‘--program-prefix=PREFIX’ or ‘--program-suffix=SUFFIX’.
Enabling Relocatability
=======================
that packages are not relocatable. It means a user cannot copy a
program, installed by another user on the same machine, to his home
directory, and have it work correctly (including i18n). So many users
-need to go through `configure; make; make install' with all its
+need to go through ‘configure; make; make install’ with all its
dependencies, options, and hurdles.
Red Hat, Debian, and similar package systems solve the "ease of
-installation" problem, but they hardwire path names, usually to `/usr'
-or `/usr/local'. This means that users need root privileges to install
+installation" problem, but they hardwire path names, usually to ‘/usr’
+or ‘/usr/local’. This means that users need root privileges to install
a binary package, and prevents installing two different versions of the
same binary package.
to do the same thing with a hard link _only_ if the hard link file is
in the same directory as the real program.
- To configure a program to be relocatable, add `--enable-relocatable'
-to the `configure' command line.
+ To configure a program to be relocatable, add ‘--enable-relocatable’
+to the ‘configure’ command line.
On some OSes the executables remember the location of shared
libraries and prefer them over any other search path. Therefore, such
an executable will look for its shared libraries first in the original
installation directory and only then in the current installation
-directory. Thus, for reliability, it is best to also give a `--prefix'
+directory. Thus, for reliability, it is best to also give a ‘--prefix’
option pointing to a directory that does not exist now and which never
-will be created, e.g. `--prefix=/nonexistent'. You may use
-`DESTDIR=DEST-DIR' on the `make' command line to avoid installing into
+will be created, e.g. ‘--prefix=/nonexistent’. You may use
+‘DESTDIR=DEST-DIR’ on the ‘make’ command line to avoid installing into
that directory.
We do not recommend using a prefix writable by unprivileged users
-(e.g. `/tmp/inst$$') because such a directory can be recreated by an
+(e.g. ‘/tmp/inst$$’) because such a directory can be recreated by an
unprivileged user after the original directory has been removed. We
also do not recommend prefixes that might be behind an automounter
-(e.g. `$HOME/inst$$') because of the performance impact of directory
+(e.g. ‘$HOME/inst$$’) because of the performance impact of directory
searching.
Here's a sample installation run that takes into account all these
make
make install DESTDIR=/tmp/inst$$
- Installation with `--enable-relocatable' will not work for setuid or
+ Installation with ‘--enable-relocatable’ will not work for setuid or
setgid executables, because such executables search only system library
paths for security reasons. Also, installation with
-`--enable-relocatable' might not work on OpenBSD, when the package
+‘--enable-relocatable’ might not work on OpenBSD, when the package
contains shared libraries and libtool versions 1.5.xx are used.
The runtime penalty and size penalty are negligible on GNU/Linux
Optional Features
=================
- Some packages pay attention to `--enable-FEATURE' options to
-`configure', where FEATURE indicates an optional part of the package.
-They may also pay attention to `--with-PACKAGE' options, where PACKAGE
-is something like `gnu-as' or `x' (for the X Window System). The
-`README' should mention any `--enable-' and `--with-' options that the
+ Some packages pay attention to ‘--enable-FEATURE’ options to
+‘configure’, where FEATURE indicates an optional part of the package.
+They may also pay attention to ‘--with-PACKAGE’ options, where PACKAGE
+is something like ‘gnu-as’ or ‘x’ (for the X Window System). The
+‘README’ should mention any ‘--enable-’ and ‘--with-’ options that the
package recognizes.
- For packages that use the X Window System, `configure' can usually
+ For packages that use the X Window System, ‘configure’ can usually
find the X include and library files automatically, but if it doesn't,
-you can use the `configure' options `--x-includes=DIR' and
-`--x-libraries=DIR' to specify their locations.
+you can use the ‘configure’ options ‘--x-includes=DIR’ and
+‘--x-libraries=DIR’ to specify their locations.
For packages that use the GNU libiconv library, you can use the
-`configure' option `--with-libiconv-prefix' to specify the prefix you
+‘configure’ option ‘--with-libiconv-prefix’ to specify the prefix you
used while installing GNU libiconv. This option is not necessary if
that other prefix is the same as the one now specified through --prefix.
For packages that use the GNU libintl library, you can use the
-`configure' option `--with-libintl-prefix' to specify the prefix you
+‘configure’ option ‘--with-libintl-prefix’ to specify the prefix you
used while installing GNU gettext-runtime. This option is not necessary if
that other prefix is the same as the one now specified through --prefix.
and if that doesn't work, install pre-built binaries of GCC for HP-UX.
On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
-parse its `<wchar.h>' header file. The option `-nodtk' can be used as
+parse its ‘<wchar.h>’ header file. The option ‘-nodtk’ can be used as
a workaround. If GNU CC is not installed, it is therefore recommended
to try
Specifying the System Type
==========================
- There may be some features `configure' can not figure out
+ There may be some features ‘configure’ can not figure out
automatically, but needs to determine by the type of host the package
-will run on. Usually `configure' can figure that out, but if it prints
+will run on. Usually ‘configure’ can figure that out, but if it prints
a message saying it can not guess the host type, give it the
-`--host=TYPE' option. TYPE can either be a short name for the system
-type, such as `sun4', or a canonical name with three fields:
+‘--host=TYPE’ option. TYPE can either be a short name for the system
+type, such as ‘sun4’, or a canonical name with three fields:
CPU-COMPANY-SYSTEM
-See the file `config.sub' for the possible values of each field. If
-`config.sub' isn't included in this package, then this package doesn't
+See the file ‘config.sub’ for the possible values of each field. If
+‘config.sub’ isn't included in this package, then this package doesn't
need to know the host type.
If you are building compiler tools for cross-compiling, you can also
-use the `--target=TYPE' option to select the type of system they will
-produce code for and the `--build=TYPE' option to select the type of
+use the ‘--target=TYPE’ option to select the type of system they will
+produce code for and the ‘--build=TYPE’ option to select the type of
system on which you are compiling the package.
Sharing Defaults
================
- If you want to set default values for `configure' scripts to share,
-you can create a site shell script called `config.site' that gives
-default values for variables like `CC', `cache_file', and `prefix'.
-`configure' looks for `PREFIX/share/config.site' if it exists, then
-`PREFIX/etc/config.site' if it exists. Or, you can set the
-`CONFIG_SITE' environment variable to the location of the site script.
-A warning: not all `configure' scripts look for a site script.
+ If you want to set default values for ‘configure’ scripts to share,
+you can create a site shell script called ‘config.site’ that gives
+default values for variables like ‘CC’, ‘cache_file’, and ‘prefix’.
+‘configure’ looks for ‘PREFIX/share/config.site’ if it exists, then
+‘PREFIX/etc/config.site’ if it exists. Or, you can set the
+‘CONFIG_SITE’ environment variable to the location of the site script.
+A warning: not all ‘configure’ scripts look for a site script.
Operation Controls
==================
- `configure' recognizes the following options to control how it
+ ‘configure’ recognizes the following options to control how it
operates.
-`--cache-file=FILE'
+‘--cache-file=FILE’
Use and save the results of the tests in FILE instead of
- `./config.cache'. Set FILE to `/dev/null' to disable caching, for
- debugging `configure'.
+ ‘./config.cache’. Set FILE to ‘/dev/null’ to disable caching, for
+ debugging ‘configure’.
-`--help'
- Print a summary of the options to `configure', and exit.
+‘--help’
+ Print a summary of the options to ‘configure’, and exit.
-`--quiet'
-`--silent'
-`-q'
+‘--quiet’
+‘--silent’
+‘-q’
Do not print messages saying which checks are being made. To
- suppress all normal output, redirect it to `/dev/null' (any error
+ suppress all normal output, redirect it to ‘/dev/null’ (any error
messages will still be shown).
-`--srcdir=DIR'
+‘--srcdir=DIR’
Look for the package's source code in directory DIR. Usually
- `configure' can determine that directory automatically.
+ ‘configure’ can determine that directory automatically.
-`--version'
- Print the version of Autoconf used to generate the `configure'
+‘--version’
+ Print the version of Autoconf used to generate the ‘configure’
script, and exit.
-`configure' also accepts some other, not widely useful, options.
+‘configure’ also accepts some other, not widely useful, options.
+2012-01-26 Bruno Haible <bruno@clisp.org>
+
+ Modernize quoting.
+ * FAQ.html: Quote 'like this', not `like this', as per the recent
+ change to the GNU coding standards.
+ * ISO_3166: Likewise.
+ * ISO_3166_de: Likewise.
+ * tutorial.html: Process through
+ sed -e "s/\`\`\([^']*\)''/“\1”/g" | sed -e "s/\`\([^']*\)'/‘\1’/g"
+
2011-07-08 Bruno Haible <bruno@clisp.org>
* gettext.texi (aclocal): Recommend the use of aclocal's --install
</ul>
<h3>Other</h3>
<ul>
- <li><a href="#newline">What does this mean: “`msgid' and `msgstr'
+ <li><a href="#newline">What does this mean: “'msgid' and 'msgstr'
entries do not both
end with '\n'”</a></li>
<li><a href="#translit">German umlauts are displayed like “ge"andert”
</li>
</ul>
<h3>Other</h3>
-<h4><a name="newline"></a>What does this mean: “`msgid' and `msgstr'
+<h4><a name="newline"></a>What does this mean: “'msgid' and 'msgstr'
entries do not both end
with '\n'”</h4>
It means that when the original string ends in a newline, your
# Columns are separated by a single tab.
# The table is sorted by country code.
#
-# Lines beginning with `#' are comments.
+# Lines beginning with '#' are comments.
#
#country-
#code country name
# Columns are separated by a single tab.
# The table is sorted by 2-letter country code.
#
-# Lines beginning with `#' are comments.
+# Lines beginning with '#' are comments.
#
AD AND Andorra
AE ARE Vereinigte Arabische Emirate
A simple example</A>
</H1>
<A NAME="sec:simple"></A>Our first example of using <TT>gettext</TT> will be the good old Hello World program,
-whose sole function is to print the phrase ``Hello, world!'' to the terminal.
+whose sole function is to print the phrase “Hello, world!” to the terminal.
The internationalized version of this program might be saved in hello.c as:
<PRE>
1 #include <libintl.h>
The programmer's viewpoint</A>
</H2>
As expected, when the <TT>hello</TT> executable is run under the default locale
-(usually the C locale) it prints ``Hello, world!'' in the terminal. Besides
+(usually the C locale) it prints “Hello, world!” in the terminal. Besides
some initial setup work, the only additional burden faced by the programmer is
to replace any string to be printed with <TT>gettext(string)</TT>, i.e., to
instead pass the string as an argument to the <TT>gettext</TT> function. For lazy
and an empty string as the second one, initializes the entire current locale
of the program as per environment variables set by the user. In other words,
the program locale is initialized to match that of the user. For details see
- ``man <TT>setlocale</TT>.''
+ “man <TT>setlocale</TT>.”
</LI>
<LI>The <TT>bindtextdomain</TT> function on line 8 sets the base directory for the
message catalogs for a given message domain. A message domain is a set of
translatable messages, with every software package typically having its own
- domain. Here, we have used ``hello'' as the name of the message domain for
+ domain. Here, we have used “hello” as the name of the message domain for
our toy program. As the second argument, /usr/share/locale, is the default
system location for message catalogs, what we are saying here is that we are
going to place the message catalog in the default system directory. Thus, we
could have dispensed with the call to <TT>bindtextdomain</TT> here, and this
function is useful only if the message catalogs are installed in a
non-standard place, e.g., a packaged software distribution might have
- the catalogs under a po/ directory under its own main directory. See ``man
- <TT>bindtextdomain</TT>'' for details.
+ the catalogs under a po/ directory under its own main directory. See “man
+ <TT>bindtextdomain</TT>” for details.
</LI>
<LI>The <TT>textdomain</TT> call on line 9 sets the message domain of the current
- program to ``hello,'' i.e., the name that we are using for our example
- program. ``man textdomain'' will give usage details for the function.
+ program to “hello,” i.e., the name that we are using for our example
+ program. “man textdomain” will give usage details for the function.
</LI>
<LI>Finally, on line 10, we have replaced what would normally have been,
<PRE>
The message domain for the program should be specified as the argument
to the -d option, and should match the domain specified in the call to
<TT>textdomain</TT> (on line 9 of the program source). Other details on how to use
-<TT>gettext</TT> can be found from ``man gettext.''
+<TT>gettext</TT> can be found from “man gettext.”
<P>
A .pot (portable object template) file is used as the basis for translating
the corresponding English string. For the <TT>msgstr</TT> line in each of the
remaining entries, add the translated Oriya text between the double quotes;
the translation corresponding to the English phrase in the <TT>msgid</TT> string
-for the entry. For example, for the phrase ``Hello world!<!-- MATH
+for the entry. For example, for the phrase “Hello world!<!-- MATH
$\backslash$
-->
-<SPAN CLASS="MATH">\</SPAN>n'' in
-oriya.po, we could enter ``ନମସ୍କାର<!-- MATH
+<SPAN CLASS="MATH">\</SPAN>n” in
+oriya.po, we could enter “ନମସ୍କାର<!-- MATH
$\backslash$
-->
-<SPAN CLASS="MATH">\</SPAN>n''. The final
+<SPAN CLASS="MATH">\</SPAN>n”. The final
oriya.po file might look like:
<PRE>
# Oriya translations for hello example package.
file will be in the sub-directory LL/LC_MESSAGES or LL_CC/LC_MESSAGES under
the base directory, where LL stands for a language, and CC for a country. For
example, as we have chosen the standard location, /usr/share/locale, for our
-base directory, and for us the language and country strings are ``or'' and
-``IN,'' respectively, we will place hello.mo in /usr/share/locale/or_IN. Note
+base directory, and for us the language and country strings are “or” and
+“IN,” respectively, we will place hello.mo in /usr/share/locale/or_IN. Note
that you will need super-user privilege to copy hello.mo to this system
directory. Thus,
<PRE><FONT color="red">
seems to have better support for internationalization. gnome-terminal needs to
be told that the bytes arriving are UTF-8 encoded multibyte sequences. This
can be done by (a) choosing Terminal <TT>-></TT> Character Coding <TT>-></TT>
-Unicode (UTF-8), or (b) typing ``/bin/echo -n -e
+Unicode (UTF-8), or (b) typing “/bin/echo -n -e
'<!-- MATH
$\backslash$
-->
<SPAN CLASS="MATH">\</SPAN>033%<!-- MATH
$\backslash$
-->
-<SPAN CLASS="MATH">\</SPAN>G''' in the terminal, or (c) by running
+<SPAN CLASS="MATH">\</SPAN>G'” in the terminal, or (c) by running
/bin/unicode_start. Likewise, you can revert to the default locale by (a)
choosing Terminal <TT>-></TT> Character Coding <TT>-></TT> Current Locale
-(ISO-8859-1), or (b) ``/bin/echo -n -e '<!-- MATH
+(ISO-8859-1), or (b) “/bin/echo -n -e '<!-- MATH
$\backslash$
-->
<SPAN CLASS="MATH">\</SPAN>033%<!-- MATH
$\backslash$
-->
-<SPAN CLASS="MATH">\</SPAN>@','' or
+<SPAN CLASS="MATH">\</SPAN>@',” or
(c) by running /bin/unicode_stop. Now, running the example program (after
compiling with gcc as described in Sec. <A HREF="#sec:simple">2</A>) with,
<PRE><FONT color="red">
./hello
</FONT></PRE>
should give you output in Oriya. Please note that conjuncts will most likely
-be displayed with a ``halant'' as the terminal probably does not render Indian
+be displayed with a “halant” as the terminal probably does not render Indian
language fonts correctly. Also, as most terminal emulators assume fixed-width
fonts, the results are hardly likely to be aesthetically appealing.
</FONT></PRE>
The -U option updates the existing
.po file, oriya.po. We could have chosen to instead create a new .po file by
-using ``-o <SPAN CLASS="MATH"><</SPAN>filename<SPAN CLASS="MATH">></SPAN>'' instead of -U. The updated .po file will still
+using “-o <SPAN CLASS="MATH"><</SPAN>filename<SPAN CLASS="MATH">></SPAN>” instead of -U. The updated .po file will still
have the old translations embedded in it, and new entries with untranslated
<TT>msgid</TT> lines. For us, the new lines in oriya.po will look like,
<PRE>
msgid "How are you?\n"
msgstr ""
</PRE>
-For the new translation, we could use, ``ଆପଣ
-କିପରି ଅଛନ୍ତି?'' in
-place of the English phrase ``How are you?'' The updated oriya.po file,
+For the new translation, we could use, “ଆପଣ
+କିପରି ଅଛନ୍ତି?” in
+place of the English phrase “How are you?” The updated oriya.po file,
including the translation might look like:
<PRE>
# Oriya translations for hello example package.
<H1><A NAME="SECTION00070000000000000000">
The Emacs info browser</A>
</H1>
-<A NAME="sec:emacs-info"></A>You can start up Emacs from the command-line by typing ``emacs,'' or ``emacs
-<SPAN CLASS="MATH"><</SPAN>filename<SPAN CLASS="MATH">></SPAN>.'' It can be started from the menu in some desktops, e.g., on
+<A NAME="sec:emacs-info"></A>You can start up Emacs from the command-line by typing “emacs,” or “emacs
+<SPAN CLASS="MATH"><</SPAN>filename<SPAN CLASS="MATH">></SPAN>.” It can be started from the menu in some desktops, e.g., on
my GNOME desktop, it is under Main Menu <TT>-></TT> Programming <TT>-></TT>
Emacs. If you are unfamiliar with Emacs, a tutorial can be started by typing
-``C-h t'' in an Emacs window, or from the Help item in the menubar at the
-top. Emacs makes extensive use of the Control (sometimes labelled as ``CTRL''
-or ``CTL'') and Meta (sometimes labelled as ``Edit'' or ``Alt'') keys. In
-Emacs parlance, a hyphenated sequence, such as ``C-h'' means to press the
-Control and `h' key simultaneously, while ``C-h t'' would mean to press the
-Control and `h' key together, release them, and press the `t' key. Similarly,
-``M-x'' is used to indicate that the Meta and `x' keys should be pressed at
+“C-h t” in an Emacs window, or from the Help item in the menubar at the
+top. Emacs makes extensive use of the Control (sometimes labelled as “CTRL”
+or “CTL”) and Meta (sometimes labelled as “Edit” or “Alt”) keys. In
+Emacs parlance, a hyphenated sequence, such as “C-h” means to press the
+Control and ‘h’ key simultaneously, while “C-h t” would mean to press the
+Control and ‘h’ key together, release them, and press the ‘t’ key. Similarly,
+“M-x” is used to indicate that the Meta and ‘x’ keys should be pressed at
the same time.
<P>
-The info browser can be started by typing ``C-h i'' in Emacs. The first time
+The info browser can be started by typing “C-h i” in Emacs. The first time
you do this, it will briefly list some commands available inside the info
browser, and present you with a menu of major topics. Each menu item, or
cross-reference is hyperlinked to the appropriate node, and you can visit that
* gettext: (gettext). GNU gettext utilities.
</PRE>
and visit that node. Or, as it is several pages down, you can locate it using
-``I-search.'' Type ``C-s'' to enter ``I-search'' which will then prompt you
+“I-search.” Type “C-s” to enter “I-search” which will then prompt you
for a string in the mini-buffer at the bottom of the window. This is an
incremental search, so that Emacs will keep moving you forward through the
buffer as you are entering your search string. If you have reached the last
occurrence of the search string in the current buffer, you will get a message
-saying ``Failing I-search: ...'' on pressing ``C-s.'' At that point, press
-``C-s'' again to resume the search at the beginning of the buffer. Likewise,
-``C-r'' incrementally searches backwards from the present location.
+saying “Failing I-search: ...” on pressing “C-s.” At that point, press
+“C-s” again to resume the search at the beginning of the buffer. Likewise,
+“C-r” incrementally searches backwards from the present location.
<P>
-Info nodes are listed in this document with a ``::'' separator, so
+Info nodes are listed in this document with a “::” separator, so
that one can go to the gettext::Creating::Header Entry:: by visiting the
-``gettext'' node from the main info menu, navigating to the ``Creating''
-node, and following that to the ``Header Entry'' node.
+“gettext” node from the main info menu, navigating to the “Creating”
+node, and following that to the “Header Entry” node.
<P>
A stand-alone info browser, independent of Emacs, is also available on many
systems. Thus, the <TT>gettext</TT> info page can also be accessed by typing
-``info gettext'' in a terminal. <TT>xinfo</TT> is an X application serving as an
-info browser, so that if it is installed, typing ``xinfo gettext'' from the
+“info gettext” in a terminal. <TT>xinfo</TT> is an X application serving as an
+info browser, so that if it is installed, typing “xinfo gettext” from the
command line will open a new browser window with the <TT>gettext</TT> info page.
<P>
Emacs PO mode</A>
</H2>
Emacs should automatically enter po-mode when you load a .po file, as
-indicated by ``PO'' in the modeline at the bottom. The window is made
+indicated by “PO” in the modeline at the bottom. The window is made
read-only, so that you can edit the .po file only through special commands. A
description of Emacs po-mode can be found under the gettext::Basics info node,
-or type `h' or `?' in a po-mode window for a list of available commands. While
+or type ‘h’ or ‘?’ in a po-mode window for a list of available commands. While
I find Emacs po-mode quite restrictive, this is probably due to unfamiliarity
with it. Its main advantage is that it imposes rigid conformance to the PO
file format, and checks the file format when closing the .po file
+2012-01-26 Bruno Haible <bruno@clisp.org>
+
+ Modernize quoting.
+ * hostname.c (usage): Quote 'like this', not `like this', as per the
+ recent change to the GNU coding standards.
+ * msgattrib.c (usage): Likewise.
+ * msgcat.c (usage): Likewise.
+ * msgcmp.c (usage): Likewise.
+ * msgcomm.c (usage): Likewise.
+ * msgconv.c (usage): Likewise.
+ * msgen.c (usage): Likewise.
+ * msgexec.c (usage): Likewise.
+ * msgfilter.c (usage): Likewise.
+ * msgfmt.c (usage, msgfmt_set_domain, msgfmt_frob_new_message):
+ Likewise.
+ * msggrep.c (usage): Likewise.
+ * msginit.c (usage): Likewise.
+ * msgl-cat.c (catenate_msgdomain_list): Likewise.
+ * msgl-check.c (check_pair, check_header_entry): Likewise.
+ * msgmerge.c (usage): Likewise.
+ * msgunfmt.c (usage): Likewise.
+ * msguniq.c (usage): Likewise.
+ * recode-sr-latin.c (usage): Likewise.
+ * urlget.c (usage): Likewise.
+ * write-po.c (wrap): Likewise.
+ * xgettext.c (main, usage, remember_a_message, construct_header,
+ language_to_extractor): Likewise.
+ * po-gram-gen.y: Likewise.
+ * po-error.h: Likewise.
+ * po-lex.h: Likewise.
+ * read-catalog-abstract.h: Likewise.
+ * x-c.c: Likewise.
+
2011-10-04 Bruno Haible <bruno@clisp.org>
xgettext for Scheme: Understand guile 2.0 comment syntax, part 2.
/* Display hostname in various forms.
- Copyright (C) 2001-2003, 2006-2007 Free Software Foundation, Inc.
+ Copyright (C) 2001-2003, 2006-2007, 2012 Free Software Foundation, Inc.
Written by Bruno Haible <haible@clisp.cons.org>, 2001.
This program is free software: you can redistribute it and/or modify
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
/* Manipulates attributes of messages in translation catalogs.
- Copyright (C) 2001-2007, 2009-2010 Free Software Foundation, Inc.
+ Copyright (C) 2001-2007, 2009-2010, 2012 Free Software Foundation, Inc.
Written by Bruno Haible <haible@clisp.cons.org>, 2001.
This program is free software: you can redistribute it and/or modify
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
/* Concatenates several translation catalogs.
- Copyright (C) 2001-2007, 2009-2011 Free Software Foundation, Inc.
+ Copyright (C) 2001-2007, 2009-2012 Free Software Foundation, Inc.
Written by Bruno Haible <haible@clisp.cons.org>, 2001.
This program is free software: you can redistribute it and/or modify
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
/* GNU gettext - internationalization aids
- Copyright (C) 1995-1998, 2000-2010 Free Software Foundation, Inc.
+ Copyright (C) 1995-1998, 2000-2010, 2012 Free Software Foundation, Inc.
This file was written by Peter Miller <millerp@canb.auug.org.au>
This program is free software: you can redistribute it and/or modify
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
/* GNU gettext - internationalization aids
- Copyright (C) 1997-1998, 2000-2007, 2009-2011 Free Software Foundation, Inc.
+ Copyright (C) 1997-1998, 2000-2007, 2009-2012 Free Software Foundation, Inc.
This file was written by Peter Miller <millerp@canb.auug.org.au>
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
printf (_("\
-F, --sort-by-file sort output by file location\n"));
printf (_("\
- --omit-header don't write header with `msgid \"\"' entry\n"));
+ --omit-header don't write header with 'msgid \"\"' entry\n"));
printf ("\n");
printf (_("\
Informative output:\n"));
/* Converts a translation catalog to a different character encoding.
- Copyright (C) 2001-2007, 2009-2010 Free Software Foundation, Inc.
+ Copyright (C) 2001-2007, 2009-2010, 2012 Free Software Foundation, Inc.
Written by Bruno Haible <haible@clisp.cons.org>, 2001.
This program is free software: you can redistribute it and/or modify
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
/* Creates an English translation catalog.
- Copyright (C) 2001-2007, 2009-2010 Free Software Foundation, Inc.
+ Copyright (C) 2001-2007, 2009-2010, 2012 Free Software Foundation, Inc.
Written by Bruno Haible <haible@clisp.cons.org>, 2001.
This program is free software: you can redistribute it and/or modify
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
/* Pass translations to a subprocess.
- Copyright (C) 2001-2011 Free Software Foundation, Inc.
+ Copyright (C) 2001-2012 Free Software Foundation, Inc.
Written by Bruno Haible <haible@clisp.cons.org>, 2001.
This program is free software: you can redistribute it and/or modify
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
/* Edit translations using a subprocess.
- Copyright (C) 2001-2010 Free Software Foundation, Inc.
+ Copyright (C) 2001-2010, 2012 Free Software Foundation, Inc.
Written by Bruno Haible <haible@clisp.cons.org>, 2001.
This program is free software: you can redistribute it and/or modify
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
/* Converts Uniforum style .po files to binary .mo files
- Copyright (C) 1995-1998, 2000-2007, 2009-2010 Free Software Foundation, Inc.
+ Copyright (C) 1995-1998, 2000-2007, 2009-2010, 2012 Free Software Foundation, Inc.
Written by Ulrich Drepper <drepper@gnu.ai.mit.edu>, April 1995.
This program is free software: you can redistribute it and/or modify
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
static void
msgfmt_set_domain (default_catalog_reader_ty *this, char *name)
{
- /* If no output file was given, we change it with each `domain'
+ /* If no output file was given, we change it with each 'domain'
directive. */
if (!java_mode && !csharp_mode && !csharp_resources_mode && !tcl_mode
&& !qt_mode && output_file_name == NULL)
{
if (check_domain)
po_gram_error_at_line (&gram_pos,
- _("`domain %s' directive ignored"), name);
+ _("'domain %s' directive ignored"), name);
/* NAME was allocated in po-gram-gen.y but is not used anywhere. */
free (name);
error_with_progname = false;
error_at_line (0, 0, mp->pos.file_name, mp->pos.line_number,
(mp->msgstr[0] == '\0'
- ? _("empty `msgstr' entry ignored")
- : _("fuzzy `msgstr' entry ignored")));
+ ? _("empty 'msgstr' entry ignored")
+ : _("fuzzy 'msgstr' entry ignored")));
error_with_progname = true;
}
}
-/* Test for `#, fuzzy' comments and warn. */
+/* Test for '#, fuzzy' comments and warn. */
static void
msgfmt_comment_special (abstract_catalog_reader_ty *that, const char *s)
{
/* Extract some translations of a translation catalog.
- Copyright (C) 2001-2007, 2009-2010 Free Software Foundation, Inc.
+ Copyright (C) 2001-2007, 2009-2010, 2012 Free Software Foundation, Inc.
Written by Bruno Haible <haible@clisp.cons.org>, 2001.
This program is free software: you can redistribute it and/or modify
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
/* Initializes a new PO file.
- Copyright (C) 2001-2011 Free Software Foundation, Inc.
+ Copyright (C) 2001-2012 Free Software Foundation, Inc.
Written by Bruno Haible <haible@clisp.cons.org>, 2001.
This program is free software: you can redistribute it and/or modify
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
/* Message list concatenation and duplicate handling.
- Copyright (C) 2001-2003, 2005-2008 Free Software Foundation, Inc.
+ Copyright (C) 2001-2003, 2005-2008, 2012 Free Software Foundation, Inc.
Written by Bruno Haible <haible@clisp.cons.org>, 2001.
This program is free software: you can redistribute it and/or modify
{
if (k == 0)
error (EXIT_FAILURE, 0, _("\
-input file `%s' doesn't contain a header entry with a charset specification"),
+input file '%s' doesn't contain a header entry with a charset specification"),
files[n]);
else
error (EXIT_FAILURE, 0, _("\
-domain \"%s\" in input file `%s' doesn't contain a header entry with a charset specification"),
+domain \"%s\" in input file '%s' doesn't contain a header entry with a charset specification"),
mdlp->item[k]->domain, files[n]);
}
}
/* Checking of messages in PO files.
- Copyright (C) 1995-1998, 2000-2008, 2010-2011 Free Software Foundation, Inc.
+ Copyright (C) 1995-1998, 2000-2008, 2010-2012 Free Software Foundation, Inc.
Written by Ulrich Drepper <drepper@gnu.ai.mit.edu>, April 1995.
This program is free software: you can redistribute it and/or modify
po_xerror (PO_SEVERITY_ERROR,
mp, msgid_pos->file_name, msgid_pos->line_number,
(size_t)(-1), false, _("\
-`msgid' and `msgid_plural' entries do not both begin with '\\n'"));
+'msgid' and 'msgid_plural' entries do not both begin with '\\n'"));
seen_errors++;
}
for (p = msgstr, j = 0; p < msgstr + msgstr_len; p += strlen (p) + 1, j++)
{
char *msg =
xasprintf (_("\
-`msgid' and `msgstr[%u]' entries do not both begin with '\\n'"), j);
+'msgid' and 'msgstr[%u]' entries do not both begin with '\\n'"), j);
po_xerror (PO_SEVERITY_ERROR,
mp, msgid_pos->file_name, msgid_pos->line_number,
(size_t)(-1), false, msg);
po_xerror (PO_SEVERITY_ERROR,
mp, msgid_pos->file_name, msgid_pos->line_number,
(size_t)(-1), false, _("\
-`msgid' and `msgstr' entries do not both begin with '\\n'"));
+'msgid' and 'msgstr' entries do not both begin with '\\n'"));
seen_errors++;
}
}
po_xerror (PO_SEVERITY_ERROR,
mp, msgid_pos->file_name, msgid_pos->line_number,
(size_t)(-1), false, _("\
-`msgid' and `msgid_plural' entries do not both end with '\\n'"));
+'msgid' and 'msgid_plural' entries do not both end with '\\n'"));
seen_errors++;
}
for (p = msgstr, j = 0; p < msgstr + msgstr_len; p += strlen (p) + 1, j++)
{
char *msg =
xasprintf (_("\
-`msgid' and `msgstr[%u]' entries do not both end with '\\n'"), j);
+'msgid' and 'msgstr[%u]' entries do not both end with '\\n'"), j);
po_xerror (PO_SEVERITY_ERROR,
mp, msgid_pos->file_name, msgid_pos->line_number,
(size_t)(-1), false, msg);
po_xerror (PO_SEVERITY_ERROR,
mp, msgid_pos->file_name, msgid_pos->line_number,
(size_t)(-1), false, _("\
-`msgid' and `msgstr' entries do not both end with '\\n'"));
+'msgid' and 'msgstr' entries do not both end with '\\n'"));
seen_errors++;
}
}
if (endp == NULL)
{
char *msg =
- xasprintf (_("header field `%s' missing in header\n"),
+ xasprintf (_("header field '%s' missing in header\n"),
required_fields[cnt]);
po_xerror (severity, mp, NULL, 0, 0, true, msg);
free (msg);
{
char *msg =
xasprintf (_("\
-header field `%s' should start at beginning of line\n"),
+header field '%s' should start at beginning of line\n"),
required_fields[cnt]);
po_xerror (severity, mp, NULL, 0, 0, true, msg);
free (msg);
int severity =
(initial < nrequiredfields ? PO_SEVERITY_ERROR : PO_SEVERITY_WARNING);
char *msg =
- xasprintf (_("header field `%s' still has the initial default value\n"),
+ xasprintf (_("header field '%s' still has the initial default value\n"),
required_fields[initial]);
po_xerror (severity, mp, NULL, 0, 0, true, msg);
free (msg);
/* GNU gettext - internationalization aids
- Copyright (C) 1995-1998, 2000-2010 Free Software Foundation, Inc.
+ Copyright (C) 1995-1998, 2000-2010, 2012 Free Software Foundation, Inc.
This file was written by Peter Miller <millerp@canb.auug.org.au>
This program is free software: you can redistribute it and/or modify
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
existing, nil numbered if numbered backups exist, simple otherwise\n\
simple, never always make simple backups\n"));
printf (_("\
-The backup suffix is `~', unless set with --suffix or the SIMPLE_BACKUP_SUFFIX\n\
+The backup suffix is '~', unless set with --suffix or the SIMPLE_BACKUP_SUFFIX\n\
environment variable.\n\
"));
printf ("\n");
/* msgunfmt - converts binary .mo files to Uniforum style .po files
- Copyright (C) 1995-1998, 2000-2007, 2009-2010 Free Software Foundation, Inc.
+ Copyright (C) 1995-1998, 2000-2007, 2009-2010, 2012 Free Software Foundation, Inc.
Written by Ulrich Drepper <drepper@gnu.ai.mit.edu>, April 1995.
This program is free software: you can redistribute it and/or modify
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
/* Remove, select or merge duplicate translations.
- Copyright (C) 2001-2007, 2009-2010 Free Software Foundation, Inc.
+ Copyright (C) 2001-2007, 2009-2010, 2012 Free Software Foundation, Inc.
Written by Bruno Haible <haible@clisp.cons.org>, 2001.
This program is free software: you can redistribute it and/or modify
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
/* Error handling during reading and writing of PO files.
- Copyright (C) 2004, 2006 Free Software Foundation, Inc.
+ Copyright (C) 2004, 2006, 2012 Free Software Foundation, Inc.
Written by Bruno Haible <bruno@clisp.org>, 2004.
This program is free software: you can redistribute it and/or modify
# if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 5) || __STRICT_ANSI__
# define __attribute__(Spec) /* empty */
# endif
-/* The __-protected variants of `format' and `printf' attributes
+/* The __-protected variants of 'format' and 'printf' attributes
are accepted by gcc versions 2.6.4 (effectively 2.7) and later. */
# if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 7)
# define __format__ format
/* GNU gettext - internationalization aids
- Copyright (C) 1995-1996, 1998, 2000-2001, 2003, 2005-2006 Free Software Foundation, Inc.
+ Copyright (C) 1995-1996, 1998, 2000-2001, 2003, 2005-2006, 2012 Free Software Foundation, Inc.
This file was written by Peter Miller <pmiller@agso.gov.au>
{
check_obsolete ($1, $2);
check_obsolete ($1, $3);
- po_gram_error_at_line (&$1.pos, _("missing `msgstr[]' section"));
+ po_gram_error_at_line (&$1.pos, _("missing 'msgstr[]' section"));
free_message_intro ($1);
string_list_destroy (&$2.stringlist);
free ($3.string);
{
check_obsolete ($1, $2);
check_obsolete ($1, $3);
- po_gram_error_at_line (&$1.pos, _("missing `msgid_plural' section"));
+ po_gram_error_at_line (&$1.pos, _("missing 'msgid_plural' section"));
free_message_intro ($1);
string_list_destroy (&$2.stringlist);
free ($3.rhs.msgstr);
| message_intro string_list
{
check_obsolete ($1, $2);
- po_gram_error_at_line (&$1.pos, _("missing `msgstr' section"));
+ po_gram_error_at_line (&$1.pos, _("missing 'msgstr' section"));
free_message_intro ($1);
string_list_destroy (&$2.stringlist);
}
/* GNU gettext - internationalization aids
- Copyright (C) 1995-1998, 2000-2006 Free Software Foundation, Inc.
+ Copyright (C) 1995-1998, 2000-2006, 2012 Free Software Foundation, Inc.
This file was written by Peter Miller <millerp@canb.auug.org.au>
# if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 5) || __STRICT_ANSI__
# define __attribute__(Spec) /* empty */
# endif
-/* The __-protected variants of `format' and `printf' attributes
+/* The __-protected variants of 'format' and 'printf' attributes
are accepted by gcc versions 2.6.4 (effectively 2.7) and later. */
# if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 7)
# define __format__ format
/* Reading PO files, abstract class.
- Copyright (C) 1995-1996, 1998, 2000-2003, 2005-2006, 2008-2009 Free Software Foundation, Inc.
+ Copyright (C) 1995-1996, 1998, 2000-2003, 2005-2006, 2008-2009, 2012 Free Software Foundation, Inc.
This file was written by Peter Miller <millerp@canb.auug.org.au>
/* This next structure defines the base class passed to the methods.
Derived methods will often need to cast their first argument before
- using it (this corresponds to the implicit ``this'' argument in C++).
+ using it (this corresponds to the implicit 'this' argument in C++).
When declaring derived classes, use the ABSTRACT_CATALOG_READER_TY define
at the start of the structure, to declare inherited instance variables,
/* Recode Serbian text from Cyrillic to Latin script.
- Copyright (C) 2006-2007, 2010 Free Software Foundation, Inc.
+ Copyright (C) 2006-2007, 2010, 2012 Free Software Foundation, Inc.
Written by Bruno Haible <bruno@clisp.org>, 2006.
This program is free software: you can redistribute it and/or modify
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
/* Get the contents of an URL.
- Copyright (C) 2001-2003, 2005-2010 Free Software Foundation, Inc.
+ Copyright (C) 2001-2003, 2005-2010, 2012 Free Software Foundation, Inc.
Written by Bruno Haible <haible@clisp.cons.org>, 2001.
This program is free software: you can redistribute it and/or modify
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
/* GNU gettext - internationalization aids
- Copyright (C) 1995-1998, 2000-2010 Free Software Foundation, Inc.
+ Copyright (C) 1995-1998, 2000-2010, 2012 Free Software Foundation, Inc.
This file was written by Peter Miller <millerp@canb.auug.org.au>
{
char *error_message =
xasprintf (_("\
-internationalized messages should not contain the `\\%c' escape sequence"),
+internationalized messages should not contain the '\\%c' escape sequence"),
c);
po_xerror (PO_SEVERITY_WARNING, mp, NULL, 0, 0, false,
error_message);
/* xgettext C/C++/ObjectiveC backend.
- Copyright (C) 1995-1998, 2000-2009 Free Software Foundation, Inc.
+ Copyright (C) 1995-1998, 2000-2009, 2012 Free Software Foundation, Inc.
This file was written by Peter Miller <millerp@canb.auug.org.au>
between the user requesting a newline in the string (e.g. using
"\n" or "\012") from the user failing to terminate the string or
character constant. The ANSI C standard says: 3.1.3.4 Character
- Constants contain ``any character except single quote, backslash or
- newline; or an escape sequence'' and 3.1.4 String Literals contain
- ``any character except double quote, backslash or newline; or an
- escape sequence''.
+ Constants contain "any character except single quote, backslash or
+ newline; or an escape sequence" and 3.1.4 String Literals contain
+ "any character except double quote, backslash or newline; or an
+ escape sequence".
Most compilers give a fatal error in this case, however gcc is
stupidly silent, even though this is a very common typo. OK, so
- gcc --pedantic will tell me, but that gripes about too much other
- stuff. Could I have a ``gcc -Wnewline-in-string'' option, or
- better yet a ``gcc -fno-newline-in-string'' option, please? Gcc is
+ "gcc --pedantic" will tell me, but that gripes about too much other
+ stuff. Could I have a "gcc -Wnewline-in-string" option, or
+ better yet a "gcc -fno-newline-in-string" option, please? Gcc is
also inconsistent between string literals and character constants:
you may not embed newlines in character constants; try it, you get
a useful diagnostic. --PMiller */
/* Extracts strings from C source file to Uniforum style .po file.
- Copyright (C) 1995-1998, 2000-2011 Free Software Foundation, Inc.
+ Copyright (C) 1995-1998, 2000-2012 Free Software Foundation, Inc.
Written by Ulrich Drepper <drepper@gnu.ai.mit.edu>, April 1995.
This program is free software: you can redistribute it and/or modify
if (language == NULL)
{
error (0, 0, _("\
-warning: file `%s' extension `%s' is unknown; will try C"), filename, extension);
+warning: file '%s' extension '%s' is unknown; will try C"), filename, extension);
language = "C";
}
this_file_extractor = language_to_extractor (language);
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
printf (_("\
-F, --sort-by-file sort output by file location\n"));
printf (_("\
- --omit-header don't write header with `msgid \"\"' entry\n"));
+ --omit-header don't write header with 'msgid \"\"' entry\n"));
printf (_("\
--copyright-holder=STRING set copyright holder in output\n"));
printf (_("\
CONVERT_STRING (s, lc_comment);
/* To reduce the possibility of unwanted matches we do a two
- step match: the line must contain `xgettext:' and one of
+ step match: the line must contain 'xgettext:' and one of
the possible format description strings. */
if ((t = c_strstr (s, "xgettext:")) != NULL)
{
multiline_warning (xasprintf (_("warning: ")),
xstrdup (_("\
The option --msgid-bugs-address was not specified.\n\
-If you are using a `Makevars' file, please specify\n\
+If you are using a 'Makevars' file, please specify\n\
the MSGID_BUGS_ADDRESS variable there; otherwise please\n\
specify an --msgid-bugs-address command line option.\n\
")));
return result;
}
- error (EXIT_FAILURE, 0, _("language `%s' unknown"), name);
+ error (EXIT_FAILURE, 0, _("language '%s' unknown"), name);
/* NOTREACHED */
{
extractor_ty result = { NULL, NULL, NULL, NULL };
+2012-01-26 Bruno Haible <bruno@clisp.org>
+
+ Modernize quoting.
+ * tstgettext.c (usage): Quote 'like this', not `like this', as per the
+ recent change to the GNU coding standards.
+ * tstngettext.c (usage): Likewise.
+
2012-01-15 Bruno Haible <bruno@clisp.org>
Avoid test failure on Solaris 11.
/* gettext - retrieve text string from message catalog and print it.
- Copyright (C) 1995-1997, 2000-2007 Free Software Foundation, Inc.
+ Copyright (C) 1995-1997, 2000-2007, 2012 Free Software Foundation, Inc.
Written by Ulrich Drepper <drepper@gnu.ai.mit.edu>, May 1995.
This program is free software: you can redistribute it and/or modify
#define _(str) gettext (str)
/* If true, add newline after last string. This makes only sense in
- the `echo' emulation mode. */
+ the 'echo' emulation mode. */
static bool add_newline;
/* If true, expand escape sequences in strings before looking in the
usage (EXIT_SUCCESS);
/* We have two major modes: use following Uniforum spec and as
- internationalized `echo' program. */
+ internationalized 'echo' program. */
if (!do_shell)
{
/* We have to write a single strings translation to stdout. */
if (domaindir != NULL && domaindir[0] != '\0')
bindtextdomain (domain, domaindir);
- /* We have to simulate `echo'. All arguments are strings. */
+ /* We have to simulate 'echo'. All arguments are strings. */
do
{
msgid = argv[optind++];
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
environment variable TEXTDOMAIN. If the message catalog is not found in the\n\
regular directory, another location can be specified with the environment\n\
variable TEXTDOMAINDIR.\n\
-When used with the -s option the program behaves like the `echo' command.\n\
+When used with the -s option the program behaves like the 'echo' command.\n\
But it does not simply copy its arguments to stdout. Instead those messages\n\
found in the selected catalog are translated.\n\
Standard search directory: %s\n"),
/* ngettext - retrieve plural form strings from message catalog and print them.
- Copyright (C) 1995-1997, 2000-2007 Free Software Foundation, Inc.
+ Copyright (C) 1995-1997, 2000-2007, 2012 Free Software Foundation, Inc.
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
usage (int status)
{
if (status != EXIT_SUCCESS)
- fprintf (stderr, _("Try `%s --help' for more information.\n"),
+ fprintf (stderr, _("Try '%s --help' for more information.\n"),
program_name);
else
{
+2012-01-26 Bruno Haible <bruno@clisp.org>
+
+ Modernize quoting.
+ * lib/backupfile.c: Quote 'like this', not `like this', as per the
+ recent change to the GNU coding standards.
+ * lib/basename.c: Likewise.
+ * lib/closeout.c: Likewise.
+ * lib/xmalloc.c: Likewise.
+
2012-01-06 Bruno Haible <bruno@clisp.org>
Update after gnulib changed.
/* backupfile.c -- make Emacs style backup file names
- Copyright (C) 1990-1999, 2000-2003, 2005-2006 Free Software Foundation, Inc.
+ Copyright (C) 1990-1999, 2000-2003, 2005-2006, 2012 Free Software Foundation, Inc.
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
- It's typically faster.
Posix 1003.2-1992 section 2.5.2.1 page 50 lines 1556-1558 says that
only '0' through '9' are digits. Prefer ISDIGIT to isdigit unless
- it's important to use the locale's definition of `digit' even when the
+ it's important to use the locale's definition of 'digit' even when the
host does not conform to Posix. */
#define ISDIGIT(c) ((unsigned) (c) - '0' <= 9)
char *s;
const char *suffix = simple_backup_suffix;
- /* Allow room for simple or `.~N~' backups. */
+ /* Allow room for simple or '.~N~' backups. */
backup_suffix_size_max = strlen (simple_backup_suffix) + 1;
if (HAVE_DIR && backup_suffix_size_max < numbered_suffix_size_max)
backup_suffix_size_max = numbered_suffix_size_max;
/* Return the name-within-directory of a file name.
- Copyright (C) 1996-1999, 2000-2002, 2004, 2006, 2010 Free Software Foundation, Inc.
+ Copyright (C) 1996-1999, 2000-2002, 2004, 2006, 2010, 2012 Free Software Foundation, Inc.
NOTE: The canonical source of this file is maintained with the GNU C Library.
Bugs can be reported to bug-glibc@gnu.org.
#endif
#ifndef _LIBC
-/* We cannot generally use the name `basename' since XPG defines an unusable
+/* We cannot generally use the name 'basename' since XPG defines an unusable
variant of the function but we cannot use it. */
# undef basename
# define basename gnu_basename
#endif
-/* In general, we can't use the builtin `basename' function if available,
+/* In general, we can't use the builtin 'basename' function if available,
since it has different meanings in different environments.
- In some environments the builtin `basename' modifies its argument.
- If NAME is all slashes, be sure to return `/'. */
+ In some environments the builtin 'basename' modifies its argument.
+ If NAME is all slashes, be sure to return '/'. */
char *
basename (char const *name)
all_slashes = 0;
}
- /* If NAME is all slashes, arrange to return `/'. */
+ /* If NAME is all slashes, arrange to return '/'. */
if (*base == '\0' && ISSLASH (*name) && all_slashes)
--base;
/* closeout.c - close standard output and standard error
- Copyright (C) 1998-2007 Free Software Foundation, Inc.
+ Copyright (C) 1998-2007, 2012 Free Software Foundation, Inc.
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
Likewise for standard error.
It's important to detect such failures and exit nonzero because many
- tools (most notably `make' and other build-management systems) depend
+ tools (most notably 'make' and other build-management systems) depend
on being able to detect failure in other tools via their exit status. */
/* Close standard output and standard error, exiting with status EXIT_FAILURE
/* xmalloc.c -- malloc with out of memory checking
- Copyright (C) 1990-1996, 2000-2003, 2005-2007 Free Software Foundation, Inc.
+ Copyright (C) 1990-1996, 2000-2003, 2005-2007, 2012 Free Software Foundation, Inc.
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
xalloc_die ()
{
error (xmalloc_exit_failure, 0, _("memory exhausted"));
- /* The `noreturn' cannot be given to error, since it may return if
+ /* _Noreturn cannot be given to error, since it may return if
its first argument is 0. To help compilers understand the
xalloc_die does terminate, call exit. */
exit (EXIT_FAILURE);
projects / thirdparty / gettext.git / commitdiff
