Changes:
* output.c (hvpos): recover the old code in hvpos() for japanese
because the changed code leads to incorrect result in some cases.
other cases than japanese are not affected.
* writet1.c (t1_check_unusual_charstring): new fn.
(t1_subset_charstrings): call it. This resolves a bug reported by
Knuth when there is a newline between the /CharStrings and the
following number (dict size).
The package behaves in a similar way as if you provided the
(non-existent) Japanese option to babel so that you can handle
Japanese language text in LaTeX documents. The package requires
a Japanese-enabled TeX system, such as pTeX or jTeX.
* Fix btree index corruption from insertions concurrent with vacuuming
* Recover from errors occurring during WAL replay of DROP TABLESPACE
* Fix transient zeroing of shared buffers during WAL replay
* Fix postmaster to attempt restart after a hot-standby crash
* Fix corner case in SSI transaction cleanup
* Update per-column permissions, not only per-table permissions, when changing
table owner
* Fix handling of data-modifying WITH subplans in READ COMMITTED rechecking
* Fix for "could not find plan for CTE" failures
* Fix unsupported node type error caused by COLLATE in an INSERT expression
* Avoid crashing when we have problems deleting table files post-commit
* Fix recently-introduced memory leak in processing of inet/cidr
* Fix GIN cost estimation to handle column IN (...) index conditions
* Fix I/O-conversion-related memory leaks in plpgsql
* Teach pg_upgrade to handle renaming of plpython's shared library (affecting
upgrades to 9.1)
2012-1-27 meld 1.5.3
====================
New features:
* Add simple animations for chunk actions to make it easier to follow the
result of insertion and deletion actions (Kai Willadsen)
* Show the currently displayed page area in the side bars (Kai Willadsen)
Fixes:
* Don't show links between chunks where one of the chunks is completely
off-screen, reducing visual clutter (Kai Willadsen)
* Syntax highlighting will now assume that all files in a comparison are
of the same type if we can't determine otherwise (Kai Willadsen)
* Some fixes to colour usage and legibility for dark themes, with more
theme fixes coming soon (Kai Willadsen)
* Remember active filters across sessions in directory and VC comparions
(Kai Willadsen)
* Guess which version control system a user is most likely to want to see,
in the event of multiple VCs in a single working copy (Kai Willadsen)
* Work with Subversion 1.7 (Kai Willadsen)
* Many sundry bug fixes (Aaron Schrab, Julian Taylor, Kai Willadsen)
Translation updates:
* Bruno Brouard (fr)
* Christian Kirbach (de)
* Daniel Mustieles (es)
* Fran Dieguez (gl)
* Gabriel Speckhahn (pt_BR)
* Jiro Matsuzawa (ja)
* Jorge González (es)
* Marcin Floryan (pl)
* Marek Černocký (cs)
* Mario Blättermann (de)
* Matej Urbančič (sl)
* Petr Kovar (cs)
* Piotr Drąg (pl)
* Takeshi AIHANA (ja)
* Yuri Myasoedov (ru)
New in 1.11.3:
* WARNING: Future backward-incompatibilities!
- The support for the "obscure" multilib feature has been deprecated,
and will be moved out of the automake core in the next major Automake
release (1.12).
- The support for ".log -> .html" conversion and the check-html and
recheck-html targets will be removed in the next major Automake
release (1.12).
- The obsolescent AM_WITH_REGEX macro has been deprecated (since the
GNU rx library has been decommissioned), and will be removed in the
next major Automake release (1.12).
- The `lzma' compression format for distribution archives has been
deprecated in favor of `xz' and `lzip', and will be removed in the
next major Automake release (1.12).
- The `--acdir' option of aclocal is deprecated, and will probably be
removed in the next major Automake release (1.12).
- The exact order in which the directories in the aclocal macro
search path are looked up is probably going to be changed in the
next Automake release (1.12).
- The Automake support for automatic de-ANSI-fication will be removed
in the next major Automake release (1.12).
- Starting from the next Automake release (1.12), warnings in the
`extra-portability' category will be enabled by `-Wall' (right now,
one has to use `-Wextra-portability' explicitly).
* Miscellaneous changes:
- Automake's own build system is more silent by default, making use of
the 'silent-rules' option.
- The master copy of the `gnupload' script is now maintained in gnulib,
not in automake.
- The `missing' script doesn't try to wrap calls to `tar' anymore.
- "make dist" doesn't wrap `tar' invocations with the `missing' script
anymore. Similarly, the obsolescent variable `$(AMTAR)' (which you
shouldn't be using BTW ;-) does not invoke the missing script anymore
to wrap tar, but simply invokes the `tar' program itself.
- "make dist" can now create lzip-compressed tarballs.
- In the Automake info documentation, the Top node and the nodes about
the invocation of the automake and aclocal programs have been renamed;
now, calling "info automake" will open the Top node, while calling
"info automake-invocation" and "info aclocal-invocation" will access
the nodes about the invocation of respectively automake and aclocal.
- Automake is now distributed as a gzip-compressed and an xz-compressed
tarball. Previously, bzip2 was used instead of xz.
- The last relics of Python 1.5 support have been removed from the
AM_PATH_PYTHON macro.
- For programs and libraries, automake now detects EXTRA_foo_DEPENDENCIES
and adds them to the normal list of dependencies, but without
overwriting the foo_DEPENDENCIES variable, which is normally computed
by automake.
Bugs fixed in 1.11.3:
* Bugs introduced by 1.11.2:
- Automake now correctly recognizes the prefix/primary combination
`pkglibexec_SCRIPTS' as valid.
- The parallel-tests harness doesn't trip anymore on sed implementations
with stricter limits on the length of input lines (problem seen at
least on Solaris 8).
* Long-standing bugs:
- The "deleted header file problem" for *.am files is avoided by stub
rules. This allows `make' to trigger a rerun of `automake' also if
some previously needed `.am' file has been removed.
- The `silent-rules' option now generates working makefiles even
for the uncommon `make' implementations that do not support the
nested-variables extension to POSIX 2008. For such `make'
implementations, whether a build is silent is determined at
configure time, and cannot be overridden at make time with
`make V=0' or `make V=1'.
- Vala support now works better in VPATH setups.
New in 1.11.2:
* Changes to aclocal:
- The `--acdir' option is deprecated. Now you should use the new options
`--automake-acdir' and `--system-acdir' instead.
- The `ACLOCAL_PATH' environment variable is now interpreted as a
colon-separated list of additional directories to search after the
automake internal acdir (by default ${prefix}/share/aclocal-APIVERSION)
and before the system acdir (by default ${prefix}/share/aclocal).
* Miscellaneous changes:
- The Automake support for automatic de-ANSI-fication has been
deprecated. It will probably be removed in the next major Automake
release (1.12).
- The `lzma' compression scheme and associated automake option `dist-lzma'
is obsoleted by `xz' and `dist-xz' due to upstream changes.
- You may adjust the compression options used in dist-xz and dist-bzip2.
The default is now merely -e for xz, but still -9 for bzip; you may
specify a different level via the XZ_OPT and BZIP2 envvars respectively.
E.g., "make dist-xz XZ_OPT=-7" or "make dist-bzip2 BZIP2=-5"
- The `compile' script now converts some options for MSVC for a better
user experience. Similarly, the new `ar-lib' script wraps Microsoft lib.
- The py-compile script now accepts empty arguments passed to the options
`--destdir' and `--basedir', and complains about unrecognized options.
Moreover, a non-option argument or a special `--' argument terminates
the list of options.
- A developer that needs to pass specific flags to configure at "make
distcheck" time can now, and indeed is advised to, do so by defining
the developer-reserved makefile variable AM_DISTCHECK_CONFIGURE_FLAGS,
instead of the old DISTCHECK_CONFIGURE_FLAGS.
The DISTCHECK_CONFIGURE_FLAGS variable should now be reserved for the
user; still, the old Makefile.am files that used to define it will
still continue to work as before.
- New macro AM_PROG_AR that looks for an archiver and wraps it in the new
'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
This new macro is required for LIBRARIES and LTLIBRARIES when automake
is run with -Wextra-portability and -Werror.
- When using DejaGnu-based testsuites, the user can extend the `site.exp'
file generated by automake-provided rules by defining the special make
variable `$(EXTRA_DEJAGNU_SITE_CONFIG)'.
- The `install-info' rule can now be instructed not to create/update
the `${infodir}/dir' file, by exporting the new environment variable
`AM_UPDATE_INFO_DIR' to the value "no".
Bugs fixed in 1.11.2:
* Bugs introduced by 1.11:
- The parallel-tests driver no longer produces erroneous results with
Tru64/OSF 5.1 sh upon unreadable log files.
- The `parallel-tests' test driver does not report spurious successes
when used with concurrent FreeBSD make (e.g., "make check -j3").
- When the parallel-tests driver is in use, automake now explicitly
rejects invalid entries and conditional contents in TEST_EXTENSIONS,
instead of issuing confusing and apparently unrelated error messages
(e.g., "non-POSIX variable name", "bad characters in variable name",
or "redefinition of TEST_EXTENSIONS), or even, in some situations,
silently producing broken `Makefile.in' files.
- The `silent-rules' option now truly silences all compile rules, even
when dependency tracking is disabled. Also, when `silent-rules' is
not used, `make' output no longer contains spurious backslash-only
lines, thus once again matching what Automake did before 1.11.
- The AM_COND_IF macro also works if the shell expression for the
conditional is no longer valid for the condition.
* Long-standing bugs:
- The order of Yacc and Lex flags is fixed to be consistent with other
languages: $(AM_YFLAGS) comes before $(YFLAGS), and $(AM_LFLAGS) before
$(LFLAGS), so that the user variables override the developer variables.
- "make distcheck" now correctly complains also when "make uninstall"
leaves one and only one file installed in $(prefix).
- A "make uninstall" issued before a "make install", or after a mere
"make install-data" or a mere "make install-exec" does not spuriously
fail anymore.
- Automake now warns about more primary/directory invalid combinations,
such as "doc_LIBRARIES" or "pkglib_PROGRAMS".
- Rules generated by Automake now try harder to not change any files when
`make -n' is invoked. Fixes include compilation of Emacs Lisp, Vala, or
Yacc source files and the rule to update config.h.
- Several scripts and the parallel-tests testsuite driver now exit with
the right exit status upon receiving a signal.
- A per-Makefile.am setting of -Werror does not erroneously carry over
to the handling of other Makefile.am files.
- The code for automatic dependency tracking works around a Solaris
make bug triggered by sources containing repeated slashes when the
`subdir-objects' option was used.
- The makedepend and hp depmodes now work better with VPATH builds.
- Java sources specified with check_JAVA are no longer compiled for
"make all", but only for "make check".
- An usage like "java_JAVA = foo.java" will now cause Automake to warn
and error out if `javadir' is undefined, instead of silently producing
a broken Makefile.in.
- aclocal and automake now honour the configure-time definitions of
AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
- The `install-info' recipe no longer tries to guess whether the
`install-info' program is from Debian or from GNU, and adaptively
change its behaviour; this has proven to be frail and easy to
regress.
* Reduced planning time in estimate mode for sizes with large prime factors.
* Added AVX autodetection under Visual Studio.
* Modern Fortran interface now uses a separate fftw3l.f03 interface file for
the long double interface, which is not supported by some Fortran compilers.
Provided new fftw3q.f03 interface file to access the quadruple-precision FFTW
routines with recent versions of gcc/gfortran.
* Added support for the NEON extensions to the ARM ISA.
* MPI code now compiles even if mpicc is a C++ compiler.
intltool 0.50.2
===============
intltool 0.50.2 is another minor release improving backwards compatibility.
Only one bug is fixed in this release:
* Use --no-translations only if intltool >= 0.50 is available (#903340).
Patch contributed by Hib Eris (https://launchpad.net/~hiberis).
intltool 0.50.1
===============
intltool 0.50.1 is a minor release with the following improvements:
* Support AM_SILENT_RULES (#402516).
Patch contributed by Hib Eris (https://launchpad.net/~hiberis).
* Improve support for extracting messages from GSettings files (#922685).
Patch contributed by Ryan Lortie (https://launchpad.net/~desrt).
* Support attribute tag extraction for Glade/GtkBuilder files (#923841).
Patch contributed by Ryan Lortie (https://launchpad.net/~desrt).
* Start including a ChangeLog in tarballs and provide a NEWS file (#924386).
This introduces a soft dependency on "bzr": it's only required for
maintainers who wish to regenerate a ChangeLog file from the bzr checkout.
* Fix quoting of XGETTEXT variable when setting MSGMERGE and GENPOT
in Makefile (#900738).
Patch contributed by Matthias Klose (https://launchpad.net/~doko).
intltool 0.50.0
===============
intltool 0.50.0 is a major bug fix release.
Among the fixes, the following stand out:
* Bug #580526
Finally, support for gsettings gschema.xml files is merged in, which
should enable maintainers to get a slightly simpler build setup
(i.e. no need to use NOMERGE rule anymore, and you can have intltool
directly extract translations from .gschema.xml files).
* Bug #790574:
Let xgettext extract Scheme strings out, and add support for
`intltool-update -m` to find files with marked strings.
* Bug #806006:
Improve handling of quotes in `intltool-update -m` so you get less
(no?) warnings about mismatched quotes, and Python processing doesn't
get messed up with docstrings and similar.
* Bug #520986:
One for the translators—messages are extracted in the order they appear
in original files now, thus allowing translators to infer more of the
context from the ordering.
