mime-types-data 3.2024.0604 → 3.2024.1001
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/Code-of-Conduct.md +99 -46
- data/Contributing.md +40 -81
- data/History.md +34 -0
- data/Licence.md +1 -1
- data/Manifest.txt +3 -0
- data/SECURITY.md +7 -0
- data/data/content_type_mime.db +4 -3
- data/data/ext_mime.db +4 -3
- data/data/mime-types.json +1 -1
- data/data/mime.content_type.column +25 -5
- data/data/mime.docs.column +20 -0
- data/data/mime.encoding.column +20 -0
- data/data/mime.flags.column +23 -3
- data/data/mime.friendly.column +20 -0
- data/data/mime.pext.column +20 -0
- data/data/mime.use_instead.column +23 -3
- data/data/mime.xrefs.column +48 -28
- data/lib/mime/types/data.rb +1 -1
- data/types/application.yaml +165 -16
- data/types/audio.yaml +14 -4
- data/types/example.yaml +1 -0
- data/types/haptics.yaml +28 -0
- data/types/image.yaml +8 -0
- data/types/message.yaml +6 -0
- data/types/model.yaml +4 -0
- data/types/multipart.yaml +8 -0
- data/types/text.yaml +24 -0
- data/types/video.yaml +6 -4
- metadata +7 -3
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: f2c4a58fc0920f93f675623adcda0313a45a36d3ddb2f7f4dc3a5c68a204fe8b
|
|
4
|
+
data.tar.gz: 8a40a69501bb0603346b86150685cd16877a1f6eff0e3906b4e3611b012a0ff0
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 9bcdfa93837e4f5c1b806c605c3eee8c6556133e078d886e0f7bcdffebd201eb7b5598f3dd5efb71c550dc5c86c905a346461f6bd155a3a38319664fbe51a7f2
|
|
7
|
+
data.tar.gz: 6e7ef7a4d4434ea83c854a20b07ad5051c07b15cd510977d193941cd7dd92fb0c54fa5535e15e66ed93328983f414f3ff5543800017042e9b7fb2b262a261523
|
data/Code-of-Conduct.md
CHANGED
|
@@ -2,74 +2,127 @@
|
|
|
2
2
|
|
|
3
3
|
## Our Pledge
|
|
4
4
|
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
and orientation.
|
|
5
|
+
We as members, contributors, and leaders pledge to make participation in our
|
|
6
|
+
community a harassment-free experience for everyone, regardless of age, body
|
|
7
|
+
size, visible or invisible disability, ethnicity, sex characteristics, gender
|
|
8
|
+
identity and expression, level of experience, education, socio-economic status,
|
|
9
|
+
nationality, personal appearance, race, caste, color, religion, or sexual
|
|
10
|
+
identity and orientation.
|
|
11
|
+
|
|
12
|
+
We pledge to act and interact in ways that contribute to an open, welcoming,
|
|
13
|
+
diverse, inclusive, and healthy community.
|
|
11
14
|
|
|
12
15
|
## Our Standards
|
|
13
16
|
|
|
14
|
-
Examples of behavior that contributes to
|
|
15
|
-
include:
|
|
17
|
+
Examples of behavior that contributes to a positive environment for our
|
|
18
|
+
community include:
|
|
16
19
|
|
|
17
|
-
-
|
|
18
|
-
- Being respectful of differing viewpoints and experiences
|
|
19
|
-
-
|
|
20
|
-
-
|
|
21
|
-
|
|
20
|
+
- Demonstrating empathy and kindness toward other people
|
|
21
|
+
- Being respectful of differing opinions, viewpoints, and experiences
|
|
22
|
+
- Giving and gracefully accepting constructive feedback
|
|
23
|
+
- Accepting responsibility and apologizing to those affected by our mistakes,
|
|
24
|
+
and learning from the experience
|
|
25
|
+
- Focusing on what is best not just for us as individuals, but for the overall
|
|
26
|
+
community
|
|
22
27
|
|
|
23
|
-
Examples of unacceptable behavior
|
|
28
|
+
Examples of unacceptable behavior include:
|
|
24
29
|
|
|
25
|
-
- The use of sexualized language or imagery and
|
|
26
|
-
|
|
27
|
-
- Trolling, insulting
|
|
30
|
+
- The use of sexualized language or imagery, and sexual attention or advances of
|
|
31
|
+
any kind
|
|
32
|
+
- Trolling, insulting or derogatory comments, and personal or political attacks
|
|
28
33
|
- Public or private harassment
|
|
29
|
-
- Publishing others' private information, such as a physical or
|
|
30
|
-
|
|
34
|
+
- Publishing others' private information, such as a physical or email address,
|
|
35
|
+
without their explicit permission
|
|
31
36
|
- Other conduct which could reasonably be considered inappropriate in a
|
|
32
37
|
professional setting
|
|
33
38
|
|
|
34
|
-
##
|
|
39
|
+
## Enforcement Responsibilities
|
|
35
40
|
|
|
36
|
-
|
|
37
|
-
behavior and
|
|
38
|
-
response to any
|
|
41
|
+
Community leaders are responsible for clarifying and enforcing our standards of
|
|
42
|
+
acceptable behavior and will take appropriate and fair corrective action in
|
|
43
|
+
response to any behavior that they deem inappropriate, threatening, offensive,
|
|
44
|
+
or harmful.
|
|
39
45
|
|
|
40
|
-
|
|
46
|
+
Community leaders have the right and responsibility to remove, edit, or reject
|
|
41
47
|
comments, commits, code, wiki edits, issues, and other contributions that are
|
|
42
|
-
not aligned to this Code of Conduct,
|
|
43
|
-
|
|
44
|
-
offensive, or harmful.
|
|
48
|
+
not aligned to this Code of Conduct, and will communicate reasons for moderation
|
|
49
|
+
decisions when appropriate.
|
|
45
50
|
|
|
46
51
|
## Scope
|
|
47
52
|
|
|
48
|
-
This Code of Conduct applies
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
representative at an online or offline event.
|
|
53
|
-
further defined and clarified by project maintainers.
|
|
53
|
+
This Code of Conduct applies within all community spaces, and also applies when
|
|
54
|
+
an individual is officially representing the community in public spaces.
|
|
55
|
+
Examples of representing our community include using an official email address,
|
|
56
|
+
posting via an official social media account, or acting as an appointed
|
|
57
|
+
representative at an online or offline event.
|
|
54
58
|
|
|
55
59
|
## Enforcement
|
|
56
60
|
|
|
57
61
|
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
|
58
|
-
reported
|
|
59
|
-
complaints will be reviewed and investigated and
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
62
|
+
reported to the community leaders responsible for enforcement at [INSERT CONTACT
|
|
63
|
+
METHOD]. All complaints will be reviewed and investigated promptly and fairly.
|
|
64
|
+
|
|
65
|
+
All community leaders are obligated to respect the privacy and security of the
|
|
66
|
+
reporter of any incident.
|
|
67
|
+
|
|
68
|
+
## Enforcement Guidelines
|
|
69
|
+
|
|
70
|
+
Community leaders will follow these Community Impact Guidelines in determining
|
|
71
|
+
the consequences for any action they deem in violation of this Code of Conduct:
|
|
72
|
+
|
|
73
|
+
### 1. Correction
|
|
74
|
+
|
|
75
|
+
**Community Impact**: Use of inappropriate language or other behavior deemed
|
|
76
|
+
unprofessional or unwelcome in the community.
|
|
77
|
+
|
|
78
|
+
**Consequence**: A private, written warning from community leaders, providing
|
|
79
|
+
clarity around the nature of the violation and an explanation of why the
|
|
80
|
+
behavior was inappropriate. A public apology may be requested.
|
|
81
|
+
|
|
82
|
+
### 2. Warning
|
|
83
|
+
|
|
84
|
+
**Community Impact**: A violation through a single incident or series of
|
|
85
|
+
actions.
|
|
64
86
|
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
87
|
+
**Consequence**: A warning with consequences for continued behavior. No
|
|
88
|
+
interaction with the people involved, including unsolicited interaction with
|
|
89
|
+
those enforcing the Code of Conduct, for a specified period of time. This
|
|
90
|
+
includes avoiding interactions in community spaces as well as external channels
|
|
91
|
+
like social media. Violating these terms may lead to a temporary or permanent
|
|
92
|
+
ban.
|
|
93
|
+
|
|
94
|
+
### 3. Temporary Ban
|
|
95
|
+
|
|
96
|
+
**Community Impact**: A serious violation of community standards, including
|
|
97
|
+
sustained inappropriate behavior.
|
|
98
|
+
|
|
99
|
+
**Consequence**: A temporary ban from any sort of interaction or public
|
|
100
|
+
communication with the community for a specified period of time. No public or
|
|
101
|
+
private interaction with the people involved, including unsolicited interaction
|
|
102
|
+
with those enforcing the Code of Conduct, is allowed during this period.
|
|
103
|
+
Violating these terms may lead to a permanent ban.
|
|
104
|
+
|
|
105
|
+
### 4. Permanent Ban
|
|
106
|
+
|
|
107
|
+
**Community Impact**: Demonstrating a pattern of violation of community
|
|
108
|
+
standards, including sustained inappropriate behavior, harassment of an
|
|
109
|
+
individual, or aggression toward or disparagement of classes of individuals.
|
|
110
|
+
|
|
111
|
+
**Consequence**: A permanent ban from any sort of public interaction within the
|
|
112
|
+
community.
|
|
68
113
|
|
|
69
114
|
## Attribution
|
|
70
115
|
|
|
71
|
-
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
|
|
72
|
-
available at
|
|
116
|
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
|
|
117
|
+
version 2.1, available at
|
|
118
|
+
<https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.
|
|
119
|
+
|
|
120
|
+
Community Impact Guidelines were inspired by
|
|
121
|
+
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
|
|
122
|
+
|
|
123
|
+
For answers to common questions about this code of conduct, see the FAQ at
|
|
124
|
+
<https://www.contributor-covenant.org/faq>. Translations are available at
|
|
125
|
+
<https://www.contributor-covenant.org/translations>.
|
|
73
126
|
|
|
74
|
-
[homepage]:
|
|
75
|
-
[
|
|
127
|
+
[homepage]: https://www.contributor-covenant.org
|
|
128
|
+
[Mozilla CoC]: https://github.com/mozilla/diversity
|
data/Contributing.md
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
|
|
1
|
+
# Contributing
|
|
2
2
|
|
|
3
3
|
Contributions to mime-types-data is encouraged in any form: a bug report, new
|
|
4
4
|
MIME type definitions, or additional code to help manage the MIME types. As with
|
|
@@ -10,8 +10,8 @@ acceptance of your code contributions:
|
|
|
10
10
|
- Use a thoughtfully-named topic branch that contains your change. Rebase your
|
|
11
11
|
commits into logical chunks as necessary.
|
|
12
12
|
- Use [quality commit messages][qcm].
|
|
13
|
-
- Do not change the version number; when your patch is accepted and a release
|
|
14
|
-
|
|
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
15
|
- Submit a GitHub pull request with your changes.
|
|
16
16
|
- New or changed behaviours require new or updated documentation.
|
|
17
17
|
|
|
@@ -21,7 +21,7 @@ implementation that wishes to use the data as a MIME types registry, so I am
|
|
|
21
21
|
particularly interested in tools that will create a mime-types-data package for
|
|
22
22
|
other languages.
|
|
23
23
|
|
|
24
|
-
|
|
24
|
+
## Adding or Modifying MIME Types
|
|
25
25
|
|
|
26
26
|
The Ruby mime-types gem loads its data from files encoded in the `data`
|
|
27
27
|
directory in this gem by loading `mime-types-data` and reading
|
|
@@ -60,7 +60,7 @@ If you are making a change for a private fork, use `rake convert:yaml:json` to
|
|
|
60
60
|
convert the YAML to JSON, or `rake convert:yaml:columnar` to convert it to the
|
|
61
61
|
new columnar format.
|
|
62
62
|
|
|
63
|
-
|
|
63
|
+
### Updating Types from the IANA or Apache Lists
|
|
64
64
|
|
|
65
65
|
If you are maintaining a private fork and wish to update your copy of the MIME
|
|
66
66
|
types registry used by this gem, you can do this with the rake tasks:
|
|
@@ -70,71 +70,47 @@ $ rake mime:iana
|
|
|
70
70
|
$ rake mime:apache
|
|
71
71
|
```
|
|
72
72
|
|
|
73
|
-
|
|
73
|
+
#### A Note on Provisional Types
|
|
74
74
|
|
|
75
|
-
|
|
76
|
-
|
|
75
|
+
Provisionally registered types from IANA are contained in the `types/*.yaml`
|
|
76
|
+
files. Per IANA,
|
|
77
77
|
|
|
78
78
|
> This registry, unlike some other provisional IANA registries, is only for
|
|
79
79
|
> temporary use. Entries in this registry are either finalized and moved to the
|
|
80
80
|
> main media types registry or are abandoned and deleted. Entries in this
|
|
81
81
|
> registry are suitable for use for development and test purposes only.
|
|
82
82
|
|
|
83
|
-
|
|
84
|
-
|
|
85
|
-
recommended that any updates required to the data be performed
|
|
86
|
-
application if you require provisional types.
|
|
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
87
|
|
|
88
|
-
|
|
88
|
+
## Development Dependencies
|
|
89
89
|
|
|
90
|
-
|
|
91
|
-
manage the release process, and it adds a number of rake tasks. You will mostly
|
|
92
|
-
be interested in:
|
|
90
|
+
## Test Dependencies
|
|
93
91
|
|
|
94
|
-
|
|
95
|
-
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
which runs the tests the same way that:
|
|
99
|
-
|
|
100
|
-
```sh
|
|
101
|
-
$ rake test
|
|
102
|
-
$ rake travis
|
|
103
|
-
```
|
|
104
|
-
|
|
105
|
-
will do.
|
|
106
|
-
|
|
107
|
-
To assist with the installation of the development dependencies for
|
|
108
|
-
mime-types-data, I have provided the simplest possible Gemfile pointing to the
|
|
109
|
-
(generated) `mime-types-data.gemspec` file. This will permit you to do:
|
|
110
|
-
|
|
111
|
-
```sh
|
|
112
|
-
$ bundle install
|
|
113
|
-
```
|
|
114
|
-
|
|
115
|
-
to get the development dependencies. If you aleady have `hoe` installed, you
|
|
116
|
-
can accomplish the same thing with:
|
|
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.
|
|
117
95
|
|
|
118
|
-
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
This task will install any missing dependencies, run the tests
|
|
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
|
|
123
101
|
generate the RDoc.
|
|
124
102
|
|
|
125
|
-
You can run tests with code coverage analysis by running:
|
|
126
|
-
|
|
127
|
-
```sh
|
|
128
|
-
$ rake test:coverage
|
|
129
|
-
```
|
|
103
|
+
You can run tests with code coverage analysis by running `rake test:coverage`.
|
|
130
104
|
|
|
131
105
|
### Workflow
|
|
132
106
|
|
|
133
107
|
Here's the most direct way to get your work merged into the project:
|
|
134
108
|
|
|
135
109
|
- Fork the project.
|
|
136
|
-
- Clone down your fork
|
|
137
|
-
|
|
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`).
|
|
138
114
|
- Hack away, add tests. Not necessarily in that order.
|
|
139
115
|
- Make sure everything still passes by running `rake`.
|
|
140
116
|
- If necessary, rebase your commits into logical chunks, without errors.
|
|
@@ -142,50 +118,32 @@ Here's the most direct way to get your work merged into the project:
|
|
|
142
118
|
- Create a pull request against mime-types/mime-types-data and describe what
|
|
143
119
|
your change does and the why you think it should be merged.
|
|
144
120
|
|
|
145
|
-
|
|
121
|
+
## The Release Process
|
|
146
122
|
|
|
147
|
-
The release process
|
|
148
|
-
|
|
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.
|
|
149
126
|
|
|
150
127
|
1. Review any outstanding issues or pull requests to see if anything needs to be
|
|
151
|
-
addressed. This is necessary because there is
|
|
152
|
-
|
|
128
|
+
addressed. This is necessary because there is no automated source for
|
|
129
|
+
extensions for the thousands of MIME entries. (Suggestions and/or pull
|
|
153
130
|
requests for same would be deeply appreciated.)
|
|
154
131
|
2. `bundle install`
|
|
155
132
|
3. `bundle exec rake mime:apache`
|
|
156
133
|
4. `bundle exec rake mime:iana`
|
|
157
134
|
5. Review the changes to make sure that the changes are sane. The IANA data
|
|
158
135
|
source changes from time to time, resulting in big changes or even a broken
|
|
159
|
-
step 4. (The most recent change was the addition of the font
|
|
136
|
+
step 4. (The most recent change was the addition of the `font/*` top-level
|
|
160
137
|
category.)
|
|
161
138
|
6. `bundle exec rake convert`
|
|
162
139
|
7. `bundle exec rake update:version`
|
|
163
|
-
8. Write up the changes in History.md
|
|
164
|
-
be noted specifically
|
|
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`.
|
|
165
143
|
9. Commit the changes and push to GitHub.
|
|
166
144
|
10. `bundle exec rake release VERSION=newversion`
|
|
167
145
|
|
|
168
|
-
|
|
169
|
-
|
|
170
|
-
If anyone wishes to provide suggestions on automation, this would be a two-phase
|
|
171
|
-
process:
|
|
172
|
-
|
|
173
|
-
1. A system would need to periodically create PRs to the GitHub repository with
|
|
174
|
-
the output of the following commands (steps 2, 3, and 4):
|
|
175
|
-
|
|
176
|
-
```sh
|
|
177
|
-
bundle install
|
|
178
|
-
bundle exec rake mime:apache
|
|
179
|
-
bundle exec rake mime:iana
|
|
180
|
-
git add .
|
|
181
|
-
git commit -m "[Automated] MIME Type update for $(date)"
|
|
182
|
-
# Somehow make the PR from here.
|
|
183
|
-
```
|
|
184
|
-
|
|
185
|
-
2. Once this PR is approved and merged, the next steps would be conversion,
|
|
186
|
-
version update, automatic update of History.md, and release (steps 6–10).
|
|
187
|
-
|
|
188
|
-
This is based on an issue [#18][].
|
|
146
|
+
This is based on an issue [#18][#18].
|
|
189
147
|
|
|
190
148
|
### Contributors
|
|
191
149
|
|
|
@@ -233,6 +191,7 @@ Thanks to everyone else who has contributed to mime-types:
|
|
|
233
191
|
- Robert Buchberger
|
|
234
192
|
- Samuel Williams
|
|
235
193
|
- Sergio Baptista
|
|
194
|
+
- Shane Eskritt
|
|
236
195
|
- Tao Guo
|
|
237
196
|
- Thomas Leese
|
|
238
197
|
- Tibor Szolár
|
|
@@ -241,4 +200,4 @@ Thanks to everyone else who has contributed to mime-types:
|
|
|
241
200
|
|
|
242
201
|
[qcm]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
|
|
243
202
|
[rmt]: https://github.com/mime-types/ruby-mime-types/
|
|
244
|
-
[
|
|
203
|
+
[hoe]: https://github.com/seattlerb/hoe
|
data/History.md
CHANGED
|
@@ -2,6 +2,38 @@
|
|
|
2
2
|
|
|
3
3
|
<!-- automatic-release -->
|
|
4
4
|
|
|
5
|
+
## 3.2024.1001 / 2024-10-01
|
|
6
|
+
|
|
7
|
+
- Updated the Apache and IANA media registry entries as of release date
|
|
8
|
+
|
|
9
|
+
## 3.2024.0903 / 2024-09-03
|
|
10
|
+
|
|
11
|
+
- Updated the Apache and IANA media registry entries as of release date
|
|
12
|
+
|
|
13
|
+
## 3.2024.0820 / 2024-08-20
|
|
14
|
+
|
|
15
|
+
- Updated the Apache and IANA media registry entries as of release date.
|
|
16
|
+
|
|
17
|
+
- Added `.jxl` extension for `image/jxl`. Contributed by Shane Eskritt in
|
|
18
|
+
[#81][#81].
|
|
19
|
+
|
|
20
|
+
## 3.2024.0806 / 2024-08-06
|
|
21
|
+
|
|
22
|
+
- Updated the Apache and IANA media registry entries as of release date
|
|
23
|
+
|
|
24
|
+
## 3.2024.0702 / 2024-07-02
|
|
25
|
+
|
|
26
|
+
- Updated the Apache and IANA media registry entries as of release date
|
|
27
|
+
|
|
28
|
+
- This update adds an empty `example/` top-level media type group.
|
|
29
|
+
|
|
30
|
+
- This update adds a new `haptics/` group with three media types defined.
|
|
31
|
+
|
|
32
|
+
- Moved extensions from `audio/x-aac` to `audio/aac` and mark `audio/x-aac` as
|
|
33
|
+
obsolete. Based on [#77][#77] by Samuel Williams.
|
|
34
|
+
|
|
35
|
+
- Made the same changes for `audio/flac` and `audio/matroska`.
|
|
36
|
+
|
|
5
37
|
## 3.2024.0604 / 2024-06-04
|
|
6
38
|
|
|
7
39
|
- Updated the Apache and IANA media registry entries as of release date
|
|
@@ -570,6 +602,8 @@
|
|
|
570
602
|
[#53]: https://github.com/mime-types/mime-types-data/pull/53
|
|
571
603
|
[#54]: https://github.com/mime-types/mime-types-data/issues/54
|
|
572
604
|
[#55]: https://github.com/mime-types/mime-types-data/issues/55
|
|
605
|
+
[#77]: https://github.com/mime-types/mime-types-data/pull/77
|
|
606
|
+
[#81]: https://github.com/mime-types/mime-types-data/pull/81
|
|
573
607
|
[rmt]: https://github.com/mime-types/ruby-mime-types
|
|
574
608
|
[code of conduct]: Code-of-Conduct.md
|
|
575
609
|
[mini_mime]: https://github.com/discourse/mini_mime/issues/41
|
data/Licence.md
CHANGED
data/Manifest.txt
CHANGED
|
@@ -5,6 +5,7 @@ Licence.md
|
|
|
5
5
|
Manifest.txt
|
|
6
6
|
README.md
|
|
7
7
|
Rakefile
|
|
8
|
+
SECURITY.md
|
|
8
9
|
data/content_type_mime.db
|
|
9
10
|
data/ext_mime.db
|
|
10
11
|
data/mime-types.json
|
|
@@ -23,7 +24,9 @@ types/audio.yaml
|
|
|
23
24
|
types/chemical.yaml
|
|
24
25
|
types/conference.yaml
|
|
25
26
|
types/drawing.yaml
|
|
27
|
+
types/example.yaml
|
|
26
28
|
types/font.yaml
|
|
29
|
+
types/haptics.yaml
|
|
27
30
|
types/image.yaml
|
|
28
31
|
types/message.yaml
|
|
29
32
|
types/model.yaml
|
data/SECURITY.md
ADDED
data/data/content_type_mime.db
CHANGED
|
@@ -645,8 +645,11 @@ awb audio/AMR-WB
|
|
|
645
645
|
evc audio/EVRC base64
|
|
646
646
|
l16 audio/L16 base64
|
|
647
647
|
smv audio/SMV base64
|
|
648
|
+
aac audio/aac base64
|
|
648
649
|
adp audio/adpcm base64
|
|
649
650
|
au audio/basic base64
|
|
651
|
+
flac audio/flac base64
|
|
652
|
+
mka audio/matroska base64
|
|
650
653
|
kar audio/midi base64
|
|
651
654
|
mp4 audio/mp4 base64
|
|
652
655
|
mpga audio/mpeg base64
|
|
@@ -671,11 +674,8 @@ rip audio/vnd.rip
|
|
|
671
674
|
smp3 audio/vnd.sealedmedia.softseal.mpeg base64
|
|
672
675
|
wav audio/wav base64
|
|
673
676
|
weba audio/webm base64
|
|
674
|
-
aac audio/x-aac base64
|
|
675
677
|
aif audio/x-aiff base64
|
|
676
678
|
caf audio/x-caf base64
|
|
677
|
-
flac audio/x-flac base64
|
|
678
|
-
mka audio/x-matroska base64
|
|
679
679
|
m3u audio/x-mpegurl base64
|
|
680
680
|
wax audio/x-ms-wax base64
|
|
681
681
|
wma audio/x-ms-wma base64
|
|
@@ -707,6 +707,7 @@ jp2 image/jp2
|
|
|
707
707
|
jpeg image/jpeg base64
|
|
708
708
|
jpm image/jpm base64
|
|
709
709
|
jpx image/jpx base64
|
|
710
|
+
jxl image/jxl base64
|
|
710
711
|
ktx image/ktx base64
|
|
711
712
|
png image/png base64
|
|
712
713
|
btif image/prs.btif base64
|
data/data/ext_mime.db
CHANGED
|
@@ -10,7 +10,7 @@
|
|
|
10
10
|
@dir application/x-director base64
|
|
11
11
|
@dxr application/x-director base64
|
|
12
12
|
aab application/x-authorware-bin base64
|
|
13
|
-
aac audio/
|
|
13
|
+
aac audio/aac base64
|
|
14
14
|
aam application/x-authorware-map base64
|
|
15
15
|
aas application/x-authorware-seg base64
|
|
16
16
|
abw application/x-abiword base64
|
|
@@ -281,7 +281,7 @@ fh5 image/x-freehand
|
|
|
281
281
|
fh7 image/x-freehand base64
|
|
282
282
|
fhc image/x-freehand base64
|
|
283
283
|
fig application/x-xfig base64
|
|
284
|
-
flac audio/
|
|
284
|
+
flac audio/flac base64
|
|
285
285
|
fli video/x-fli base64
|
|
286
286
|
flo application/vnd.micrografx.flo base64
|
|
287
287
|
flv video/x-flv base64
|
|
@@ -428,6 +428,7 @@ jpx image/jpx
|
|
|
428
428
|
js text/javascript quoted-printable
|
|
429
429
|
json application/json 8bit
|
|
430
430
|
jsonml application/jsonml+json base64
|
|
431
|
+
jxl image/jxl base64
|
|
431
432
|
k25 image/x-kodak-k25 base64
|
|
432
433
|
kar audio/midi base64
|
|
433
434
|
karbon application/vnd.kde.karbon base64
|
|
@@ -527,7 +528,7 @@ mjpeg video/x-motion-jpeg
|
|
|
527
528
|
mjpg video/x-motion-jpeg base64
|
|
528
529
|
mjs text/javascript quoted-printable
|
|
529
530
|
mk3d video/x-matroska base64
|
|
530
|
-
mka audio/
|
|
531
|
+
mka audio/matroska base64
|
|
531
532
|
mkd text/markdown quoted-printable
|
|
532
533
|
mks video/x-matroska base64
|
|
533
534
|
mkv video/x-matroska base64
|