[
https://issues.apache.org/jira/browse/NIFI-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005869#comment-15005869
]
Andre edited comment on NIFI-318 at 11/15/15 12:47 PM:
-------------------------------------------------------
[~mcgilman]
Perhaps the technique described in
[here|https://css-tricks.com/snippets/css/using-font-face/] could help solving
all the instances above?
was (Author: trixpan):
[~mcgilman]
Perhaps the technique describe in
[here|https://css-tricks.com/snippets/css/using-font-face/] could help solving
all the instances above?
> 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)
