Regex Library Supporting Different Character Encodings
Oniguruma is a regular expressions library. The characteristics of
this library is that different character encoding for every regular
expression object can be specified.
Supported character encodings: ASCII, UTF-8, UTF-16BE, UTF-16LE,
UTF-32BE, UTF-32LE, EUC-JP, EUC-TW, EUC-KR, EUC-CN, Shift_JIS, Big5, GB
18030, KOI8-R, KOI8, ISO-8859-1, ISO-8859-2, ISO-8859-3, ISO-8859-4,
ISO-8859-5, ISO-8859-6, ISO-8859-7, ISO-8859-8, ISO-8859-9,
ISO-8859-10, ISO-8859-11, ISO-8859-13, ISO-8859-14, ISO-8859-15,
ISO-8859-16.
- Developed at devel:languages:ruby
- Sources inherited from project openSUSE:Factory
-
2
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Leap:15.1:Staging:FactoryCandidates/oniguruma && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| onig-6.9.6.tar.gz | 0000926459 905 KB | |
| oniguruma.changes | 0000010744 10.5 KB | |
| oniguruma.spec | 0000003954 3.86 KB |
Revision 24 (latest revision is 27)
Dominique Leuenberger (dimstar_suse)
accepted
request 846284
from
Marcus Rueckert (darix)
(revision 24)
- Update to 6.9.6
- When using configure script, if you have the POSIX API enabled
in an earlier version (disabled by default in 6.9.5) and you
need application binary compatibility with the POSIX API,
specify "--enable-binary-compatible-posix-api=yes" instead of
"--enable-posix-api=yes". Starting in 6.9.6,
"--enable-posix-api=yes" only supports source-level
compatibility for 6.9.5 and earlier about POSIX API. (Issue
#210)
- NEW: configure option
--enable-binary-compatible-posix-api=[yes/no]
- NEW API: Limiting the maximum number of calls of subexp-call
- NEW API: ONIG_OPTION_NOT_BEGIN_STRING / NOT_END_STRING /
NOT_BEGIN_POSITION
- Fixed behavior of ONIG_OPTION_NOTBOL / NOTEOL
- Fixed many problems found by OSS-Fuzz
- Fixed many problems found by Coverity
- Fixed CVE-2020-26159 (This turned out not to be a problem
later. #221)
- Under cygwin and mingw, generate and install the libonig.def
file (Issue #220)
Comments 0