Imported Upstream version 0.18.3.2

[platform/upstream/gettext.git] / gettext-tools / doc / msgfmt.texi

diff --git a/gettext-tools/doc/msgfmt.texi b/gettext-tools/doc/msgfmt.texi
index 2067f93..2a0dd6f 100644 (file)
--- a/gettext-tools/doc/msgfmt.texi
+++ b/gettext-tools/doc/msgfmt.texi
@@ -18,7 +18,7 @@ translation description.
 @opindex -D@r{, @code{msgfmt} option}
 @opindex --directory@r{, @code{msgfmt} option}
 Add @var{directory} to the list of directories.  Source files are
-searched relative to this list of directories.  The resulting @file{.po}
+searched relative to this list of directories.  The resulting binary
 file will be written relative to the current directory, though.
 
 @end table
@@ -265,6 +265,19 @@ Align strings to @var{number} bytes (default: 1).
 @c Currently the README mentions that this constant could be changed by
 @c the installer by changing the value in config.h.  Should this go away?
 
+@item --endianness=@var{byteorder}
+@opindex --endianness@r{, @code{msgfmt} option}
+Write out 32-bit numbers in the given byte order.  The possible values are
+@code{big} and @code{little}.  The default depends on the platform, namely
+on the endianness of the CPU.
+
+MO files of any endianness can be used on any platform.  When a MO file has
+an endianness other than the platform's one, the 32-bit numbers from the MO
+file are swapped at runtime.  The performance impact is negligible.
+
+This option can be useful to produce MO files that are independent of the
+platform.
+
 @item --no-hash
 @opindex --no-hash@r{, @code{msgfmt} option}
 Don't include a hash table in the binary file.  Lookup will be more expensive