[
https://issues.apache.org/jira/browse/TIKA-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892836#comment-17892836
]
Gustavo de Oliveira Silva commented on TIKA-4339:
-------------------------------------------------
{quote}Do we leave the other fonts as is? There are a bunch of other font
types. What do we do with those?
{quote}
Yes. Keep them as they are, since they are not in IANA list.
{quote}I see woff in the spec, but I don't think we handle that. As a separate
issue, should we add woff and woff2 detection?
{quote}
Since woff and woff2 aren't in current mimetype list, I think it is a good idea
to create a separated issue for that.
{quote}Is this a breaking enough change that we should keep it only in the 4.x
branch and not make the change in the 3.x branch?
{quote}
I think that keeping the old mimetype as alias will prevent some issues, but I
think that this change needs some time to transition, then I would suggest to
apply only for 4.x+
> Wrong mimetype for font
> -----------------------
>
> Key: TIKA-4339
> URL: https://issues.apache.org/jira/browse/TIKA-4339
> Project: Tika
> Issue Type: Bug
> Components: mime
> Reporter: Gustavo de Oliveira Silva
> Assignee: Tim Allison
> Priority: Minor
> Attachments: suggestion.diff
>
>
> The current font mimetype are `application/x-font-otf` and
> `application/x-font-ttf`
> They are this since 2009. But with RFC8081, IANA added the type `font/*` for
> fonts.
> IANA: [https://www.iana.org/assignments/media-types/media-types.xhtml#font]
> RFC8081: [https://www.rfc-editor.org/rfc/rfc8081.html]
>
> Almost only change `application/x-font-otf` to `font/otf` and
> `application/x-font-ttf` to `font/ttf`.
> The attached file is a suggestion
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
