Mail Archives: cygwin/2008/11/15/17:54:45
gettext is the GNU package which provides 'national language support'
for other programs. It includes a number of utility programs.
These should be upgraded together with the libiconv packages.
libiconv-1.12-1
libiconv2-1.12-1
libcharset1-1.12-1
gettext-0.17-1
gettext-devel-0.17-1
libintl8-0.17-1
libgettextpo0-0.17-1
libasprintf0-0.17-1
CHANGES:
* Routine update to 0.17 upstream release
* Removed all references to 'relocatable' from .cygport
so that -src package can be (re)built using stock
cygport-0.4.2.
* Detailed changes listed below.
TESTSUITE RESULTS:
gettext-tools
===================================================================
All 300 tests passed (27 tests were not run)
gettext-tools/gnulib-tests
===================================================================
All 47 tests passed
(2 tests were not run)
ASIDE: all tests fail when gettext is compiled with
--enable-relocation (because the makefile in the gnulib-tests
directory doesn;t have the appropriate hooks to support building
relocatable executables -- but the config.h and DEFS are such
that the source code "expects" those hooks to be present. [1]
. However, the official cygwin package i /not/ compiled using
that flag.
[1] gcc -std=gnu99 -DHAVE_CONFIG_H <stripped lots of -I paths> -O2 -pipe
-MT test-argmatch.o -MD -MP -MF .deps/test-argmatch.Tpo -c -o
test-argmatch.o /path/to/test-argmatch.c
/path/to/test-argmatch.c: In function `main':
/path/to/test-argmatch.c:68: error: `INSTALLDIR' undeclared (first use
in this function)
gettext-runtime
===================================================================
All 1 tests passed
gettext-rpath
===================================================================
All 30 tests passed
ASIDE: this is a little deceptive. If gettext-0.15 is installed when
gettext-0.17 is built and tested, then all rpath tests pass.
However, if gettext-0.17 is installed, and gettext-0.17 is
(re)built and (re)tested, then all tests involving DLLs FAIL!
I haven't figured out why that is, yet; somehow the $PATH is
not getting set when the test executables are run. [1]
This could simply be related to the fact that I re-autotooled
gettext to use libtool-2.2 and autoconf-2.63 ... and maybe
gettext's .m4 files aren't /quite/ ready for that yet. But
that's just a guess.
[1] /path/toutoconf-lib-link/tests/tstdir/rp3bbb-build4/usez.exe: error
while loading shared libraries: cygrpathx-0.dll: cannot open shared
object file: No such file or directory
(You only get this diagnostic when running under cygwin-1.7. On
cygwin-1.5 the tests fail, but no error message. Except on Vista,
where you get a popup window, six times. Ugh.)
It seems that (a) there is some "leakage" from the installed
.m4 files into the test environment, and (b) there something
broken in the gettext-0.17 config.rpath. I'll keep working
the issue, but we've waited long enough for a modern gettext.
--
Chuck
====================================================================
To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page. This downloads setup.exe to your
system. Then, run setup and answer all of the questions.
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there. It will be in the format:
cygwin-announce-unsubscribe-you=3D3Dyourdomain DOT com AT cygwin DOT com
If you need more information on unsubscribing, start reading here:
http://sources.redhat.com/lists.html#unsubscribe-simple
Please read *all* of the information on unsubscribing that is available
starting at this URL.
============================================================
Version 0.17 - November 2007
* License: The gettext related programs and tools are now
licensed under the GPL version 3, instead of the GPL
version 2. The libintl library continues to be licensed
under LGPL.
* PO file format: The Project-Id-Version field in the header
entry may now already be filled in the POT file. In this
case, the translators don't need to fill it in. xgettext
has new options --package-name and --package-version that
allow to specify the package name and version from a
Makefile.
* Colorized PO files: The msgcat program has new options
--color and --style that produce a colorized PO file
output, where keywords, strings, comments, or format
directives can be highlighted. See the documentation
section "Highlighting parts of PO files" for more info.
* gettextize now has a --po-dir option that allows several
PO directories to be updated all together.
* Programming languages support:
- Contexts (msgctxt) are now also supported for Java and C#.
- C# with Qt: The support for Qt format strings has been
updated for Qt 4.
- C++ with KDE: xgettext has a new option --kde that
triggers the recognition and marking of KDE 4 format
strings.
* Autoconf macros:
- A new macro AM_XGETTEXT_OPTION can be used as an
alternative to modifying po/Makevars.
* libgettextpo library:
- New functions are available for querying the list of
supported format types.
- The functions po_message_comments and
po_message_extracted_comments return a multiline string
where each line no longer starts with a redundant space.
The leading space in every comment line is now stripped
while reading the PO file. - Conversely, when you pass a
multiline string to the function po_message_set_comments
or po_message_set_extracted_comments, you normally don't
pass a space at the beginning of each line, because such
spaces are no longer trimmed during output.
* Documentation:
- The "Users" chapter has been completely rewritten.
- New section "Highlighting parts of PO files".
- A complete example showing the use of GNU gettext in
Java with the Qt/Jambi GUI toolkit has been added.
============================================================
Version 0.16.1 - November 2006
* Bug fix in the gettext.m4 autoconf macros.
============================================================
Version 0.16 - October 2006
* Interoperability with automake-1.10.
* msgmerge has a new option --previous that has the effect
of saving the previous msgid of message when making them
fuzzy. These previous msgids are stored in the resulting
PO file, using a pseudo-comment syntax like this:
#, fuzzy
#| msgid "too many arguments"
msgid "too few arguments"
msgstr "trop d'arguments"
The translator then only needs to compare the previous
and the current msgid ("too many arguments" and "too few
arguments"), and infer which parts of the translation she
needs to change.
msgattrib has a new option --clear-previous that removes
these #| lines.
* msgmerge is faster now on CPUs with multiple execution
units, if compiled with GCC 4.2 or newer.
* msgcmp now ignores fuzzy and untranslated messages in the
PO file. Previously it considered fuzzy and untranslated
messages the same way as translated messages, which was
hardly useful. The previous behaviour can be obtained
through the options --use-fuzzy --use-untranslated.
* gettextize, when invoked without --intl option, now
installs only the .m4 files that are needed: gettext.m4,
iconv.m4, lib-ld.m4, lib-link.m4, lib-prefix.m4, nls.m4,
po.m4, progtest.m4.
* gettextize no longer creates symbolic links by default; it
makes file copies instead. The option --copy is removed.
You can get back the flawed symlinking behaviour by
specifying the --symlink option.
* Autoconf macros:
- The gettext autoconf macros now require autoconf 2.52 or
newer and GNU m4 1.4.5 or newer.
- A new autoconf macro AM_GNU_GETTEXT_INTL_SUBDIR is
added. It allows to specify the presence of an intl/
subdirectory outside the AM_GNU_GETTEXT invocation.
- A new autoconf macro AM_GNU_GETTEXT_NEED is added. It
allows to specify the requirements relating to the GNU
gettext implementation outside the AM_GNU_GETTEXT
invocation.
* The libgettextpo library no longer exports symbols that
could clash with symbols of the application that uses it.
* Vastly improved French translations. Thanks to Christophe
Combelles.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -