* Fix LICENSE, the license is gnu-lgpl-v3 not gnu-gpl-v3
Changelog:
Overview of changes in gst123-0.3.0:
* Support visualization plugins during audio playback (Issue 3).
* Fix compilation for GNU/Hurd (Issue 7).
Changelog:
----------------------------------------------------------------------
OmegaT 2.5.2 update 2
----------------------------------------------------------------------
1 Enhancement
5 Bug fixes
1 Localisation update
----------------------------------------------------------------------
2.5.2 update 2 vs. 2.5.2
- The writeable glossary file can now have a .utf8 extension instead
of a .txt one, .txt being still the default
Bug fixes:
- When using Remove Tags, some non-OmegaT tags (e.g., %s, depending on
the kind of tags checked in Options > Tag Validation) and some
non-useful spaces could be copied at the end of the segment in the target
document
- In some rare circumstances, the display of matches in the Fuzzy Matches
pane could be very slow
- When the Fuzzy Matches pane was closed, the explanation text was
displayed in bold instead of the initial non-bold attribute
- In TMXs, the end of line was hardcoded as LF, instead of using the
system line separator (e.g., CR+LF under Windows, LF under Linux)
- In the Android filter, the "do not translate" mark has been corrected
Localisation updates:
- Dutch localisation updated to 2.5.2 (UI)
----------------------------------------------------------------------
OmegaT 2.5.2 update 1
----------------------------------------------------------------------
0 Enhancement
1 Bug fix
0 Localisation update
----------------------------------------------------------------------
2.5.2 update 1 vs. 2.5.2
Bug fixes:
- When the glossary folder wasn't in the default location, the
default writeable glossary file wasn't computed correctly. In addition,
the name of the glossary file was lost on saving when a manual correction
was done in project properties.
----------------------------------------------------------------------
OmegaT 2.5.2
----------------------------------------------------------------------
8 Enhancements
2 Bug fixes
5 Localisation updates
----------------------------------------------------------------------
2.5.2 vs. 2.5.1 update 1
Implemented requests:
- Show non-breakable space
http://sourceforge.net/support/tracker.php?aid=3495779
- Use search term as window title in Search window
http://sourceforge.net/support/tracker.php?aid=2610094
- Clarification of the Options > Spell Checking... dialog
http://sourceforge.net/support/tracker.php?aid=3473630
- Selectable location for the writeable glossary file
http://sourceforge.net/support/tracker.php?aid=3503373
- Second plugin location in <home>/plugins
http://sourceforge.net/support/tracker.php?aid=3428485
Other enhancements:
- Add explanatory messages to windows as hints when no project is open
- Segments containing a note can be marked with View >
Mark Segments with Notes. This marking has priority over Mark Translated
and Mark Untranslated.
- Display of the corresponding colours in the View menu for "Mark"
menu entries
Bug fixes:
- In the PO filter, "path" was always displayed in the Comment pane,
even if it was empty
- When using Insert Source Tags, a space was added before the first one
Localisation updates:
- Simplified Chinese localisation updated to 2.5.0 (UI, readme, documentation)
- Italian localisation updated to 2.5.1 (UI)
- Dutch localisation updated to 2.5.1 (UI)
- Japanese localisation updated to 2.5.1 (UI)
- Slovenian localisation updated to 2.5.2 (UI)
* New utf8_general_mysql500_ci and ucs2_general_mysql500_ci collations have
been added that preserve the behavior of utf8_general_ci and ucs2_general_ci
from versions of MySQL previous to 5.1.24. Bug 27877 corrected an error in
the original collations but introduced an incompatibility for columns that
contain German 'ß' LATIN SMALL LETTER SHARP S. (As a result of the fix, that
character compares equal to characters with which it previously compared
different.) A symptom of the problem after upgrading to MySQL 5.1.24 or newer
from a version older than 5.1.24 is that CHECK TABLE produces this error:
* yaSSL was upgraded from version 1.7.2 to 2.2.0.
* Bugs Fixed
Remove devel/py-ctypes (only needed by and supporting python24).
Remove PYTHON_VERSIONS_ACCEPTED and PYTHON_VERSIONS_INCOMPATIBLE
lines that just mirror defaults now.
Miscellaneous cleanup while editing all these files.
* InnoDB Storage Engine: A deprecation warning is now issued when
--ignore-builtin-innodb is used.
* yaSSL was upgraded from version 1.7.2 to 2.2.0.
* Security Fix: Bug 13510739 and Bug 63775 were fixed.
* Important Change: InnoDB Storage Engine: When a row grew in size due to an
UPDATE operation, other (non-updated) columns could be moved to off-page
storage so that information about the row still fit within the constraints of
the InnoDB page size. The pointer to the new allocated off-page data was not
set up until the pages were allocated and written, potentially leading to
lost data if the system crashed while the column was being moved out of the
page. The problem was more common with tables using ROW_FORMAT=DYNAMIC or
ROW_FORMAT=COMPRESSED along with the Barracuda file format, particularly with
the innodb_file_per_table setting enabled, because page allocation operations
are more common as the .ibd tablespace files are extended. Still, the problem
could occur with any combination of InnoDB version, file format, and row
format.
* InnoDB Storage Engine: An erroneous assertion could occur, in debug builds
only, when creating an index on a column containing zero-length values (that
is, '').
* InnoDB Storage Engine: A DDL operation such as ALTER TABLE ... ADD COLUMN
could stall, eventually timing out with an Error 1005: Can't create table
message referring to fil_rename_tablespace.
* InnoDB Storage Engine: A DDL operation for an InnoDB table could cause a busy
MySQL server to halt with an assertion error:
More...
Track the sysinst changes of 2012-04-06 introducing the new
post-install configuration menu.
Print a message before creating the disk image, as it can take
a long time and make it appear that anita has hung.
The problem is the following: When checking the CFLAGS / LIBS for
including pthread support, any warning on stdout is counted as a no.
However, the test does not use CFLAGS on the command line, which
produces a harmless debug warning. This workaround has the consequence
of adding the default CFLAGS twice on the command line but this is not
a problem.
implementation in MirBSD enforces this.
Use ${MKDIR} to create the target directory before running pax.
This does not actually fix the build on MirBSD (it needs some more
work in the configure), it is at least a start.
implementation in MirBSD enforces this.
Use ${MKDIR} to create the target directory before running pax.
Unbreaks things like firefox-l10n and friends on MirBSD.
Changes in Maxima 5.27:
Backwards-incompatible changes:
* remove obsolete Cray Fortran translator
* rename topoly and to_poly_solver to to_poly and to_poly_solve, respectively
New items in core:
* new functions zn_order, zn_primroot_p, zn_primroot, zn_log, chinese
New items in share:
* package rkf45: Runge-Kutta-Fehlberg 4th-5th order numerical o.d.e. solver
Other changes:
* functions bessel_i, bessel_j: results for imaginary arguments
* function build_info: return a structure instead of just printing its data
* function plot3d: allow 3-d parametric plots
* functions fortmx, f90mx: generate assignments to 1-d array when argument is a list
* package ezunits: update values for physical constants
* revise and update documentation
* reorganization of directory maxima/share
* clean up source code by cutting out unused functions
Bug fixes:
3509430: limit of tanh(x) at 0 makes no sense
3497046: Integration of products of sin(nz)/(nz) sometimes fails
3495182: hgfred([-n/2, (n-1)/2],[1],x) --> error
3484414: display places (false) before output if display2d is false
3480954: integrate(sin(x)^2/x,x,minf,inf) gives not zero
3473549: gcl bug using 1-12-2012 defint.lisp
3470668: Integration is not correct: invalid 'false' term in results
3469184: integrate(exp(-x^n),x,0,1) bug for n >2
3449369: nfloat
3397562: sin(x^2)/(x^2) improper integral incorrect?
mailing list 2012-02-27: print ( false ) bug 5.26.0
mailing list circa 2012-02-19: BIGFLOAT::%TO should pass CL complex numbers
mailing list circa 2012-01-27: nonstandard extension in category scripts
mailing list circa 2012-01-09: invert_by_lu does not work as expected
overflow in regularized incomplete gamma function
incorrect value for gamma_incomplete(0,200*%i)
* Move some MesaLib files from files/xorg to files/xfree.MesaLib,
or unwanted MesaLib may be buildlinked (and result in build failure).
* Add some files from OpenBSD-5.0.
allowed in option names (pkglint has been updated).
---
Module Name: pkgsrc
Committed By: sbd
Date: Wed Apr 4 22:20:37 UTC 2012
Modified Files:
pkgsrc/lang/gcc46: options.mk
Log Message:
Rename option "gcc-c++" to "gcc-cpp" (with legacy support) as pkglint
complains with: "gcc-c++" is not a valid option name.
To generate a diff of this commit:
cvs rdiff -u -r1.4 -r1.5 pkgsrc/lang/gcc46/options.mk
allowed in option names (pkglint has been updated).
---
Module Name: pkgsrc
Committed By: sbd
Date: Wed Apr 4 22:18:30 UTC 2012
Modified Files:
pkgsrc/lang/gcc44: options.mk
Log Message:
Rename option "gcc-c++" to "gcc-cpp" (with legacy support) as pkglint
complains with: "gcc-c++" is not a valid option name.
To generate a diff of this commit:
cvs rdiff -u -r1.7 -r1.8 pkgsrc/lang/gcc44/options.mk
Because it depends on changes to the API in libtiff 4.x, set the minimum
BUILDLINK_API_DEPENDS accordingly. And, even though it wasn't building,
bump PKGREVISION to 7; the new package depending on tiff>=4.0 needs to
be distinguishable from the old package depending on tiff<4.0.
XXX: This package desperately needs to be updated. It is years out of
XXX: date with respect to upstream.
Attempt to honor VARBASE instead of blithely dropping stuff into /var;
may be incomplete. Doing this right may require sorting out multiple
/var trees as it shouldn't, at least by default, be working dialer
locks in the pkgsrc VARBASE; however, it's not clear that those will
always necessarily be in /var either. For now the package assumes
they will be though.
*** If I have broken this for you, please let me know ASAP.
because quota-related FFS header reorganization caused the definition
of the FFS struct direct to no longer be visible; however, on older
NetBSD since struct direct and struct dirent diverged (which was some
time back) it would have built successfully unless given -Wall, but
not worked.
dirent rather than the FFS struct direct. As this has been POSIX for
at least twenty years I very, very much doubt there are any exceptions
left in the wild.
Fixes build on NetBSD-current.
