summaryrefslogtreecommitdiff
path: root/textproc
AgeCommit message (Collapse)AuthorFilesLines
2017-01-30Update to 2.27wen2-8/+7
Upstream changes: * Noteworthy changes in release 2.27 (2016-12-06) [stable] ** Bug fixes grep no longer reports a false match in a multibyte, non-UTF8 locale like zh_CN.gb18030, with a regular expression like ".*7" that just happens to match the 4-byte representation of gb18030's \uC9, the final byte of which is the digit "7". [bug introduced in grep-2.19] grep by default now reads all of standard input if it is a pipe, even if this cannot affect grep's output or exit status. This works better with nonportable scripts that run "PROGRAM | grep PATTERN >/dev/null" where PROGRAM dies when writing into a broken pipe. [bug introduced in grep-2.26] grep no longer mishandles ranges in nontrivial unibyte locales. [bug introduced in grep-2.26] grep -P no longer attempts multiline matches. This works more intuitively with unusual patterns, and means that grep -Pz no longer rejects patterns containing ^ and $ and works when combined with -x. [bugs introduced in grep-2.23] A downside is that grep -P is now significantly slower, albeit typically still faster than pcregrep. grep -m0 -L PAT FILE now outputs "FILE". [bug introduced in grep-2.5] To output ':' and tab-align the following character C, grep -T no longer outputs tab-backspace-':'-C, an approach that has problems if run inside an Emacs shell window. [bug introduced in grep-2.5.2] grep -T now uses worst-case widths of line numbers and byte offsets instead of guessing widths that might not work with larger files. [bug introduced in grep-2.5.2] grep's use of getprogname no longer causes a build failure on HP-UX. ** Improvements grep no longer reads the input in a few more cases when it is easy to see that matching cannot succeed, e.g., 'grep -f /dev/null'. * Noteworthy changes in release 2.26 (2016-10-02) [stable] ** Bug fixes Grep no longer omits output merely because it follows an output line suppressed due to encoding errors. [bug introduced in grep-2.21] In the Shift_JIS locale, grep no longer mistakenly matches in the middle of a multibyte character. [bug present since "the beginning"] ** Improvements grep can be much faster now when standard output is /dev/null. grep -F is now typically much faster when many patterns are given, as it now uses the Aho-Corasick algorithm instead of the Commentz-Walter algorithm in that case. grep -iF is typically much faster in a multibyte locale, if the pattern and its case counterparts contain only single byte characters. grep with complicated expressions (e.g., back-references) and without -i now uses the regex fastmap for better performance. In multibyte locales, grep now handles leading "." in patterns more efficiently. grep now prints a "FILENAME:LINENO: " prefix when diagnosing an invalid regular expression that was read from an '-f'-specified file. * Noteworthy changes in release 2.25 (2016-04-21) [stable] ** Bug fixes In the C or POSIX locale, grep now treats all bytes as valid characters even if the C runtime library says otherwise. The revised behavior is more compatible with the original intent of POSIX, and the next release of POSIX will likely make this official. [bug introduced in grep-2.23] grep -Pz no longer mistakenly diagnoses patterns like [^a] that use negated character classes. [bug introduced in grep-2.24] grep -oz now uses null bytes, not newlines, to terminate output lines. [bug introduced in grep-2.5] ** Improvements grep now outputs details more consistently when reporting a write error. E.g., "grep: write error: No space left on device" rather than just "grep: write error".
2017-01-30Update to 1.41wen2-7/+7
Upstream changes: 1.41 2016-12-29 15:10:00 MANWAR - Proposed fix for RT #119292 and rollbacked patch for RT #118764. Document how close() deals when <filename> or <fh> is involved. i.e. When <fh> is provided then don't try to close the file handle at the end. Leave that for the end user to deal with it outside. Added new method flush() that does exactly this. 1.40 2016-12-20 12:00:00 MANWAR - Proposed fix for RT #118945.
2017-01-28Update to 1.57wen2-8/+7
Upstream changes: 1.57 2017-01-22 rurban ---- * Todo the t/exec.t test 2 on cygwin. * Fixed/Todo the t/decrypt.t test 7 utf8 failures. Skip with non UTF-8 locale. 1.56 2017-01-20 rurban ---- * add binmode to the decrypt/encr,decrypt sample scripts * add utf8-encoded testcase to t/decrypt.t [cpan #110921]. use -C * stabilized some tests, add diag to sometimes failing sh tests * moved filter-util.pl to t/ * fixed INSTALLDIRS back to site since 5.12 [gh #2] * fixed exec/sh test races using the same temp. filenames * reversed this Changes file to latest first * added Travis CI
2017-01-27This is the proper GITHUB_RELEASE, fixes fetching. No change to distfile hash.fhajny1-2/+2
2017-01-25Recursive bump for poppler updatewiz1-2/+2
2017-01-25Remove p5-XML-Sablotron.wiz6-248/+1
Obsolete and core dumps. Inspired by PR 51903.
2017-01-25Add arm64 for OpenBSD.wiz2-4/+4
From jmc@OpenBSD. Bump version.
2017-01-24Update to 3.21wen2-7/+7
Upstream changes: version 3.21: Wed 11 Jan 10:02:19 CET 2017 Fixes: - XOP hooks were instated, even though XML::Compile::XOP was not. Schema/WSDL compilation will be a little faster now. https://github.com/mjgardner/xml-compilex-schema-loader/issues/1 [Slaven Rezi�] - constant name: XS_DAEMON_NS -> XC_DAEMON_NS rt.cpan.org#119800 [Pavel Trushkin] Improvements: - spell fix Debian rt.cpan.org#118577 [Gregor Herrmann, Debian]
2017-01-24Update to 3.4.0wen2-8/+7
Upstream changes: 3.4.0 2017-01-20 15:00:00+0900 - Fix tied hash issue(#173) - Fix encoding issue(#160) - Fix segmentation fault issue by accessing uninitialized array element(#159)
2017-01-22Updated iso-codes to 3.74.wiz2-7/+7
iso-codes 3.74 -------------- Dr. Tobias Quathamer <toddy@debian.org> Mon, 16 Jan 2017 [ ISO 3166-2 ] * Remove GB- prefix from parent code for Great Britain. Closes: alioth#315604
2017-01-22Fixed spelling of NetBSD in mail addresses.rillig2-4/+4
2017-01-21Update textproc/erlang-fast_yaml to 1.0.8.fhajny2-7/+7
- Load local .so instead from system package when running tests.
2017-01-21Update textproc/erlang-fast_xml to 1.1.19.fhajny2-8/+7
- Add checks for empty string - Remove unused code - Load locally build .so file when performing tests
2017-01-21Recursive revbump from audio/pulseaudio-10.0ryoon3-6/+6
2017-01-20Updated py-vobject to 0.9.4.wiz2-9/+7
0.9.4 improved PEP8 compliance (#53) improved Python 3 compatibility (#55) improved encoding/decoding (#49, #58) - thanks @pbiering! correct handling of pytz timezones (#45) - thanks @Achimh3011! 0.9.3 Fixed use of doc in setup.py for -OO mode (#19) - thanks @dsanders11! Added python3 compatibility for base64 encoding (#21) - thanks @prauscher! Fixed ORG fields with multiple components (#23) - thanks @untitaker! Removed stray HTML entity in README (#26) - thanks @inglesp! Updated README.md to show example of adding "ORG" to a vCard (#28) - thanks @Tamerz! Handle pytz timezones in iCalendar serialization (#33) - thanks @medmunds! Use logging instead of printing to stdout (#35) - thanks @lucc!
2017-01-19Convert all occurrences (353 by my count) ofagc15-45/+45
MASTER_SITES= site1 \ site2 style continuation lines to be simple repeated MASTER_SITES+= site1 MASTER_SITES+= site2 lines. As previewed on tech-pkg. With thanks to rillig for fixing pkglint accordingly.
2017-01-18Update PLIST.{,docs} in order to fix building of groff without the `groff-docs'leot3-9/+9
option. Bump PKGREVISION Noticed by and thanks to Hiroshi Hakoyama via PR pkg/51896.
2017-01-17Fix typo.wiz1-2/+2
2017-01-17Add another bug report for failing tests.wiz1-1/+3
2017-01-16Updated gsed to 4.3.wiz5-15/+32
* Noteworthy changes in release 4.3 (2016-12-30) [stable] ** Improvements sed's regular expression matching is now typically 10x faster sed now uses unlocked-io where available, resulting in faster I/O operations. ** Bug fixes sed no longer mishandles anchors ^/$ in multiline regex (s///mg) with -z option (NUL terminated lines). [Bug introducted in sed-4.2.2 with the initial implementation of -z] sed no longer accepts a ":" command without a label; before, it would treat that as defining a label whose name is empty, and subsequent label-free "t" and "b" commands would use that label. Now, sed emits a diagnostic and fails for that invalid construct. sed no longer accesses uninitialized memory when processing certain invalid multibyte sequences. Demonstrate with this: echo a | LC_ALL=ja_JP.eucJP valgrind sed/sed 's/a/b\U\xb2c/' The error appears to have been introduced with the sed-4.0a release. The 'y' (transliterate) operator once again works with a NUL byte on the RHS. E.g., sed 'y/b/\x00/' now works like tr b '\0'. GNU sed has never before recognized \x00 in this context. However, sed-3.02 and prior did accept a literal NUL byte in the RHS, which was possible only when reading a script from a file. For example, this: echo abc|sed -f <(printf 'y/b/\x00/\n')|cat -A is what stopped working. [bug introduced some time after sed-3.02 and prior to the first sed-4* test release] When the closed-above line number ranges of N editing commands overlap (N>1), sed would apply commands 2..N to the line just beyond the largest range endpoint. [bug introduced some time after sed-4.09 and prior to release in sed-4.1] Before, this command would mistakenly modify line 5: $ seq 6|sed '2,4d;2,3s/^/x/;3,4s/^/y/' 1 yx5 6 Now, it does not: $ seq 6|sed '2,4d;2,3s/^/x/;3,4s/^/y/' 1 5 6 An erroneous sed invocation like "echo > F; sed -i s//b/ F" no longer leaves behind a temporary file. Before, that command would create a file alongside F with a name matching /^sed......$/ and fail to remove it. sed --follow-symlinks now works again for stdin. [bug introduced in sed-4.2.2] sed no longer elides invalid bytes in a substitution RHS. Now, sed copies such bytes into the output, just as Perl does. [bug introduced in sed-4.1 -- it was also present prior to 4.0.6] sed no longer prints extraneous character when a backslash follows \c. '\c\\' generates control character ^\ (ASCII 0x1C). Other characters after the second backslash are rejected (e.g. '\c\d'). [bug introduced in the sed-4.0.* releases] sed no longer mishandles incomplete multibyte sequences in s,y commands and valid multibyte SHIFT-JIS characters in character classes. Previously, the following commands would fail: LC_ALL=en_US.UTF-8 sed $'s/\316/X/' LC_ALL=ja_JP.shiftjis sed $'/[\203]/]/p' [bug introduced some time after sed-4.1.5 and before sed-4.2.1] ** Feature removal The "L" command (format a paragraph like the fmt(1) command would) has been listed in the documentation as a failed experiment for at least 10 years. That command is now removed. ** Build-related "make dist" now builds .tar.xz files, rather than .tar.gz ones. xz is portable enough and in wide-enough use that distributing only .tar.xz files is enough. It has been fine for coreutils, grep, diffutils and parted for a few years. ** New Features new --sandbox option rejects programs with r/w/e commands. * Noteworthy changes in release 4.2.2 (2012-12-22) [stable] * don't misbehave (truncate input) for lines of length 2^31 and longer * fix endless loop on incomplete multibyte sequences * -u also does unbuffered input, rather than unbuffered output only * New command `F' to print current input file name * sed -i, s///w, and the `w' and `W' commands also obey the --binary option (and create CR/LF-terminated files if the option is absent) * --posix fails for scripts (or fragments as passed to the -e option) that end in a backslash, as they are not portable. * New option -z (--null-data) to separate lines by ASCII NUL characters. * \x26 (and similar escaped sequences) produces a literal & in the replacement argument of the s/// command, rather than including the matched text.
2017-01-16Updated py-lxml to 3.7.2.wiz2-7/+7
============== lxml changelog ============== 3.7.2 (2017-01-08) ================== Bugs fixed ---------- * Work around installation problems in recent Python 2.7 versions due to FTP download failures. * GH#219: ``xmlfile.element()`` was not properly quoting attribute values. Patch by Burak Arslan. * GH#218: ``xmlfile.element()`` was not properly escaping text content of script/style tags. Patch by Burak Arslan.
2017-01-16Updated iso-codes to 3.73.wiz2-7/+7
iso-codes 3.73 -------------- Dr. Tobias Quathamer <toddy@debian.org> Tue, 3 Jan 2017 [ ISO 3166-2 ] * Remove CZ- prefix from parent code for Czechia.
2017-01-16Updated p5-Text-BibTeX to 0.78.wiz2-7/+7
0.78 2017-01-10 * Fixed some issues with uninitialized arrays and s390 * Fixed test with fileno (thanks to Karl Wette).
2017-01-14Add dependency on py-webencodings (added the package in preparation,kleink1-1/+3
but still managed not to add the dependency here). Bump PKGREVISION.
2017-01-14Update to 1.2.2ryoon3-9/+20
* Enable gobject-introspection and vala support. Required by net/corebird Changelog: News in 1.2.2, 2016-12-16 ------------------------- * GtkTextView support: fix populate-popup signal param type News in 1.2.1 ------------- * Add Croatian translation News in 1.2.0 ------------- * Translation updates News in 1.1.3 ------------- This is an unstable release in the 1.1 development cycle. The 1.2 stable version will be released at the same time as GNOME 3.22. * Add the gspell_text_view_basic_setup() convenience function to enable inline spell-checking in a GtkTextView in 2 lines. * Support words separated by dashes (compounds) * Use the AX_VALGRIND_CHECK Autotools macro * Translation updates News in 1.1.2 ------------- This is an unstable release in the 1.1 development cycle. The 1.2 stable version will be released at the same time as GNOME 3.22. * Inline checker: fix constant redrawing of the GtkTextView when the current word is not checked. * Generate enum types * Translation updates News in 1.1.1 ------------- This is an unstable release in the 1.1 development cycle. The 1.2 stable version will be released at the same time as GNOME 3.22. * New API: inline checker: add an option to select the language from the context menu (right-click menu) * Fix gtk-doc build issue * Update GtkTextRegion -> GtkSourceRegion (utility class copied from the GtkSourceView library) * Translation updates
2017-01-120.07 Fri 16 Dec 2016rodent2-8/+7
Strips \240 characters created by HTML::Formatter when it encounters a &nbsp;
2017-01-12What's new in 8.0.0rodent3-8/+38
Merge to upstream commit 1eb06f31e1dd; relevant code changes: Removing the ability for .._for_region methods in shortnumberinfo.py to work on strings, as well of phone number objects. These have been marked deprecated for months. Any users of these methods should call phonenumbers.parse first to create a PhoneNumber object, and pass this in. Support semicolon as extension character while parsing phone numbers. This is not applicable when you are trying to find the phone numbers. What's new in 7.7.5 Merge to upstream commit e905483f87cf; relevant code changes: Removing all references to possible_number_pattern other than in the metadata itself. What's new in 7.7.4 Merge to upstream commit fedbc7020703; code changes: GitHub project changes: Changed tag to vX.Y.Z from release-X.Y.Z; this may affect ports and derived projects. Metadata structure changes in XML file: Mobile and Fixed-Line blocks are no longer assumed to inherit missing data from the GeneralDesc, but are treated like every other phone number type. This means that for the non-geographical country codes, like +800, the example number has been moved from generalDesc to the relevant number types, and the code in getExampleNumberForNonGeoEntity has been changed to look at these sub-types for an example number. This also means that the "NA" and "-1" blocks present in the metadata to indicate that no mobile or fixed-line numbers appear for the entity have been removed. There should no longer be an exampleNumber at the generalDesc level, but it should be present at every PhoneNumberDesc with data. Code changes: Using new possibleLengthInfo to decide whether a short number is the right length or not. This could result in more specific results; whereas before, a number from length 3 to length 6 may have been deemed possible, now we may exclude a number of length 5. Add hash (#) as a diallable character. Numbers with # in them will no longer have formatting applied in format_n_original_format, and normalize_diallable_chars_only now retains the # symbol. example_number_for_non_geo_entity has been changed to look at the specific number types, not just the generalDesc, for the example numbers; this is a necessary change after the metadata structure change detailed above. What's new in 7.7.3 Merge to upstream commit ad0ce0c94501; code changes: Fixed phonemetadata.py not to merge from a NumberFormat's unset bool national_prefix_optional_when_formatting. What's new in 7.7.2 Merge to upstream commit 2d0d216f6032; code changes: Stop setting empty preferred_domestic_carrier_code, and if we are passed such a number then treat the empty field as if unset. What's new in 7.7.1 Merge to upstream commit 8c37310deb49; code changes: Switching the internal implementation of is_possible_number and related functions to use the new possibleLengths metadata. This affects a lot of countries, making is_possible_number more restrictive as more precise data is available. It also affects parsing ambiguous and invalid numbers, as we decide whether to strip a possible national prefix (1) or country code based on the length of the number and whether it is possible before or after this. Formatting, naming and comment tweaks to follow style guide Removal of unneeded _can_be_geocoded method in the timezone.py file, using phonenumberutil.py instead What's new in 7.7.0 Merge to upstream commit 1ec4d341c3cd; no code changes that affect the Python version so this is just a version bump to stay in sync with upstream. What's new in 7.6.1 Merge to upstream commit 7cc500f588db; code changes: phonemetadata.py has two more fields to represent possible lengths of phone numbers. Changed buildmetadatafromxml.py to alter the way that metadata about possible-lengths information is consumed when constructing metadata to populate these. Discussion list email What's new in 7.6.0 Merge to upstream commit ddf60b1c175e; code changes: Made is_number_geographical() public and added is_number_type_geographical(), and changed the geocoder to use this when checking whether to give a detailed answer or country-level only. What's new in 7.5.0 Merge to upstream commit 3f83454ed62b; no code changes that affect the Python version so this is just a version bump to stay in sync with upstream.
2017-01-12DEPENDS on devel/py-wcwidth and textproc/py-html5lib.rodent1-1/+4
2017-01-12Version 4.3.0 (December 29, 2016)rodent3-8/+11
ftfy has gotten by for four years without dependencies on other Python libraries, but now we can spare ourselves some code and some maintenance burden by delegating certain tasks to other libraries that already solve them well. This version now depends on the html5lib and wcwidth libraries. Feature changes: The remove_control_chars fixer will now remove some non-ASCII control characters as well, such as deprecated Arabic control characters and byte-order marks. Bidirectional controls are still left as is. This should have no impact on well-formed text, while cleaning up many characters that the Unicode Consortium deems "not suitable for markup" (see Unicode Technical Report #20). The unescape_html fixer uses a more thorough list of HTML entities, which it imports from html5lib. ftfy.formatting now uses wcwidth to compute the width that a string will occupy in a text console. Heuristic changes: Updated the data file of Unicode character categories to Unicode 9, as used in Python 3.6.0. (No matter what version of Python you're on, ftfy uses the same data.) Pending deprecations: The remove_bom option will become deprecated in 5.0, because it has been superseded by remove_control_chars. ftfy 5.0 will remove the previously deprecated name fix_text_encoding. It was renamed to fix_encoding in 4.0. ftfy 5.0 will require Python 3.2 or later, as planned. Python 2 users, please specify ftfy < 5 in your dependencies if you haven't already. Version 4.2.0 (September 28, 2016) Heuristic changes: Math symbols next to currency symbols are no longer considered 'weird' by the heuristic. This fixes a false positive where text that involved the multiplication sign and British pounds or euros (as in '5×£35') could turn into Hebrew letters. A heuristic that used to be a bonus for certain punctuation now also gives a bonus to successfully decoding other common codepoints, such as the non-breaking space, the degree sign, and the byte order mark. In version 4.0, we tried to "future-proof" the categorization of emoji (as a kind of symbol) to include codepoints that would likely be assigned to emoji later. The future happened, and there are even more emoji than we expected. We have expanded the range to include those emoji, too. ftfy is still mostly based on information from Unicode 8 (as Python 3.5 is), but this expanded range should include the emoji from Unicode 9 and 10. Emoji are increasingly being modified by variation selectors and skin-tone modifiers. Those codepoints are now grouped with 'symbols' in ftfy, so they fit right in with emoji, instead of being considered 'marks' as their Unicode category would suggest. This enables fixing mojibake that involves iOS's new diverse emoji. An old heuristic that wasn't necessary anymore considered Latin text with high-numbered codepoints to be 'weird', but this is normal in languages such as Vietnamese and Azerbaijani. This does not seem to have caused any false positives, but it caused ftfy to be too reluctant to fix some cases of broken text in those languages. The heuristic has been changed, and all languages that use Latin letters should be on even footing now. Version 4.1.1 (April 13, 2016) Bug fix: in the command-line interface, the -e option had no effect on Python 3 when using standard input. Now, it correctly lets you specify a different encoding for standard input. Version 4.1.0 (February 25, 2016) Heuristic changes: ftfy can now deal with "lossy" mojibake. If your text has been run through a strict Windows-1252 decoder, such as the one in Python, it may contain the replacement character � (U+FFFD) where there were bytes that are unassigned in Windows-1252. Although ftfy won't recover the lost information, it can now detect this situation, replace the entire lossy character with �, and decode the rest of the characters. Previous versions would be unable to fix any string that contained U+FFFD. As an example, text in curly quotes that gets corrupted “ like this â€� now gets fixed to be “ like this �. Updated the data file of Unicode character categories to Unicode 8.0, as used in Python 3.5.0. (No matter what version of Python you're on, ftfy uses the same data.) Heuristics now count characters such as ~ and ^ as punctuation instead of wacky math symbols, improving the detection of mojibake in some edge cases. New features: A new module, ftfy.formatting, can be used to justify Unicode text in a monospaced terminal. It takes into account that each character can take up anywhere from 0 to 2 character cells. Internally, the utf-8-variants codec was simplified and optimized. Version 4.0.0 (April 10, 2015) Breaking changes: The default normalization form is now NFC, not NFKC. NFKC replaces a large number of characters with 'equivalent' characters, and some of these replacements are useful, but some are not desirable to do by default. The fix_text function has some new options that perform more targeted operations that are part of NFKC normalization, such as fix_character_width, without requiring hitting all your text with the huge mallet that is NFKC. If you were already using NFC normalization, or in general if you want to preserve the spacing of CJK text, you should be sure to set fix_character_width=False. The remove_unsafe_private_use parameter has been removed entirely, after two versions of deprecation. The function name fix_bad_encoding is also gone. New features: Fixers for strange new forms of mojibake, including particularly clear cases of mixed UTF-8 and Windows-1252. New heuristics, so that ftfy can fix more stuff, while maintaining approximately zero false positives. The command-line tool trusts you to know what encoding your input is in, and assumes UTF-8 by default. You can still tell it to guess with the -g option. The command-line tool can be configured with options, and can be used as a pipe. Recognizes characters that are new in Unicode 7.0, as well as emoji from Unicode 8.0+ that may already be in use on iOS. Deprecations: fix_text_encoding is being renamed again, for conciseness and consistency. It's now simply called fix_encoding. The name fix_text_encoding is available but emits a warning. Pending deprecations: Python 2.6 support is largely coincidental. Python 2.7 support is on notice. If you use Python 2, be sure to pin a version of ftfy less than 5.0 in your requirements.
2017-01-12DEPENDS on devel/py-cython.rodent1-1/+3
2017-01-122.0 [2016-03-17]rodent3-15/+13
rewrite of the construction algorithm to speed it up and save memory 1.9 [2015-10-10] recompiled with Cython 0.23.4 for better compatibility with recent Python versions.
2017-01-11Update py-html5lib to 0.999999999.kleink3-60/+58
This is the actual update to 0.999999999; the previous one was to 0.9999999 only. Changes for the missed two versions can be looked up there.)
2017-01-10Update py-tinycss to 0.4.kleink3-9/+16
Version 0.4 ----------- Released on 2016-09-23. * Add an __eq__ operator to Token object. * Support Fonts 3.
2017-01-08Now gemspec dose not require ruby-pkg-config any more.taca1-2/+2
Bump PKGREVISION.
2017-01-07Updated ruby-nokogiri to 1.7.0.1.wiz3-9/+9
# 1.7.0.1 / 2017-01-04 ## Bugs * Fix OpenBSD support. (#1569) (related to #1543) # 1.7.0 / 2016-12-26 ## Features * Remove deprecation warnings in Ruby 2.4.0 (#1545) (Thanks, @matthewd!) * Support egcc compiler on OpenBSD (#1543) (Thanks, @frenkel and @knu!) ## Backwards incompatibilities. This release ends support for: * Ruby 1.9.2, for which official support ended on 2014-07-31 * Ruby 1.9.3, for which official support ended on 2015-02-23 * Ruby 2.0.0, for which official support ended on 2016-02-24 * MacRuby, which hasn't been actively supported since 2015-01-13 (see https://github.com/MacRuby/MacRuby/commit/f76b9d6e99c18236db617e8aceb12c27d593a483)
2017-01-04Updated p5-Net-IDN-Encode to 2.400.wiz2-7/+7
2.400 (2017-01-01) - new release version - remove author tests - more spelling fixes 2.399_20161227 - FIXES #119468: [PATCH] spelling fixes (reported by GREGOA) - possible fix for utf8 warnings under perl 5.8.x 2.399_20161210 - update to Unicode 9.0.0 - changed generation of tests so that TODO is no longer required when the module author's perl doesn't support the newest Unicode version
2017-01-04Use curses framework.roy1-3/+7
2017-01-04Use the curses framework.roy3-17/+9
2017-01-04Fix build on SunOS platforms.fhajny3-3/+107
2017-01-03Update textproc/erlang-stringprep to 1.0.7.fhajny3-11/+11
- Use p1_utils 1.0.6 - Fix tests - Make sure stringprep isn't compiled to native code
2017-01-03Update textproc/erlang-fast_yaml.fhajny3-11/+11
- Use p1_utils 1.0.6 - Make sure fast_yaml isn't compiled to native code
2017-01-03Include a non-versioned symlink to work for includes. PKGREVISION++fhajny2-2/+8
2017-01-03Use "${MV} || ${TRUE}" and "${RM} -f" consistently in post-install targets.jperkin8-23/+23
2017-01-03Update textproc/erlang-fast_xml to 1.1.18.fhajny3-11/+11
Version 1.1.18 - Use p1_utils 1.0.6 - fix xref with otp 17 Version 1.1.17 - Add 'undefined' type to some record fields type specs Version 1.1.16 - Improve XML generator
2017-01-03Update textproc/py-xlsxwriter to 0.9.6.fhajny2-7/+7
Release 0.9.6 - Dec 26 2016 --------------------------- * Fix for table with data but without a header. * Add a warning when the number of series in a chart exceeds Excel's limit of 255. Release 0.9.5 - Dec 24 2016 --------------------------- * Fix for missing `remove_timezone` option in Chart class. Release 0.9.4 - Dec 2 2016 -------------------------- * Added user definable removal of timezones in datetimes. See the :func:`Workbook` constructor option ``remove_timezone`` and :ref:`Timezone Handling in XlsxWriter <timezone_handling>`. * Fix duplicate header warning in :func:`add_table` when there is only one user defined header. * Fix for `center_across` property in :func:`add_format`.
2017-01-02Include xhtml5 too. Ride previous PKGREVISION bumpryoon2-3/+18
2017-01-02Install EPUB and EPUB 3. Bump PKGREVISIONryoon2-4/+23
2017-01-01Revbump after boost updateadam27-54/+54
2017-01-01Updated py-lxml to 3.7.1.wiz2-7/+7
3.7.1 (2016-12-23) ================== * No source changes, issued only to solve problems with the binary packages released for 3.7.0.
2017-01-01Add python-3.6 to incompatible versions.wiz34-68/+68
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-18 01:56:54 +0000