Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#36511 - [ipython] fonts required for notebook
Attached to Project:
Community Packages
Opened by Mike Ressler (mike_r) - Monday, 12 August 2013, 20:44 GMT
Last edited by Kyle Keen (keenerd) - Thursday, 15 August 2013, 20:01 GMT
Opened by Mike Ressler (mike_r) - Monday, 12 August 2013, 20:44 GMT
Last edited by Kyle Keen (keenerd) - Thursday, 15 August 2013, 20:01 GMT
|
DetailsDescription: The font "font-awesome" needs to be installed so that the toolbar icons in the notebook work for ipython-1.0. "otf-font-awesome" and "ttf-font-awesome" are available in the AUR. I installed the OTF version and things now work correctly.
Either version of the font needs to be adopted into the Community repo, then it needs to be added as an optional dependency to ipython. Additional info: * ipython 1.0 Steps to reproduce: Install ipython-1.0 Install jinja (see other bug reports) Start "ipython notebook" and load a notebook Toolbar icons show a small square with four characters inside, typical of an incorrect font that does not have the appropriate glyphs. |
This task depends upon
Closed by Kyle Keen (keenerd)
Thursday, 15 August 2013, 20:01 GMT
Reason for closing: Not a bug
Additional comments about closing: Bad config.
Thursday, 15 August 2013, 20:01 GMT
Reason for closing: Not a bug
Additional comments about closing: Bad config.
Are you sure this font is required? Even as an optdep, it would still need to be moved. I would prefer to change the default font to something more reasonable.
edit: Ew, it is a bunch of icons. Ipython guys, what are you doing...
http://ipython.org/ipython-doc/stable/whatsnew/version1.0.html
About 3/4 of the way down the page, under "Javascript Components" it lists:
Font-Awesome (3.1) for icons
So I found the fonts in the AUR, and after installation, all is working as I expected. I suppose there might be other symbol fonts that provide similar glyphs in the same positions, but I haven't looked to see how the particular font file gets called.
Thanks for looking into this.
edit: the otf font actually comes with ipython and is installed in /usr/lib/python3.3/site-packages/IPython/html/static/components/font-awesome/build/assets/font-awesome/font/FontAwesome.otf. I guess it is just an issue of making the "runtime" see it. I'll try some more digging later.
Based on this, I'm changing my earlier answer ... don't pull in the font-awesome files. There is clearly something not working properly within the package itself. I know the ipython guys a bit - maybe I'll ask upstream next.
I then tried it on my personal laptop at home. It works flawlessly, though there are no Font-Awesome fonts reported by lsof whatsoever. There are no OTF fonts loaded, and the TTFs are all the usual suspects like DejaVu, Liberation, etc. Nothing that resembles Font-Awesome. I'm presuming it is finding its own font, but I would have expected lsof to tell me this.
All three system are up-to-date Arch except for the kernel and graphics modules. (The 3.10.5 kernels with the nvidia and intel drivers killed everything for me, so I downgraded to 3.10.3 or 3.9.9. Everything else is current.) I'm running E17 on all three, but I don't see how that could matter. I don't think this is a PEBKAC, but I am certainly confused ...
Sorry for the noise. I think it is safe to close this with no further work.
edit: Finally traced it down to whether I let pages to choose their own fonts in Firefox. If I say "yes", it works. If I say "no", it fails. Too bad, because I carefully choose my fonts to keep things readable. So please close this -- not a bug -- though it is a "grrr".