mime-types-data 3.2024.1203 → 3.2025.0204
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/{History.md → CHANGELOG.md} +34 -0
- data/CONTRIBUTING.md +150 -0
- data/CONTRIBUTORS.md +53 -0
- data/{Licence.md → LICENCE.md} +1 -1
- data/Manifest.txt +5 -19
- data/README.md +31 -30
- data/Rakefile +40 -116
- data/SECURITY.md +1 -1
- data/data/mime-types.json +1 -1
- data/data/mime.content_type.column +12 -0
- data/data/mime.docs.column +12 -0
- data/data/mime.encoding.column +12 -0
- data/data/mime.flags.column +12 -0
- data/data/mime.friendly.column +12 -0
- data/data/mime.pext.column +12 -0
- data/data/mime.use_instead.column +12 -0
- data/data/mime.xrefs.column +47 -35
- data/lib/mime/types/data.rb +1 -1
- metadata +18 -89
- data/Contributing.md +0 -203
- data/types/application.yaml +0 -19098
- data/types/audio.yaml +0 -1753
- data/types/chemical.yaml +0 -71
- data/types/conference.yaml +0 -9
- data/types/drawing.yaml +0 -15
- data/types/example.yaml +0 -1
- data/types/font.yaml +0 -65
- data/types/haptics.yaml +0 -28
- data/types/image.yaml +0 -1329
- data/types/message.yaml +0 -247
- data/types/model.yaml +0 -454
- data/types/multipart.yaml +0 -187
- data/types/text.yaml +0 -1281
- data/types/video.yaml +0 -1158
- data/types/world.yaml +0 -8
- /data/{Code-of-Conduct.md → CODE_OF_CONDUCT.md} +0 -0
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: mime-types-data
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 3.
|
4
|
+
version: 3.2025.0204
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Austin Ziegler
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date:
|
11
|
+
date: 2025-02-05 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: hoe
|
@@ -25,49 +25,7 @@ dependencies:
|
|
25
25
|
- !ruby/object:Gem::Version
|
26
26
|
version: '4.0'
|
27
27
|
- !ruby/object:Gem::Dependency
|
28
|
-
name: hoe-
|
29
|
-
requirement: !ruby/object:Gem::Requirement
|
30
|
-
requirements:
|
31
|
-
- - "~>"
|
32
|
-
- !ruby/object:Gem::Version
|
33
|
-
version: '1.0'
|
34
|
-
type: :development
|
35
|
-
prerelease: false
|
36
|
-
version_requirements: !ruby/object:Gem::Requirement
|
37
|
-
requirements:
|
38
|
-
- - "~>"
|
39
|
-
- !ruby/object:Gem::Version
|
40
|
-
version: '1.0'
|
41
|
-
- !ruby/object:Gem::Dependency
|
42
|
-
name: hoe-gemspec2
|
43
|
-
requirement: !ruby/object:Gem::Requirement
|
44
|
-
requirements:
|
45
|
-
- - "~>"
|
46
|
-
- !ruby/object:Gem::Version
|
47
|
-
version: '1.1'
|
48
|
-
type: :development
|
49
|
-
prerelease: false
|
50
|
-
version_requirements: !ruby/object:Gem::Requirement
|
51
|
-
requirements:
|
52
|
-
- - "~>"
|
53
|
-
- !ruby/object:Gem::Version
|
54
|
-
version: '1.1'
|
55
|
-
- !ruby/object:Gem::Dependency
|
56
|
-
name: hoe-git2
|
57
|
-
requirement: !ruby/object:Gem::Requirement
|
58
|
-
requirements:
|
59
|
-
- - "~>"
|
60
|
-
- !ruby/object:Gem::Version
|
61
|
-
version: '1.7'
|
62
|
-
type: :development
|
63
|
-
prerelease: false
|
64
|
-
version_requirements: !ruby/object:Gem::Requirement
|
65
|
-
requirements:
|
66
|
-
- - "~>"
|
67
|
-
- !ruby/object:Gem::Version
|
68
|
-
version: '1.7'
|
69
|
-
- !ruby/object:Gem::Dependency
|
70
|
-
name: hoe-rubygems
|
28
|
+
name: hoe-halostatue
|
71
29
|
requirement: !ruby/object:Gem::Requirement
|
72
30
|
requirements:
|
73
31
|
- - "~>"
|
@@ -148,26 +106,6 @@ dependencies:
|
|
148
106
|
- - "~>"
|
149
107
|
- !ruby/object:Gem::Version
|
150
108
|
version: '1.0'
|
151
|
-
- !ruby/object:Gem::Dependency
|
152
|
-
name: rdoc
|
153
|
-
requirement: !ruby/object:Gem::Requirement
|
154
|
-
requirements:
|
155
|
-
- - ">="
|
156
|
-
- !ruby/object:Gem::Version
|
157
|
-
version: '4.0'
|
158
|
-
- - "<"
|
159
|
-
- !ruby/object:Gem::Version
|
160
|
-
version: '7'
|
161
|
-
type: :development
|
162
|
-
prerelease: false
|
163
|
-
version_requirements: !ruby/object:Gem::Requirement
|
164
|
-
requirements:
|
165
|
-
- - ">="
|
166
|
-
- !ruby/object:Gem::Version
|
167
|
-
version: '4.0'
|
168
|
-
- - "<"
|
169
|
-
- !ruby/object:Gem::Version
|
170
|
-
version: '7'
|
171
109
|
description: |-
|
172
110
|
mime-types-data provides a registry for information about MIME media type
|
173
111
|
definitions. It can be used with the Ruby mime-types library or other software
|
@@ -178,18 +116,20 @@ email:
|
|
178
116
|
executables: []
|
179
117
|
extensions: []
|
180
118
|
extra_rdoc_files:
|
181
|
-
-
|
182
|
-
-
|
183
|
-
-
|
184
|
-
-
|
119
|
+
- CHANGELOG.md
|
120
|
+
- CODE_OF_CONDUCT.md
|
121
|
+
- CONTRIBUTING.md
|
122
|
+
- CONTRIBUTORS.md
|
123
|
+
- LICENCE.md
|
185
124
|
- Manifest.txt
|
186
125
|
- README.md
|
187
126
|
- SECURITY.md
|
188
127
|
files:
|
189
|
-
-
|
190
|
-
-
|
191
|
-
-
|
192
|
-
-
|
128
|
+
- CHANGELOG.md
|
129
|
+
- CODE_OF_CONDUCT.md
|
130
|
+
- CONTRIBUTING.md
|
131
|
+
- CONTRIBUTORS.md
|
132
|
+
- LICENCE.md
|
193
133
|
- Manifest.txt
|
194
134
|
- README.md
|
195
135
|
- Rakefile
|
@@ -207,25 +147,14 @@ files:
|
|
207
147
|
- data/mime.xrefs.column
|
208
148
|
- lib/mime-types-data.rb
|
209
149
|
- lib/mime/types/data.rb
|
210
|
-
- types/application.yaml
|
211
|
-
- types/audio.yaml
|
212
|
-
- types/chemical.yaml
|
213
|
-
- types/conference.yaml
|
214
|
-
- types/drawing.yaml
|
215
|
-
- types/example.yaml
|
216
|
-
- types/font.yaml
|
217
|
-
- types/haptics.yaml
|
218
|
-
- types/image.yaml
|
219
|
-
- types/message.yaml
|
220
|
-
- types/model.yaml
|
221
|
-
- types/multipart.yaml
|
222
|
-
- types/text.yaml
|
223
|
-
- types/video.yaml
|
224
|
-
- types/world.yaml
|
225
150
|
homepage: https://github.com/mime-types/mime-types-data/
|
226
151
|
licenses:
|
227
152
|
- MIT
|
228
153
|
metadata:
|
154
|
+
homepage_uri: https://github.com/mime-types/mime-types-data/
|
155
|
+
bug_tracker_uri: https://github.com/mime-types/mime-types-data/issues
|
156
|
+
source_code_uri: https://github.com/mime-types/mime-types-data/
|
157
|
+
changelog_uri: https://github.com/mime-types/mime-types-data/blob/main/CHANGELOG.md
|
229
158
|
rubygems_mfa_required: 'true'
|
230
159
|
post_install_message:
|
231
160
|
rdoc_options:
|
@@ -244,7 +173,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
244
173
|
- !ruby/object:Gem::Version
|
245
174
|
version: '0'
|
246
175
|
requirements: []
|
247
|
-
rubygems_version: 3.5.
|
176
|
+
rubygems_version: 3.5.22
|
248
177
|
signing_key:
|
249
178
|
specification_version: 4
|
250
179
|
summary: mime-types-data provides a registry for information about MIME media type
|
data/Contributing.md
DELETED
@@ -1,203 +0,0 @@
|
|
1
|
-
# Contributing
|
2
|
-
|
3
|
-
Contributions to mime-types-data is encouraged in any form: a bug report, new
|
4
|
-
MIME type definitions, or additional code to help manage the MIME types. As with
|
5
|
-
many of my projects, I have a few suggestions for improving the chance of
|
6
|
-
acceptance of your code contributions:
|
7
|
-
|
8
|
-
- The support files are written in Ruby and should remain in the coding style
|
9
|
-
that already exists, and I use hoe for releasing the mime-types-data RubyGem.
|
10
|
-
- Use a thoughtfully-named topic branch that contains your change. Rebase your
|
11
|
-
commits into logical chunks as necessary.
|
12
|
-
- Use [quality commit messages][qcm].
|
13
|
-
- Do not change the version number; when your patch is accepted and a release is
|
14
|
-
made, the version will be updated at that point.
|
15
|
-
- Submit a GitHub pull request with your changes.
|
16
|
-
- New or changed behaviours require new or updated documentation.
|
17
|
-
|
18
|
-
Although mime-types-data was extracted from the [Ruby mime-types][rmt] gem and
|
19
|
-
the support files are written in Ruby, the _target_ of mime-types-data is any
|
20
|
-
implementation that wishes to use the data as a MIME types registry, so I am
|
21
|
-
particularly interested in tools that will create a mime-types-data package for
|
22
|
-
other languages.
|
23
|
-
|
24
|
-
## Adding or Modifying MIME Types
|
25
|
-
|
26
|
-
The Ruby mime-types gem loads its data from files encoded in the `data`
|
27
|
-
directory in this gem by loading `mime-types-data` and reading
|
28
|
-
MIME::Types::Data::PATH. These files are compiled files from the collection of
|
29
|
-
data in the `types` directory. Pull requests that include changes to these files
|
30
|
-
will require amendment to revert these files.
|
31
|
-
|
32
|
-
New or modified MIME types should be edited in the appropriate YAML file under
|
33
|
-
`types`. The format is as shown below for the `application/xml` MIME type in
|
34
|
-
`types/application.yml`.
|
35
|
-
|
36
|
-
```yaml
|
37
|
-
- !ruby/object:MIME::Type
|
38
|
-
content-type: application/xml
|
39
|
-
encoding: 8bit
|
40
|
-
extensions:
|
41
|
-
- xml
|
42
|
-
- xsl
|
43
|
-
references:
|
44
|
-
- IANA
|
45
|
-
- RFC3023
|
46
|
-
xrefs:
|
47
|
-
rfc:
|
48
|
-
- rfc3023
|
49
|
-
registered: true
|
50
|
-
```
|
51
|
-
|
52
|
-
There are other fields that can be added, matching the fields discussed in the
|
53
|
-
documentation for MIME::Type. Pull requests for MIME types should just contain
|
54
|
-
the changes to the YAML files for the new or modified MIME types; I will convert
|
55
|
-
the YAML files to JSON prior to a new release. I would rather not have to verify
|
56
|
-
that the JSON matches the YAML changes, which is why it is not necessary to
|
57
|
-
convert for the pull request.
|
58
|
-
|
59
|
-
If you are making a change for a private fork, use `rake convert:yaml:json` to
|
60
|
-
convert the YAML to JSON, or `rake convert:yaml:columnar` to convert it to the
|
61
|
-
new columnar format.
|
62
|
-
|
63
|
-
### Updating Types from the IANA or Apache Lists
|
64
|
-
|
65
|
-
If you are maintaining a private fork and wish to update your copy of the MIME
|
66
|
-
types registry used by this gem, you can do this with the rake tasks:
|
67
|
-
|
68
|
-
```sh
|
69
|
-
$ rake mime:iana
|
70
|
-
$ rake mime:apache
|
71
|
-
```
|
72
|
-
|
73
|
-
#### A Note on Provisional Types
|
74
|
-
|
75
|
-
Provisionally registered types from IANA are contained in the `types/*.yaml`
|
76
|
-
files. Per IANA,
|
77
|
-
|
78
|
-
> This registry, unlike some other provisional IANA registries, is only for
|
79
|
-
> temporary use. Entries in this registry are either finalized and moved to the
|
80
|
-
> main media types registry or are abandoned and deleted. Entries in this
|
81
|
-
> registry are suitable for use for development and test purposes only.
|
82
|
-
|
83
|
-
Provisional types are rewritten when updated, so pull requests to manually
|
84
|
-
customize provisional types (such as with extensions) are considered lower
|
85
|
-
priority. It is recommended that any updates required to the data be performed
|
86
|
-
in your application if you require provisional types.
|
87
|
-
|
88
|
-
## Development Dependencies
|
89
|
-
|
90
|
-
## Test Dependencies
|
91
|
-
|
92
|
-
mime-types-data uses Ryan Davis’s [Hoe][hoe] to manage the release process, and
|
93
|
-
it adds a number of rake tasks. You will mostly be interested in `rake`, which
|
94
|
-
runs tests the same way that `rake test` does.
|
95
|
-
|
96
|
-
To assist with the installation of the development dependencies for mime-types,
|
97
|
-
I have provided the simplest possible Gemfile pointing to the (generated)
|
98
|
-
`mime-types-data.gemspec` file. This permits `bundle install` for dependencies.
|
99
|
-
If you already have `hoe` installed, you can accomplish the same thing with
|
100
|
-
`rake newb`. This task will install any missing dependencies, run the tests, and
|
101
|
-
generate the RDoc.
|
102
|
-
|
103
|
-
You can run tests with code coverage analysis by running `rake test:coverage`.
|
104
|
-
|
105
|
-
### Workflow
|
106
|
-
|
107
|
-
Here's the most direct way to get your work merged into the project:
|
108
|
-
|
109
|
-
- Fork the project.
|
110
|
-
- Clone down your fork
|
111
|
-
(`git clone git://github.com/<username>/mime-types-data.git`).
|
112
|
-
- Create a topic branch to contain your change
|
113
|
-
(`git checkout -b my\_awesome\_feature`).
|
114
|
-
- Hack away, add tests. Not necessarily in that order.
|
115
|
-
- Make sure everything still passes by running `rake`.
|
116
|
-
- If necessary, rebase your commits into logical chunks, without errors.
|
117
|
-
- Push the branch up (`git push origin my\_awesome\_feature`).
|
118
|
-
- Create a pull request against mime-types/mime-types-data and describe what
|
119
|
-
your change does and the why you think it should be merged.
|
120
|
-
|
121
|
-
## The Release Process
|
122
|
-
|
123
|
-
The release process is much more automated than it used to be, as regular
|
124
|
-
updates are performed with GitHub actions on Tuesdays. Before release, however,
|
125
|
-
a final step of checking for IANA updates should be performed.
|
126
|
-
|
127
|
-
1. Review any outstanding issues or pull requests to see if anything needs to be
|
128
|
-
addressed. This is necessary because there is no automated source for
|
129
|
-
extensions for the thousands of MIME entries. (Suggestions and/or pull
|
130
|
-
requests for same would be deeply appreciated.)
|
131
|
-
2. `bundle install`
|
132
|
-
3. `bundle exec rake mime:apache`
|
133
|
-
4. `bundle exec rake mime:iana`
|
134
|
-
5. Review the changes to make sure that the changes are sane. The IANA data
|
135
|
-
source changes from time to time, resulting in big changes or even a broken
|
136
|
-
step 4. (The most recent change was the addition of the `font/*` top-level
|
137
|
-
category.)
|
138
|
-
6. `bundle exec rake convert`
|
139
|
-
7. `bundle exec rake update:version`
|
140
|
-
8. Write up the changes in `History.md`. If any PRs have been merged, these
|
141
|
-
should be noted specifically and contributions should be added in
|
142
|
-
`Contributing.md`.
|
143
|
-
9. Commit the changes and push to GitHub.
|
144
|
-
10. `bundle exec rake release VERSION=newversion`
|
145
|
-
|
146
|
-
This is based on an issue [#18][#18].
|
147
|
-
|
148
|
-
### Contributors
|
149
|
-
|
150
|
-
- Austin Ziegler created mime-types.
|
151
|
-
|
152
|
-
Thanks to everyone else who has contributed to mime-types:
|
153
|
-
|
154
|
-
- Aaron Patterson
|
155
|
-
- Aggelos Avgerinos
|
156
|
-
- Alessio Parma
|
157
|
-
- Alex Balhatchet
|
158
|
-
- Andre Pankratz
|
159
|
-
- Andrey Eremin
|
160
|
-
- Andy Brody
|
161
|
-
- Arnaud Meuret
|
162
|
-
- Bradley Meck
|
163
|
-
- Brandon Galbraith
|
164
|
-
- Chris Gat
|
165
|
-
- Chris Salzberg
|
166
|
-
- David Genord
|
167
|
-
- Eric Marden
|
168
|
-
- Garret Alfert
|
169
|
-
- Godfrey Chan
|
170
|
-
- Greg Brockman
|
171
|
-
- Hans de Graaff
|
172
|
-
- Henrik Hodne
|
173
|
-
- Jeremy Evans
|
174
|
-
- John Gardner
|
175
|
-
- Jon Sneyers
|
176
|
-
- Jonas Petersen
|
177
|
-
- Juanito Fatas
|
178
|
-
- Keerthi Siva
|
179
|
-
- Ken Ip
|
180
|
-
- Łukasz Śliwa
|
181
|
-
- Lucia
|
182
|
-
- Martin d'Allens
|
183
|
-
- Mauricio Linhares
|
184
|
-
- Mohammed Gad
|
185
|
-
- Myk Klemme
|
186
|
-
- nycvotes-dev
|
187
|
-
- Postmodern
|
188
|
-
- Richard Hirner
|
189
|
-
- Richard Hurt
|
190
|
-
- Richard Schneeman
|
191
|
-
- Robert Buchberger
|
192
|
-
- Samuel Williams
|
193
|
-
- Sergio Baptista
|
194
|
-
- Shane Eskritt
|
195
|
-
- Tao Guo
|
196
|
-
- Thomas Leese
|
197
|
-
- Tibor Szolár
|
198
|
-
- Todd Carrico
|
199
|
-
- Yoran Brondsema
|
200
|
-
|
201
|
-
[qcm]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
|
202
|
-
[rmt]: https://github.com/mime-types/ruby-mime-types/
|
203
|
-
[hoe]: https://github.com/seattlerb/hoe
|