http://rubyforge.org RubyForge Project News Highlights http://rubyforge.org/forum/forum.php?forum_id=41521 mxx_ru/cpp/toolsets/vc11.rb file was added to support Microsoft Visual Studio 2012 C++ compiler. Clang toolsets family added. mxx_ru/cpp/toolsets/clang_linux.rb file was added to support clang compiler on linux platform. Fixed incompatibilities with Ruby 1.9.1 Fixed problem with linkage under some versions of g++: order of used static libs matters even though '-Wl,--start-group' and ' -Wl,--end-group' params ARE used. Fixes at GccFamily toolsets build options: option -fPIC moved from GccFamily to GccUnixFamily toolset options for compatibility with GccMswinFamily. New sample added. Mxx_ru Nicolay Shmakov 2013-06-19T12:07:15+00:00 http://rubyforge.org/forum/forum.php?forum_id=41520 `Update README.rdoc`, pushed by hahahana (h.wang081@gmail.com). View more details for this change at https://github.com/alexdunae/holidays/commit/9e04d8e249f6b1bf3d8a4dfbe1e9323e3ec795dc. Ruby Holidays Gem Alex Dunae 2013-06-18T03:36:08+00:00 http://rubyforge.org/forum/forum.php?forum_id=41507 TZInfo version 1.0.0 and TZInfo::Data version 1.2013.3 have been released (the latter based on version 2013c of IANA Timezone Database). Gem, zip and tar.gz files can be found at http://rubyforge.org/frs/?group_id=894. You can use 'gem update' to upgrade if you already have the tzinfo gem installed. The timezone data previously included with TZInfo as Ruby modules has now been moved to a separate TZInfo::Data library (available as the tzinfo-data gem). TZInfo also now supports using the system zoneinfo files on Linux, Mac OS X and other Unix-like operating systems. If you want to continue using the Ruby timezone modules, or you are using an operating system that does not include zoneinfo files (such as Microsoft Windows), you will need to install TZInfo::Data. This can be done by running: gem install tzinfo-data If TZInfo::Data is installed then TZInfo will use the Ruby timezone modules. Otherwise, it will attempt to find the system zoneinfo files. Please refer to the TZInfo documentation for further information. Changes in this release of TZInfo: * Allow TZInfo to be used with different data sources instead of just the built-in Ruby module data files. * Include a data source that allows TZInfo to load data from the binary zoneinfo files produced by zic and included with many Linux and Unix-like distributions. * Remove the definition and index Ruby modules from TZInfo and move them into a separate TZInfo::Data library (available as the tzinfo-data gem). * Default to using the TZInfo::Data library as the data source if it is installed, otherwise use zoneinfo files instead. * Preserve the nanoseconds of local timezone Time objects when performing conversions (issue #29705). * Don't add the tzinfo lib directory to the search path when requiring 'tzinfo'. The tzinfo lib directory must now be in the search path before 'tzinfo' is required. * Add utc_start_time, utc_end_time, local_start_time and local_end_time instance methods to TimezonePeriod. These return an identical value as the existing utc_start, utc_end, local_start and local_end methods, but return Time instances instead of DateTime. * Make the start_transition, end_transition and offset properties of TimezonePeriod protected. To access properties of the period, callers should use other TimezonePeriod instance methods instead (issue #7655). TZInfo Philip Ross 2013-06-02T05:12:42+00:00 http://rubyforge.org/forum/forum.php?forum_id=41506 icalendar version 1.4.0 has been released! This is a Ruby library for dealing with iCalendar files. Rather than explaining myself, here is the introduction from RFC-2445, which defines the format: The use of calendaring and scheduling has grown considerably in the last decade. Enterprise and inter-enterprise business has become dependent on rapid scheduling of events and actions using this information technology. However, the longer term growth of calendaring and scheduling, is currently limited by the lack of Internet standards for the message content types that are central to these knowledgeware applications. This memo is intended to progress the level of interoperability possible between dissimilar calendaring and scheduling applications. This memo defines a MIME content type for exchanging electronic calendaring and scheduling information. The Internet Calendaring and Scheduling Core Object Specification, or iCalendar, allows for the capture and exchange of information normally stored within a calendaring and scheduling application; such as a Personal Information Manager (PIM) or a Group Scheduling product. The iCalendar format is suitable as an exchange format between applications or systems. The format is defined in terms of a MIME content type. This will enable the object to be exchanged using several transports, including but not limited to SMTP, HTTP, a file system, desktop interactive protocols such as the use of a memory- based clipboard or drag/drop interactions, point-to-point asynchronous communication, wired-network transport, or some form of unwired transport such as infrared might also be used. Changes: ### 1.4.0 2013-05-21 * Implement ACKNOWLEDGED property for VALARM - tsuzuki08 * Output VERSION property as first line after BEGIN:VCALENDAR * Check for unbounded timezone transitions in tzinfo iCalendar Ryan Ahearn 2013-05-21T11:17:45+00:00 http://rubyforge.org/forum/forum.php?forum_id=41505 = BinData is a declarative way to read and write structured binary data. Minory updates for compatability with Ruby 2.0. Source code has been moved to github. Further information at http://github.com/dmendel/bindata BinData Dion Mendel 2013-05-21T11:10:28+00:00 http://rubyforge.org/forum/forum.php?forum_id=41498 "Automatic Ruby" is updated! This is a powerful framework for automation all! This framework can be extended freely by the plug-ins! Installation to put follow command. $ gem install automatic Create your own plug-ins directory by follow command. $ automatic scaffold So, ~/.automatic/plugins/ will be create. Specify any recipe with -c option. $ automatic -c <recipe> Example. $ automatic -c your_recipe.yml If exist ~/.automatic/config/your_recipe.yml, load it. Check the documents! https://github.com/automaticruby/automaticruby/tree/master/doc More info! https://github.com/automaticruby/automaticruby https://rubygems.org/gems/automatic Blog entry (Japanese) http://blog.id774.net/post/ This version in Rubyforge http://rubyforge.org/frs/shownotes.php?release_id=47241 ChangeLog https://github.com/automaticruby/automaticruby/blob/master/doc/ChangeLog Automatic Ruby id 774 2013-05-18T12:28:59+00:00 http://rubyforge.org/forum/forum.php?forum_id=41494 Runt v0.9.0 has been released. This release provides several long overdue fixes for 1.9/2.0 compatibility. Please note that Runt is now hosted on GitHub (https://github.com/mlipper/runt). Runt - Ruby Temporal Expressions Matthew Lipper 2013-05-17T12:11:44+00:00 http://rubyforge.org/forum/forum.php?forum_id=41481 ## kramdown 1.0.2 released This release fixes some bugs; updating is recommended. Some notes: * The [tests page](../tests.html) has been updated to include relative times in the benchmark so that it is possible to better gauge the performance of kramdown (requested by postmodern). * The [kramdown Wiki][1] now contains a listing of libraries that extend kramdown (idea by postmodern). ## Changes * 4 bug fixes - Fixed [GH#51]: Try requiring a parser/converter library based on the specified input/output name (requested by postmodern) - Fixed [GH#49]: Convert non-breaking space to `~` for LaTeX converter (patch by Henning Perl) - Fixed [GH#42]: No more warning for IALs/ALDs/extensions without attributes (reported by DHB) - Fixed [GH#44]: Removed trailing whitespace in link definition for kramdown converter (patch by Marcus Stollsteimer) [1]: https://github.com/gettalong/kramdown/wiki [GH#44]: https://github.com/gettalong/kramdown/pull/44 [GH#42]: https://github.com/gettalong/kramdown/issues/42 [GH#49]: https://github.com/gettalong/kramdown/pull/49 [GH#51]: https://github.com/gettalong/kramdown/issues/51 About kramdown kramdown is a fast, pure-Ruby Markdown-superset converter. kramdown is yet-another-markdown-parser but fast, pure Ruby, using a strict syntax definition and supporting several common extensions. kramdown Thomas Leitner 2013-05-09T06:58:48+00:00 http://rubyforge.org/forum/forum.php?forum_id=41465 mime-types version 1.23 has been released! This library allows for the identification of a file's likely MIME content type. This is release 1.23 that adds the ability to enumerate over the collection of MIME types and updates the sources of a few MIME types. The identification of MIME content type is based on a file's filename extensions. MIME types are used in MIME-compliant communications, as in e-mail or HTTP traffic, to indicate the type of content which is transmitted. MIME::Types provides the ability for detailed information about MIME entities (provided as a set of MIME::Type objects) to be determined and used programmatically. There are many types defined by RFCs and vendors, so the list is long but not complete; don't hesitate to ask to add additional information. This library follows the IANA collection of MIME types (see below for reference). MIME::Types for Ruby was originally based on and synchronized with MIME::Types for Perl by Mark Overmeer, copyright 2001 - 2009. As of version 1.15, the data format for the MIME::Type list has changed and the synchronization will no longer happen. MIME::Types is built to conform to the MIME types of RFCs 2045 and 2231. It follows the official {IANA registry}[http://www.iana.org/assignments/media-types/] ({ftp}[ftp://ftp.iana.org/assignments/media-types]) with some unofficial types added from the the {LTSW collection}[http://www.ltsw.se/knbase/internet/mime.htp]. Changes: ## 1.23 / 2013-04-20 * New Feature: * Arnaud Meuret (ameuret) suggested that it could be useful if the MIME type collection was enumerable, so he implemented it in #30. Thanks for the contribution! https://github.com/halostatue/mime-types/pull/30 * Updated MIME Types: * RFC6910 was adopted (application/call-completion). * RFC6902 was adopted (application/json-patch\+json). * RFC6917 was adopted (application/mrb-consumer\+xml, application/mrb-publish\+xml). * RFC6922 was adopted (application/sql). * RFC2560 is being {updated}[http://tools.ietf.org/html/draft-ietf-pkix-rfc2560bis]. * Administrivia: * The gemspec now includes information about the licenses under which the mime-types gem is available. * Using hoe-gemspec2 instead of hoe-gemspec. mime-types Austin Ziegler 2013-04-21T01:41:43+00:00 http://rubyforge.org/forum/forum.php?forum_id=41464 diff-lcs version 1.2.4 has been released! Diff::LCS computes the difference between two Enumerable sequences using the McIlroy-Hunt longest common subsequence (LCS) algorithm. It includes utilities to create a simple HTML diff output format and a standard diff-like tool. This is release 1.2.4, fixing a bug introduced after diff-lcs 1.1.3 that did not properly prune common sequences at the beginning of a comparison set. Thanks to Paul Kunysch for fixing this issue. Coincident with the release of diff-lcs 1.2.3, we reported an issue with Rubinius in 1.9 mode ({rubinius/rubinius#2268}[https://github.com/rubinius/rubinius/issues/2268]). We are happy to report that this issue has been resolved. Changes: ### 1.2.4 / 2013-04-20 * Bugs fixed: * A bug was introduced after 1.1.3 when pruning common sequences at the start of comparison. Paul Kunysch (@pck) fixed this in pull request 18. Thanks! https://github.com/halostatue/diff-lcs/pull/18 * The Rubinius (1.9 mode) bug in rubinius/rubinius#2268 has been fixed by the Rubinius team two days after it was filed. Thanks for fixing this so quickly! https://github.com/rubinius/rubinius/issues/2268 * Switching to Raggi's hoe-gemspec2 for gemspec generation. diff-lcs Austin Ziegler 2013-04-21T12:08:27+00:00