Rubygems | Latest Versions for mime-typeshttps://rubygems.org/gems2018-08-13T01:45:41Zmime-types (3.2.2)https://rubygems.org/gems/mime-types/versions/3.2.22018-08-13T01:45:40ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
Version 3.0 is a major release that requires Ruby 2.0 compatibility and removes
deprecated functions. The columnar registry format introduced in 2.6 has been
made the primary format; the registry data has been extracted from this library
and put into {mime-types-data}[https://github.com/mime-types/mime-types-data].
Additionally, mime-types is now licensed exclusively under the MIT licence and
there is a code of conduct in effect. There are a number of other smaller
changes described in the History file. mime-types (3.2.1)https://rubygems.org/gems/mime-types/versions/3.2.12018-08-12T18:26:04ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
Version 3.0 is a major release that requires Ruby 2.0 compatibility and removes
deprecated functions. The columnar registry format introduced in 2.6 has been
made the primary format; the registry data has been extracted from this library
and put into {mime-types-data}[https://github.com/mime-types/mime-types-data].
Additionally, mime-types is now licensed exclusively under the MIT licence and
there is a code of conduct in effect. There are a number of other smaller
changes described in the History file. mime-types (3.2)https://rubygems.org/gems/mime-types/versions/3.22018-08-12T16:19:27ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
Version 3.0 is a major release that requires Ruby 2.0 compatibility and removes
deprecated functions. The columnar registry format introduced in 2.6 has been
made the primary format; the registry data has been extracted from this library
and put into {mime-types-data}[https://github.com/mime-types/mime-types-data].
Additionally, mime-types is now licensed exclusively under the MIT licence and
there is a code of conduct in effect. There are a number of other smaller
changes described in the History file. mime-types (3.1)https://rubygems.org/gems/mime-types/versions/3.12016-05-22T21:00:47ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
Version 3.0 is a major release that requires Ruby 2.0 compatibility and removes
deprecated functions. The columnar registry format introduced in 2.6 has been
made the primary format; the registry data has been extracted from this library
and put into {mime-types-data}[https://github.com/mime-types/mime-types-data].
Additionally, mime-types is now licensed exclusively under the MIT licence and
there is a code of conduct in effect. There are a number of other smaller
changes described in the History file. mime-types (3.0)https://rubygems.org/gems/mime-types/versions/3.02015-11-21T15:32:52ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
Version 3.0 is a major release that requires Ruby 2.0 compatibility and removes
deprecated functions. The columnar registry format introduced in 2.6 has been
made the primary format; the registry data has been extracted from this library
and put into {mime-types-data}[https://github.com/mime-types/mime-types-data].
Additionally, mime-types is now licensed exclusively under the MIT licence and
there is a code of conduct in effect. There are a number of other smaller
changes described in the History file. mime-types (2.99.3)https://rubygems.org/gems/mime-types/versions/2.99.32016-09-11T03:24:29ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
This is release 2.99.1, the first scheduled data update for mime-types 2.x. As
of mime-types 2.99. deprecation warnings are noisy and data that has been
deprecated is now no longer available. The data is both dropped from the data
files and is stubbed out as empty or +nil+ values as appropriate.
mime-types-2.6 was the last version of mime-types 2.x with newly available
features, and mime-types 2.99 will only receive quarterly updates to the IANA
registered MIME media types plus any security updates that may be required.
If the loss of the deprecated data matters, be sure to set your dependency
appropriately:
gem &#39;mime-types&#39;, &#39;~&amp;gt; 2.6, &amp;lt; 2.99&#39; mime-types (2.99.2)https://rubygems.org/gems/mime-types/versions/2.99.22016-05-21T16:37:10ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
This is release 2.99.1, the first scheduled data update for mime-types 2.x. As
of mime-types 2.99. deprecation warnings are noisy and data that has been
deprecated is now no longer available. The data is both dropped from the data
files and is stubbed out as empty or +nil+ values as appropriate.
mime-types-2.6 was the last version of mime-types 2.x with newly available
features, and mime-types 2.99 will only receive quarterly updates to the IANA
registered MIME media types plus any security updates that may be required.
If the loss of the deprecated data matters, be sure to set your dependency
appropriately:
gem &#39;mime-types&#39;, &#39;~&amp;gt; 2.6, &amp;lt; 2.99&#39; mime-types (2.99.1)https://rubygems.org/gems/mime-types/versions/2.99.12016-02-22T04:31:13ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
This is release 2.99.1, the first scheduled data update for mime-types 2.x. As
of mime-types 2.99. deprecation warnings are noisy and data that has been
deprecated is now no longer available. The data is both dropped from the data
files and is stubbed out as empty or +nil+ values as appropriate.
mime-types-2.6 was the last version of mime-types 2.x with newly available
features, and mime-types 2.99 will only receive quarterly updates to the IANA
registered MIME media types plus any security updates that may be required.
If the loss of the deprecated data matters, be sure to set your dependency
appropriately:
gem &#39;mime-types&#39;, &#39;~&amp;gt; 2.6, &amp;lt; 2.99&#39; mime-types (2.99)https://rubygems.org/gems/mime-types/versions/2.992015-11-21T15:31:35ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
This is release 2.99, the deprecation version of mime-types 2.x, where
deprecation warnings are noisy and data that has been deprecated is now no
longer available. The data is both dropped from the data files and is stubbed
out as empty or +nil+ values as appropriate.
mime-types-2.6 was the last version of mime-types 2.x with newly available
features, and mime-types 2.99 will only receive quarterly updates to the IANA
registered MIME media types plus any security updates that may be required.
If the loss of the deprecated data matters, be sure to set your dependency
appropriately:
gem &#39;mime-types&#39;, &#39;~&amp;gt; 2.6, &amp;lt; 2.99&#39; mime-types (2.6.2)https://rubygems.org/gems/mime-types/versions/2.6.22015-09-14T03:14:08ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
MIME content types are used in MIME-compliant communications, as in e-mail or
HTTP traffic, to indicate the type of content which is transmitted. The
mime-types library provides the ability for detailed information about MIME
entities (provided as an enumerable collection of MIME::Type objects) to be
determined and used. There are many types defined by RFCs and vendors, so the
list is long but by definition incomplete; don&#39;t hesitate to add additional
type definitions. MIME type definitions found in mime-types are from RFCs, W3C
recommendations, the {IANA Media Types
registry}[https://www.iana.org/assignments/media-types/media-types.xhtml], and
user contributions. It conforms to RFCs 2045 and 2231.
This is release 2.6 with two new experimental features. The first new feature
is a new default registry storage format that greatly reduces the initial
memory use of the mime-types library. This feature is enabled by requiring
+mime/types/columnar+ instead of +mime/types+ with a small performance cost and
no change in *total* memory use if certain methods are called (see {Columnar
Store}[#label-Columnar+Store]). The second new feature is a logger interface
that conforms to the expectations of an ActiveSupport::Logger so that warnings
can be written to an application&#39;s log rather than the default location for
+warn+. This interface may be used for other logging purposes in the future.
mime-types 2.6 is the last planned version of mime-types 2.x, so deprecation
warnings are no longer cached but provided every time the method is called.
mime-types 2.6 supports Ruby 1.9.2 or later. mime-types (2.6.1)https://rubygems.org/gems/mime-types/versions/2.6.12015-05-25T19:02:58ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
MIME content types are used in MIME-compliant communications, as in e-mail or
HTTP traffic, to indicate the type of content which is transmitted. The
mime-types library provides the ability for detailed information about MIME
entities (provided as an enumerable collection of MIME::Type objects) to be
determined and used. There are many types defined by RFCs and vendors, so the
list is long but by definition incomplete; don&#39;t hesitate to add additional
type definitions. MIME type definitions found in mime-types are from RFCs, W3C
recommendations, the {IANA Media Types
registry}[https://www.iana.org/assignments/media-types/media-types.xhtml], and
user contributions. It conforms to RFCs 2045 and 2231.
This is release 2.6 with two new experimental features. The first new feature
is a new default registry storage format that greatly reduces the initial
memory use of the mime-types library. This feature is enabled by requiring
+mime/types/columnar+ instead of +mime/types+ with a small performance cost and
no change in *total* memory use if certain methods are called (see {Columnar
Store}[#columnar-store] for more details). The second new feature is a logger
interface that conforms to the expectations of an ActiveSupport::Logger so that
warnings can be written to an application&#39;s log rather than the default
location for +warn+. This interface may be used for other logging purposes in
the future.
mime-types 2.6 is the last planned version of mime-types 2.x, so deprecation
warnings are no longer cached but provided every time the method is called.
mime-types 2.6 supports Ruby 1.9.2 or later. mime-types (2.6)https://rubygems.org/gems/mime-types/versions/2.62015-05-25T17:49:02ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
MIME content types are used in MIME-compliant communications, as in e-mail or
HTTP traffic, to indicate the type of content which is transmitted. The
mime-types library provides the ability for detailed information about MIME
entities (provided as an enumerable collection of MIME::Type objects) to be
determined and used. There are many types defined by RFCs and vendors, so the
list is long but by definition incomplete; don&#39;t hesitate to add additional
type definitions. MIME type definitions found in mime-types are from RFCs, W3C
recommendations, the {IANA Media Types
registry}[https://www.iana.org/assignments/media-types/media-types.xhtml], and
user contributions. It conforms to RFCs 2045 and 2231.
This is release 2.6 with two new experimental features. The first new feature
is a new default registry storage format that greatly reduces the initial
memory use of the mime-types library. This feature is enabled by requiring
+mime/types/columnar+ instead of +mime/types+ with a small performance cost and
no change in *total* memory use if certain methods are called (see {Columnar
Store}[#columnar-store] for more details). The second new feature is a logger
interface that conforms to the expectations of an ActiveSupport::Logger so that
warnings can be written to an application&#39;s log rather than the default
location for +warn+. This interface may be used for other logging purposes in
the future.
mime-types 2.6 is the last planned version of mime-types 2.x, so deprecation
warnings are no longer cached but provided every time the method is called.
mime-types 2.6 supports Ruby 1.9.2 or later. mime-types (2.5)https://rubygems.org/gems/mime-types/versions/2.52015-04-25T05:00:43ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
MIME content types are used in MIME-compliant communications, as in e-mail or
HTTP traffic, to indicate the type of content which is transmitted. The
mime-types library provides the ability for detailed information about MIME
entities (provided as an enumerable collection 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 by definition incomplete; don&#39;t hesitate to
add additional type definitions (see Contributing.rdoc). The primary sources
for MIME type definitions found in mime-types is the
{IANA Media Types registry}[https://www.iana.org/assignments/media-types/media-types.xhtml],
RFCs, and W3C recommendations. It conforms to RFCs 2045 and 2231.
This is release 2.5 with a couple of bug fixes, updating to the latest IANA
type registry, and adding a user-contributed type. mime-types 2.x supports Ruby
1.9.2 or later. mime-types (2.4.3)https://rubygems.org/gems/mime-types/versions/2.4.32014-10-21T14:36:33ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
MIME content types are used in MIME-compliant communications, as in e-mail or
HTTP traffic, to indicate the type of content which is transmitted. The
mime-types library provides the ability for detailed information about MIME
entities (provided as an enumerable collection 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 by definition incomplete; don&#39;t hesitate to to
add additional type definitions (see Contributing.rdoc). The primary sources
for MIME type definitions found in mime-types is the IANA collection of
registrations (see below for the link), RFCs, and W3C recommendations.
This is release 2.4.3, restoring full compatibility with Ruby 1.9.2 (which will
be dropped in mime-types 3.0). It also includes the performance improvements
from mime-types 2.4.2 (since yanked because of the broken Ruby 1.9.2 support)
and the 2.4.1 fix of a bug in observed use of the mime-types library where
extensions were not previously sorted, such that
MIME::Types.of(&#39;image.jpg&#39;).first.extensions.first
returned a value of +jpeg+ in mime-types 1, but +jpe+ in mime-types 2. This was
introduced because extensions were sorted during assignment
(MIME::Type#extensions=). This behaviour has been reverted to protect clients
that work as noted above. The preferred way to express this is the new method:
MIME::Type.of(&#39;image.jpg&#39;).first.preferred_extension
Łukasz Śliwa created the
{friendly_mime}[https://github.com/lukaszsliwa/friendly_mime] gem, which offers
friendly descriptive names for MIME types. This functionality and
English-language data has been added to mime-types as MIME::Type#friendly. To
make it easy for internationalization, MIME::Type#i18n_key has been added,
which will return a key suitable for use with the
{I18n}[https://github.com/svenfuchs/i18n] library.
As a reminder, mime-types 2.x is no longer compatible with Ruby 1.8 and
mime-types 1.x is only being maintained for security issues. No new MIME types
or features will be added.
mime-types (previously called MIME::Types for Ruby) was originally based on
MIME::Types for Perl by Mark Overmeer, copyright 2001 - 2009. It is built to
conform to the MIME types of RFCs 2045 and 2231. It tracks the {IANA Media
Types registry}[https://www.iana.org/assignments/media-types/media-types.xhtml]
with some types added by the users of mime-types. mime-types (2.4.2)https://rubygems.org/gems/mime-types/versions/2.4.22014-10-15T21:16:16ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
MIME content types are used in MIME-compliant communications, as in e-mail or
HTTP traffic, to indicate the type of content which is transmitted. The
mime-types library provides the ability for detailed information about MIME
entities (provided as an enumerable collection 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 by definition incomplete; don&#39;t hesitate to to
add additional type definitions (see Contributing.rdoc). The primary sources
for MIME type definitions found in mime-types is the IANA collection of
registrations (see below for the link), RFCs, and W3C recommendations.
This is release 2.4.2, fixing bugs with unnecessary object duplication and
using JSON.parse instead of JSON.load. These fixes improve the JSON registry
loading time by about 55% over previous 2.x releases. Cached registry load
times are not changed. This release builds on the 2.4.1 release, which fixed a
bug in observed use of the mime-types library where extensions were not
previously sorted, such that
MIME::Types.of(&#39;image.jpg&#39;).first.extensions.first
returned a value of +jpeg+ in mime-types 1, but +jpe+ in mime-types 2. This was
introduced because extensions were sorted during assignment
(MIME::Type#extensions=). This behaviour has been reverted to protect clients
that work as noted above. The preferred way to express this is the new method:
MIME::Type.of(&#39;image.jpg&#39;).first.preferred_extension
Łukasz Śliwa created the
{friendly_mime}[https://github.com/lukaszsliwa/friendly_mime] gem, which offers
friendly descriptive names for MIME types. This functionality and
English-language data has been added to mime-types as MIME::Type#friendly. To
make it easy for internationalization, MIME::Type#i18n_key has been added,
which will return a key suitable for use with the
{I18n}[https://github.com/svenfuchs/i18n] library.
As a reminder, mime-types 2.x is no longer compatible with Ruby 1.8 and
mime-types 1.x is only being maintained for security issues. No new MIME types
or features will be added.
mime-types (previously called MIME::Types for Ruby) was originally based on
MIME::Types for Perl by Mark Overmeer, copyright 2001 - 2009. It is built to
conform to the MIME types of RFCs 2045 and 2231. It tracks the {IANA Media
Types registry}[https://www.iana.org/assignments/media-types/media-types.xhtml]
with some types added by the users of mime-types. mime-types (2.4.1)https://rubygems.org/gems/mime-types/versions/2.4.12014-10-07T17:49:34ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
MIME content types are used in MIME-compliant communications, as in e-mail or
HTTP traffic, to indicate the type of content which is transmitted. The
mime-types library provides the ability for detailed information about MIME
entities (provided as an enumerable collection 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 by definition incomplete; don&#39;t hesitate to to
add additional type definitions (see Contributing.rdoc). The primary sources
for MIME type definitions found in mime-types is the IANA collection of
registrations (see below for the link), RFCs, and W3C recommendations.
This is release 2.4.1 (2.4 was pulled), fixing a bug in observed use of the
mime-types library where extensions were not previously sorted, such that
MIME::Types.of(&#39;image.jpg&#39;).first.extensions.first
returned a value of +jpeg+ in mime-types 1, but +jpe+ in mime-types 2. This was
introduced because extensions were sorted during assignment
(MIME::Type#extensions=). This behaviour has been reverted to protect clients
that work as noted above. The preferred way to express this is the new method:
MIME::Type.of(&#39;image.jpg&#39;).first.preferred_extension
Łukasz Śliwa created the
{friendly_mime}[https://github.com/lukaszsliwa/friendly_mime] gem, which offers
friendly descriptive names for MIME types. This functionality and
English-language data has been added to mime-types as MIME::Type#friendly. To
make it easy for internationalization, MIME::Type#i18n_key has been added,
which will return a key suitable for use with the
{I18n}[https://github.com/svenfuchs/i18n] library.
As a reminder, mime-types 2.x is no longer compatible with Ruby 1.8 and
mime-types 1.x is only being maintained for security issues. No new MIME types
or features will be added.
mime-types (previously called MIME::Types for Ruby) was originally based on
MIME::Types for Perl by Mark Overmeer, copyright 2001 - 2009. It is built to
conform to the MIME types of RFCs 2045 and 2231. It tracks the {IANA Media
Types registry}[https://www.iana.org/assignments/media-types/media-types.xhtml]
with some types added by the users of mime-types. mime-types (2.4)https://rubygems.org/gems/mime-types/versions/2.42014-10-07T05:28:22ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
MIME content types are used in MIME-compliant communications, as in e-mail or
HTTP traffic, to indicate the type of content which is transmitted. The
mime-types library provides the ability for detailed information about MIME
entities (provided as an enumerable collection 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 by definition incomplete; don&#39;t hesitate to to
add additional type definitions (see Contributing.rdoc). The primary sources
for MIME type definitions found in mime-types is the IANA collection of
registrations (see below for the link), RFCs, and W3C recommendations.
This is release 2.2, mostly changing how the MIME type registry is updated from
the IANA registry (the format of which was incompatibly changed shortly before
this release) and taking advantage of the extra data available from IANA
registry in the form of MIME::Type#xrefs. In addition, the {LTSW
list}[http://www.ltsw.se/knbase/internet/mime.htp] has been dropped as a
supported list.
As a reminder, mime-types 2.x is no longer compatible with Ruby 1.8 and
mime-types 1.x is only being maintained for security issues. No new MIME types
or features will be added.
mime-types (previously called MIME::Types for Ruby) was originally based on
MIME::Types for Perl by Mark Overmeer, copyright 2001 - 2009. It is built to
conform to the MIME types of RFCs 2045 and 2231. It tracks the {IANA Media
Types registry}[https://www.iana.org/assignments/media-types/media-types.xhtml]
with some types added by the users of mime-types. mime-types (2.3)https://rubygems.org/gems/mime-types/versions/2.32014-05-23T03:30:23ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
MIME content types are used in MIME-compliant communications, as in e-mail or
HTTP traffic, to indicate the type of content which is transmitted. The
mime-types library provides the ability for detailed information about MIME
entities (provided as an enumerable collection 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 by definition incomplete; don&#39;t hesitate to to
add additional type definitions (see Contributing.rdoc). The primary sources
for MIME type definitions found in mime-types is the IANA collection of
registrations (see below for the link), RFCs, and W3C recommendations.
This is release 2.2, mostly changing how the MIME type registry is updated from
the IANA registry (the format of which was incompatibly changed shortly before
this release) and taking advantage of the extra data available from IANA
registry in the form of MIME::Type#xrefs. In addition, the {LTSW
list}[http://www.ltsw.se/knbase/internet/mime.htp] has been dropped as a
supported list.
As a reminder, mime-types 2.x is no longer compatible with Ruby 1.8 and
mime-types 1.x is only being maintained for security issues. No new MIME types
or features will be added.
mime-types (previously called MIME::Types for Ruby) was originally based on
MIME::Types for Perl by Mark Overmeer, copyright 2001 - 2009. It is built to
conform to the MIME types of RFCs 2045 and 2231. It tracks the {IANA Media
Types registry}[https://www.iana.org/assignments/media-types/media-types.xhtml]
with some types added by the users of mime-types. mime-types (2.2)https://rubygems.org/gems/mime-types/versions/2.22014-03-14T04:23:16ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
MIME content types are used in MIME-compliant communications, as in e-mail or
HTTP traffic, to indicate the type of content which is transmitted. The
mime-types library provides the ability for detailed information about MIME
entities (provided as an enumerable collection 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 by definition incomplete; don&#39;t hesitate to to
add additional type definitions (see Contributing.rdoc). The primary sources
for MIME type definitions found in mime-types is the IANA collection of
registrations (see below for the link), RFCs, and W3C recommendations.
This is release 2.2,
mostly changing how the MIME type registry is updated from
the IANA registry (the format of which was incompatibly changed shortly before
this release) and taking advantage of the extra data available from IANA
registry in the form of MIME::Type#xrefs. In addition, the {LTSW
list}[http://www.ltsw.se/knbase/internet/mime.htp] has been dropped as a
supported list.
As a reminder, mime-types 2.x is no longer compatible with Ruby 1.8 and
mime-types 1.x is only being maintained for security issues. No new MIME types
or features will be added.
mime-types (previously called MIME::Types for Ruby) was originally based on
MIME::Types for Perl by Mark Overmeer, copyright 2001 - 2009. It is built to
conform to the MIME types of RFCs 2045 and 2231. It tracks the {IANA Media
Types registry}[https://www.iana.org/assignments/media-types/media-types.xhtml]
with some types added by the users of mime-types. mime-types (2.1)https://rubygems.org/gems/mime-types/versions/2.12014-01-26T04:26:11ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
MIME content types are used in MIME-compliant communications, as in e-mail or
HTTP traffic, to indicate the type of content which is transmitted. The
mime-types library provides the ability for detailed information about MIME
entities (provided as an enumerable collection 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 by definition incomplete; don&#39;t hesitate to to
add additional type definitions (see Contributing.rdoc). The primary sources
for MIME type definitions found in mime-types is the IANA collection of
registrations (see below for the link), RFCs, and W3C recommendations.
This is release 2.1, mostly changing how the MIME type registry is updated from
the IANA registry (the format of which was incompatibly changed shortly before
this release) and taking advantage of the extra data available from IANA
registry in the form of MIME::Type#xrefs. In addition, the {LTSW
list}[http://www.ltsw.se/knbase/internet/mime.htp] has been dropped as a
supported list.
As a reminder, mime-types 2.x is no longer compatible with Ruby 1.8 and
mime-types 1.x is only being maintained for security issues. No new MIME types
or features will be added.
mime-types (previously called MIME::Types for Ruby) was originally based on
MIME::Types for Perl by Mark Overmeer, copyright 2001 - 2009. It is built to
conform to the MIME types of RFCs 2045 and 2231. It tracks the {IANA Media
Types registry}[https://www.iana.org/assignments/media-types/media-types.xhtml]
with some types added by the users of mime-types. mime-types (2.0)https://rubygems.org/gems/mime-types/versions/2.02013-10-28T00:26:54ZAustin ZieglerThe mime-types library provides a library and registry for information about MIME content type definitions
The mime-types library provides a library and registry for information about
MIME content type definitions. It can be used to determine defined filename
extensions for MIME types, or to use filename extensions to look up the likely
MIME type definitions.
MIME content types are used in MIME-compliant communications, as in e-mail or
HTTP traffic, to indicate the type of content which is transmitted. The
mime-types library provides the ability for detailed information about MIME
entities (provided as an enumerable collection 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 by definition incomplete; don&#39;t hesitate to to
add additional type definitions (see Contributing.rdoc). The primary sources
for MIME type definitions found in mime-types is the IANA collection of
registrations (see below for the link), RFCs, and W3C recommendations.
The mime-types library uses semantic versioning. This is release 2.0; there are
incompatible changes in the API provided by mime-types, mostly around registry
initialization (see History.rdoc for full details), and the removal of support
for Ruby 1.8 interpreters.
mime-types (previously called MIME::Types for Ruby) was originally based on
MIME::Types for Perl by Mark Overmeer, copyright 2001 - 2009. It is built to
conform to the MIME types of RFCs 2045 and 2231. It tracks the {IANA
registry}[http://www.iana.org/assignments/media-types/]
({ftp}[ftp://ftp.iana.org/assignments/media-types]) with some unofficial types
added from the {LTSW collection}[http://www.ltsw.se/knbase/internet/mime.htp]
and added by the users of mime-types. mime-types (1.25.1)https://rubygems.org/gems/mime-types/versions/1.25.12013-11-24T22:58:58ZAustin ZieglerThis library allows for the identification of a file's likely MIME content type
This library allows for the identification of a file&#39;s likely MIME content
type. This is release 1.25.1, fixing an issue with priority comparison for
mime-types 1.x. The current release is 2.0, which only supports Ruby 1.9 or
later.
Release 1.25.1 contains all features of 1.25, including the experimental
caching and lazy loading functionality. The caching and lazy loading features
were initially implemented by Greg Brockman (gdb). As these features are
experimental, they are disabled by default and must be enabled through the use
of environment variables. The cache is invalidated on a per-version basis; the
cache for version 1.25 will not be reused for any later version.
To use lazy loading, set the environment variable +RUBY_MIME_TYPES_LAZY_LOAD+
to any value other than &#39;false&#39;. When using lazy loading, the initial startup
of MIME::Types is around 12–25× faster than normal startup (on my system,
normal startup is about 90 ms; lazy startup is about 4 ms). This isn&#39;t
generally useful, however, as the MIME::Types database has not been loaded.
Lazy startup and load is just *slightly* faster—around 1 ms. The real advantage
comes from using the cache.
To enable the cache, set the environment variable +RUBY_MIME_TYPES_CACHE+ to a
filename where MIME::Types will have read-write access. The first time a new
version of MIME::Types is run using this file, it will be created, taking a
little longer than normal. Subsequent loads using the same cache file will be
approximately 3½× faster (25 ms) than normal loads. This can be combined with
+RUBY_MIME_TYPES_LAZY_LOAD+, but this is *not* recommended in a multithreaded
or multiprocess environment where all threads or processes will be using the
same cache file.
As the caching interface is still experimental, the only values cached are the
default MIME::Types database, not any custom MIME::Types added by users.
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&#39;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 MIME::Types for Perl by Mark
Overmeer, copyright 2001 - 2009.
MIME::Types is built to conform to the MIME types of RFCs 2045 and 2231. It
tracks the {IANA registry}[http://www.iana.org/assignments/media-types/]
({ftp}[ftp://ftp.iana.org/assignments/media-types]) with some unofficial types
added from the {LTSW collection}[http://www.ltsw.se/knbase/internet/mime.htp]
and added by the users of MIME::Types. mime-types (1.25)https://rubygems.org/gems/mime-types/versions/1.252013-08-30T16:25:21ZAustin ZieglerThis library allows for the identification of a file's likely MIME content type
This library allows for the identification of a file&#39;s likely MIME content
type. This is release 1.25, adding experimental caching and lazy loading
functionality.
The caching and lazy loading features were initially implemented by Greg
Brockman (gdb). As these features are experimental, they are disabled by
default and must be enabled through the use of environment variables. The cache
is invalidated on a per-version basis; the cache for version 1.25 will not be
reused for version 1.26.
To use lazy loading, set the environment variable +RUBY_MIME_TYPES_LAZY_LOAD+
to any value other than &#39;false&#39;. When using lazy loading, the initial startup
of MIME::Types is around 12–25× faster than normal startup (on my system,
normal startup is about 90 ms; lazy startup is about 4 ms). This isn&#39;t
generally useful, however, as the MIME::Types database has not been loaded.
Lazy startup and load is just *slightly* faster—around 1 ms. The real advantage
comes from using the cache.
To enable the cache, set the environment variable +RUBY_MIME_TYPES_CACHE+ to a
filename where MIME::Types will have read-write access. The first time a new
version of MIME::Types is run using this file, it will be created, taking a
little longer than normal. Subsequent loads using the same cache file will be
approximately 3½× faster (25 ms) than normal loads. This can be combined with
+RUBY_MIME_TYPES_LAZY_LOAD+, but this is *not* recommended in a multithreaded
or multiprocess environment where all threads or processes will be using the
same cache file.
As the caching interface is still experimental, the only values cached are the
default MIME::Types database, not any custom MIME::Types added by users.
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&#39;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 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
tracks the {IANA registry}[http://www.iana.org/assignments/media-types/]
({ftp}[ftp://ftp.iana.org/assignments/media-types]) with some unofficial types
added from the {LTSW collection}[http://www.ltsw.se/knbase/internet/mime.htp]
and added by the users of MIME::Types. mime-types (1.24)https://rubygems.org/gems/mime-types/versions/1.242013-08-14T22:05:09ZAustin ZieglerThis library allows for the identification of a file's likely MIME content type
This library allows for the identification of a file&#39;s likely MIME content
type. This is release 1.24, adding and updating a few MIME types and fixing
some issues with documentation.
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&#39;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 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
tracks the {IANA registry}[http://www.iana.org/assignments/media-types/]
({ftp}[ftp://ftp.iana.org/assignments/media-types]) with some unofficial types
added from the {LTSW collection}[http://www.ltsw.se/knbase/internet/mime.htp]
and added by the users of MIME::Types. mime-types (1.23)https://rubygems.org/gems/mime-types/versions/1.232013-04-21T01:41:18ZAustin ZieglerThis library allows for the identification of a file's likely MIME content type
This library allows for the identification of a file&#39;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&#39;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&#39;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]. mime-types (1.22)https://rubygems.org/gems/mime-types/versions/1.222013-03-30T22:07:18ZAustin ZieglerThis library allows for the identification of a file's likely MIME content type
This library allows for the identification of a file&#39;s likely MIME content
type. This is release 1.22 with new MIME types. The identification of MIME
content type is based on a file&#39;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&#39;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]. mime-types (1.21)https://rubygems.org/gems/mime-types/versions/1.212013-02-09T16:42:37ZAustin ZieglerThis library allows for the identification of a file's likely MIME content type
This library allows for the identification of a file&#39;s likely MIME content
type. This is release 1.21 with new MIME types. The identification of MIME
content type is based on a file&#39;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&#39;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]. mime-types (1.20.1)https://rubygems.org/gems/mime-types/versions/1.20.12013-02-04T04:02:53ZAustin ZieglerThis library allows for the identification of a file's likely MIME content type
This library allows for the identification of a file&#39;s likely MIME content
type. This is release 1.20.1 with new MIME types. The identification of MIME
content type is based on a file&#39;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&#39;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]. mime-types (1.20)https://rubygems.org/gems/mime-types/versions/1.202013-02-04T03:56:52ZAustin ZieglerThis library allows for the identification of a file's likely MIME content type
This library allows for the identification of a file&#39;s likely MIME content
type. This is release 1.20 with new MIME types. The identification of MIME
content type is based on a file&#39;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&#39;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]. mime-types (1.19)https://rubygems.org/gems/mime-types/versions/1.192012-06-21T02:50:39ZAustin ZieglerThis library allows for the identification of a file's likely MIME content type
This library allows for the identification of a file&#39;s likely MIME content
type. This is release 1.19 with new MIME types. The identification of MIME
content type is based on a file&#39;s filename extensions.
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.
:include: Licence.rdoc mime-types (1.18)https://rubygems.org/gems/mime-types/versions/1.182012-03-21T02:05:14ZAustin ZieglerThis library allows for the identification of a file's likely MIME content type
This library allows for the identification of a file&#39;s likely MIME content
type. This is release 1.17.2. The identification of MIME content type is based
on a file&#39;s filename extensions.
MIME::Types for Ruby 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.
:include: Licence.rdoc mime-types (1.17.2)https://rubygems.org/gems/mime-types/versions/1.17.22011-10-26T04:10:56ZAustin ZieglerThis library allows for the identification of a file's likely MIME content type
This library allows for the identification of a file&#39;s likely MIME content
type. This is release 1.17.2. The identification of MIME content type is based
on a file&#39;s filename extensions.
MIME::Types for Ruby 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.
Homepage:: http://mime-types.rubyforge.org/
GitHub:: http://github.com/halostatue/mime-types/
Copyright:: 2002 - 2011, Austin Ziegler
Based in part on prior work copyright Mark Overmeer
:include: License.rdoc mime-types (1.17.1)https://rubygems.org/gems/mime-types/versions/1.17.12011-10-24T03:35:59ZAustin ZieglerThis library allows for the identification of a file's likely MIME content type
This library allows for the identification of a file&#39;s likely MIME content
type. This is release 1.17.1. The identification of MIME content type is based
on a file&#39;s filename extensions.
MIME::Types for Ruby 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.
Homepage:: http://mime-types.rubyforge.org/
GitHub:: http://github.com/halostatue/mime-types/
Copyright:: 2002 - 2011, Austin Ziegler
Based in part on prior work copyright Mark Overmeer
:include: License.rdoc mime-types (1.17)https://rubygems.org/gems/mime-types/versions/1.172011-10-24T03:31:20ZAustin ZieglerThis library allows for the identification of a file's likely MIME content type
This library allows for the identification of a file&#39;s likely MIME content
type. This is release 1.17. The identification of MIME content type is based
on a file&#39;s filename extensions.
MIME::Types for Ruby 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.
Homepage:: http://mime-types.rubyforge.org/
GitHub:: http://github.com/halostatue/mime-types/
Copyright:: 2002 - 2011, Austin Ziegler
Based in part on prior work copyright Mark Overmeer
:include: License.rdoc mime-types (1.16)https://rubygems.org/gems/mime-types/versions/1.162009-07-25T18:07:15ZAustin ZieglerManages a MIME Content-Type database that will return the Content-Type for a given filename.
MIME::Types for Ruby 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 (1.15)https://rubygems.org/gems/mime-types/versions/1.152009-07-25T18:07:16ZAustin ZieglerManages a MIME Content-Type that will return the Content-Type for a given filename.
This library allows for the identification of a file&#39;s likely MIME content type. This is release 1.15. The identification of MIME content type is based on a file&#39;s filename extensions.