[
https://issues.apache.org/jira/browse/NIFI-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602810#comment-15602810
]
Matt Gilman commented on NIFI-318:
----------------------------------
We've definitely added infrastructure to address this. Specifically, updating
the build to pull down the font's and bundle them in the convenience binaries.
This was added due to licensing concerns of bundling some fonts in our source.
Off the top of my head, I think we may need to include addition fonts that are
used in the documentation and update the docs to use the bundled font.
> Web Fonts
> ---------
>
> Key: NIFI-318
> URL: https://issues.apache.org/jira/browse/NIFI-318
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Reporter: Matt Gilman
> Priority: Minor
>
> - Consider using a web font loader for more control when loading fonts from
> external sources [1]. Specifically note the iframe support for the NiFi shell
> and documents within the help section.
> - Update asciidoctor usage to try to eliminate external font (and
> font-awesome) dependencies [2][3]. The major issue here is that the Google
> fonts API returns a dynamically generated stylesheet based on the browser
> requesting the font. This makes for embedding the font's tricky.
> [1] https://github.com/typekit/webfontloader
> [2] https://github.com/asciidoctor/asciidoctor/issues/879
> [3]
> http://mrhaki.blogspot.com/2014/08/awesome-asciidoc-changing-fontawesome.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
