You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Dan Bress (JIRA)" <ji...@apache.org> on 2015/02/08 17:17:34 UTC

[jira] [Commented] (NIFI-318) Web Fonts

    [ https://issues.apache.org/jira/browse/NIFI-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14311386#comment-14311386 ] 

Dan Bress commented on NIFI-318:
--------------------------------

Matt,
   Wanted to enumerate a few of the places I've seen google fonts used so far:

  1) HTML generated by asciidoc(developer-guide, overview, expression-language-guide, user-guide, administration-guide)
  2) HTML generated by framework/nifi-documentation(Processor/ControllerService/ReportingTask documentation)

> 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)