[0.6.0] - 2022-05-13
Add split-by-byte using --bytes
Add split-by-character using --characters
Faster performance when -p (compress delimiters) is on
Faster performance when reading the input
CI now fails if the linter is not satisfied
Reviewd CI/release actions, simpler, faster
Release binaries for ARM too
### Added
- allow standard pdf/A-4
- check requirement for max-pdfversion
- add requirement for Info dictionary
- load tagpdf-base if it exists to provide the
tagging commands.
### Fixed
- Support/firstaid for colorspace package
- Support for metadata with hyperxmp and xetex
The code has been completely reorganized. The implementation documentation is
now completely in English and uses the new class koma-script-source-doc. This
class is based on version 3 of the doc package. Partially the order of the code
has changed. Some deprecated code parts have been removed completely, others
generate long overdue warnings.
scrartcl, scrbook, scrreprt:
Non-floating environments table- und figure- are also defined.
scrlttr2, scrletter:
The internal macros \if at plength, \@newplength, \@setplength, and \@addtoplength
are not only deprecated, which has been documented since KOMA-Script 3.25 from
2018/03/30, but also warn. If you haven't already done so, you should use the
user commands \Ifplength, \newplength, \setplength, and \addtoplength instead
urgently now!
* Add macro \doclicenseLongTextForHyperref and use it inside \hypersetup
to replace the fagile code that was previously used.
* Add Traditional Chinese (Taiwan), Swedish and Esperanto translations.
Adding a couple of new components and a nice feature to transistors
and tubes.
- Added TVS diodes (transorb)
- Added proximity switches
- Added partially drawn tube and transistor borders
Otherwise it blows up if CPP is $(CC) -E. Seen in the MacOS bulk builds.
(this commit syncs seamonkey and firefox52 with the newer firefoxes
that already have this fix)
There's no need for CONFLICTS between the xemacs and emacs versions of
the same elisp package unless the PLISTs overlap, and if they do (most
don't because they install into different subtrees), that fact is
sufficient.
As suggested by PR 39886, a long long time ago.
XKB_OUTPUT_DIR, which is usually derived from VARBASE, and in any case
appears intended to be handled by OWN_DIRS. While here, remove
unrecognized configure options. Fixes packaging in typical
configurations, NFCI elsewhere.