René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"svg backend has limited encoding support with usetex","articleBody":"### Bug report\r\n\r\n**Bug summary**\r\n\r\nAs reported [on Launchpad](https://bugs.launchpad.net/ubuntu/+source/matplotlib/+bug/1438278), the combination of `text.usetex=True`, `text.latex.unicode=True`, and the svg backend can produce files with missing or wrong characters. A warning does get printed.\r\n\r\n**Code for reproduction**\r\n\r\n```python\r\nfrom pylab import *\r\npp={'text.usetex': True, 'text.latex.unicode': True}\r\nrcParams.update(pp)\r\n\r\nplot(1,1)\r\nylabel(r'\\textwon')\r\nsavefig('tmp.pdf')\r\nsavefig('tmp.png')\r\nsavefig('tmp.svg')\r\n```\r\n\r\n**Actual outcome**\r\n\r\nThe svg file lacks the won character. A warning like the following is printed:\r\n\r\n```\r\n../lib/matplotlib/textpath.py:389: UserWarning: The glyph (142) of font (/usr/local/texlive/2016/texmf-dist/fonts/type1/public/cm-super/sfss3583.pfb) cannot be converted with the encoding. Glyph may be wrong\r\n  \"be wrong\" % (glyph, font_bunch.filename))\r\n```\r\n\r\n**Expected outcome**\r\n\r\nThe svg file should include the won character (₩), as the pdf and png files do. I don't think we document usetex as being supported in the svg backend, but for several use cases it works.\r\n\r\n**Matplotlib version**\r\n\r\nCurrent master (3d99e435d8b74216608f29adf97bafef7e64218c) installed from git with `pip install -e .`\r\n","author":{"url":"https://github.com/jkseppan","@type":"Person","name":"jkseppan"},"datePublished":"2017-02-12T17:54:34.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/8068/matplotlib/issues/8068"}