UnicodeDecodeError when making a plot using the 'classic' style and text.usetex=True #8423

Activity

1. ngoldbaum commented on Apr 3, 2017

   

   ngoldbaum

   on Apr 3, 2017

   Last edited by ngoldbaum

   ContributorAuthor

   More actions

   Ah, it works if the bits that interact with matplotlib look like this:

   with plt.style.context('classic'):
       plt.plot(t, s)
       plt.savefig('tex_demo')
   

   instead of this:

   plt.plot(t, s)
   with plt.style.context('classic'):
       plt.savefig('tex_demo')
   

   So I guess that explains why no one noticed until now.

   Unfortunately the way the script runs in the description is more or less how yt is using matplotlib. It's kind of a hack, but it's the only way I could figure out to work around #6518 and make sure yt plots have the same fonts they had under matplotlib 1.5.3.
2. tacaswell commented on Apr 4, 2017

   

   tacaswell

   on Apr 4, 2017

   Member

   More actions

   I can reproduce this, but do not understand why....

   I think the important thing is if the figure (and hence axes and such) are created in the context manager or not.

   The three obviously relavent rcparams ('text.latex.unicode', 'text.usetex', 'axes.unicode_minus') are the same in the new default and classic mode (or I can not read which is also possible).

   A workaround might be to set 'axes.unicode_minus' to False
3. tacaswell commented on Apr 4, 2017

   

   tacaswell

   on Apr 4, 2017

   Member

   More actions

   import numpy as np
   import matplotlib.pyplot as plt
   from matplotlib import rcParams
   rcParams['text.usetex'] = True
   
   # Example data
   t = np.arange(-1.0, 1.0 + 0.01, 0.01)
   s = np.cos(4 * np.pi * t) + 2
   
   
   plt.close('all')
   plt.plot(t, s)
   
   with plt.style.context({'text.usetex': True}, 'classic'):
   
       plt.savefig('tex_demo')

   This behaves as expected, but again, not quite sure why.
4. tacaswell

   added this to the 2.0.1 (next bug fix release)This milestone has been deleted milestone on Apr 4, 2017
5. ngoldbaum commented on Apr 4, 2017

   

   ngoldbaum

   on Apr 4, 2017

   ContributorAuthor

   More actions

   According to the API docs, plt.style.context({'text.usetex': True}, 'classic') is equivalent to plt.style.context({'text.usetex': True}) (the second argument to context is a boolean). But I see what you're getting at, this also triggers a unicode error:

   import matplotlib.pyplot as plt
   # Example data
   t = np.arange(-1.0, 1.0 + 0.01, 0.01)
   s = np.cos(4 * np.pi * t) + 2
   
   from matplotlib import rcParams
   rcParams['text.usetex'] = True
   
   plt.close('all')
   plt.plot(t, s)
   
   with plt.style.context({'text.usetex': False}):
       plt.savefig('tex_demo')
   
6. tacaswell commented on Apr 4, 2017

   

   tacaswell

   on Apr 4, 2017

   Member

   More actions

   hmm, I mis-remembered that API then...It is a list of styles, not *args of styles:

   import numpy as np
   import matplotlib.pyplot as plt
   from matplotlib import rcParams
   rcParams['text.usetex'] = True
   
   # Example data
   t = np.arange(-1.0, 1.0 + 0.01, 0.01)
   s = np.cos(4 * np.pi * t) + 2
   
   
   plt.close('all')
   plt.plot(t, s)
   
   with plt.style.context(['classic', {'text.usetex': True}]):
   
       plt.savefig('tex_demo')

   and that order makes more sense!
7. ngoldbaum commented on Apr 4, 2017

   

   ngoldbaum

   on Apr 4, 2017

   Last edited by ngoldbaum

   ContributorAuthor

   More actions

   FWIW I've mitigated this on the yt side with yt PR 2573 (https://bitbucket.org/yt_analysis/yt/pull-requests/2573). I guess using the classic style just to get the fonts I want was a bit of a blunt instrument.
8. QuLogic

   modified the milestones: 2.0.1 (next bug fix release)This milestone has been deleted, 2.0.2 (next bug fix release)This milestone has been deleted on May 3, 2017
9. tacaswell

   modified the milestones: 2.1.1 (next bug fix release)This milestone has been deleted, 2.2 (next feature release)This milestone has been deleted on Oct 9, 2017
10. jkseppan

    added

    topic: text/usetex

    on Jan 19, 2018
11. anntzer commented on Jun 18, 2019

    

    anntzer

    on Jun 18, 2019

    Contributor

    More actions

    text.latex.unicode is now on by default, per #11381 (not on the 2.2.x branch, FWIW).
    However this now fails with

    RuntimeError: latex was not able to process the following string:
    b'$\\u22121.5$'
    
    Here is the full report generated by latex:
    This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019) (preloaded format=latex)
     restricted \write18 enabled.
    entering extended mode
    (/tmp/mpld/tex.cache/ce3437ef20f4f97917585a4bd387f953.tex
    LaTeX2e <2018-12-01>
    
    <elided>
    
    ! Package inputenc Error: Unicode character − (U+2212)
    (inputenc)                not set up for use with LaTeX.
    
    See the inputenc package documentation for explanation.
    Type  H <return>  for immediate help.
     ...                                              
                                                      
    l.14 ...tsize{10.000000}{12.500000}{\sffamily $−
                                                      1.5$}
    No pages of output.
    Transcript written on ce3437ef20f4f97917585a4bd387f953.log.
    

    but I have a fix coming up for that...

    👍React with 👍1Reacted by Samuel Hinton
12. timhoffm

    closed this as completedin #14567on Jun 19, 2019
13. QuLogic

    modified the milestones: needs sorting, v3.2.0 on Jun 19, 2019