pyx-user — PyX user

[PyX-user] python 2 -> 3

[<rba...@mu...>]

2015.12.23

Hello PyX,

I get PDF, EPS & SVG but there are warnings:
---------------------
Ignoring line 14513 in mapping file 'pdftex.map': Unknown token '<MinLibBol'
Ignoring line 14514 in mapping file 'pdftex.map': Unknown token '<MinLibBol'
Ignoring line 14515 in mapping file 'pdftex.map': Unknown token '<MinLibBol'
Ignoring line 14516 in mapping file 'pdftex.map': Unknown token '<MinLibBolIta'
Ignoring line 14517 in mapping file 'pdftex.map': Unknown token '<MinLibBolIta'
Ignoring line 14518 in mapping file 'pdftex.map': Unknown token '<MinLibBolIta'
Ignoring line 14519 in mapping file 'pdftex.map': Unknown token '<MinLibIta'
Ignoring line 14520 in mapping file 'pdftex.map': Unknown token '<MinLibIta'
Ignoring line 14521 in mapping file 'pdftex.map': Unknown token '<MinLibIta'
Ignoring line 14522 in mapping file 'pdftex.map': Unknown token '<MinLibReg'
Ignoring line 14523 in mapping file 'pdftex.map': Unknown token '<MinLibReg'
Ignoring line 14524 in mapping file 'pdftex.map': Unknown token '<MinLibReg'
---------------------

 file: ~/Tex2014/texmf-var/fonts/map/pdftex/updmap/pdftex.map 

René B.

Re: [PyX-user] magic number

[André W. <wo...@us...>]

Hi René,

well, those cache files can be removed. The whole directory can be removed.

It might be, that the problem arises only when importing the svgwriter. However, from the traceback I would guess it is related to importing the email.message module from the standard lib. Might be something broken there. You probably need to search for the location of the standard lib and check the cache files there ...

Best,


André

Am 18.12.2015 um 22:49 schrieb René Bastian <rba...@mu...>:

> Salut André,
> 
> It is related to the xml-means to generate SVG-code.
> 
> Should i delete all the *.cpython-3?.py? files in directory
> __pycache__ ?
> [Soll ich ...]
> 
> a+
> rb
> 
> 
> Le Fri, 18 Dec 2015 21:59:26 +0100,
> André Wobst <wo...@us...> a écrit :
> 
>> Hi René,
>> 
>> I never faced this problem, I don't really know where it comes from,
>> but it seems a problem when mixing different python versions. See
>> http://stackoverflow.com/questions/514371/whats-the-bad-magic-number-error
>> for example. Maybe the answers to this question help you to resolve
>> the issue.
>> 
>> I guess it's not really related to PyX. You could try to do a "from
>> email import message" first. Does this work, or is this already
>> broken?
>> 
>> Best,
>> 
>> 
>> André
>> 
>> Am 18.12.2015 um 21:48 schrieb René Bastian
>> <rba...@mu...>:
>> 
>>> De: René Bastian <rba...@mu...>
>>> À: PyX User list <pyx...@li...>
>>> Sujet: magic number
>>> 
>>> 
>>> Salut all,
>>> 
>>> compiling old modules using PyX, i got these errors:
>>> 
>>> Traceback (most recent call last):
>>> File "pfb2pyx.py", line 9, in <module>
>>>   from pyx import canvas, path, text, style
>>> File "/home/rbm/Python/PyX-0.14.1/pyx/__init__.py", line 48, in
>>> <module>
>>>   importlib.import_module('.' + module, package='pyx')
>>> File "/usr/local/lib/python3.4/importlib/__init__.py", line 109, in
>>> import_module
>>>   return _bootstrap._gcd_import(name[level:], package, level)
>>> File "/home/rbm/Python/PyX-0.14.1/pyx/canvas.py", line 29, in
>>> <module> from . import attr, baseclasses, config, document, style,
>>> trafo, svgwriter, unit
>>> File "/home/rbm/Python/PyX-0.14.1/pyx/document.py", line 24, in
>>> <module>
>>>   from . import bbox, pswriter, pdfwriter, svgwriter, trafo, style,
>>> unit
>>> File "/home/rbm/Python/PyX-0.14.1/pyx/svgwriter.py", line 22, in
>>> <module>
>>>   import io, copy, time, xml.sax.saxutils
>>> File "/usr/local/lib/python3.4/xml/sax/saxutils.py", line 6, in
>>> <module>
>>>   import os, urllib.parse, urllib.request
>>> File "/usr/local/lib/python3.4/urllib/request.py", line 88, in
>>> <module>
>>>   import http.client
>>> File "/usr/local/lib/python3.4/http/client.py", line 69, in
>>> <module> import email.parser
>>> File "/usr/local/lib/python3.4/email/parser.py", line 12, in
>>> <module> from email.feedparser import FeedParser, BytesFeedParser
>>> File "/usr/local/lib/python3.4/email/feedparser.py", line 27, in
>>> <module>
>>>   from email import message
>>> File "/usr/local/lib/python3.4/email/message.py", line 10, in
>>> <module> import uu
>>> ImportError: bad magic number in 'uu': b'\x03\xf3\r\n'
>>> 
>>> ------------
>>> 
>>> I know nothing about magic numbers.
>>> Do you need more infos?
>>> 
>>> a+
>>> 
>>> René
>>> 
>>> 
>>> 
>>> -- 
>>> René Bastian
>>> www.pythoneon.org
>>> 
>>> 
>>> -- 
>>> René Bastian
>>> www.pythoneon.org
>>> 
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> PyX-user mailing list
>>> PyX...@li...
>>> https://lists.sourceforge.net/lists/listinfo/pyx-user
>> 
> 
> 
> 
> -- 
> René Bastian
> www.pythoneon.org
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> PyX-user mailing list
> PyX...@li...
> https://lists.sourceforge.net/lists/listinfo/pyx-user

-- 
by  _ _      _    Dr. André Wobst, Amselweg 22, 85716 Unterschleißheim
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript and PDF figures
 (_/ \_)_/\_/     with Python & TeX: visit http://pyx.sourceforge.net/

Re: [PyX-user] magic number

[René B. <rba...@mu...>]

Salut André,

It is related to the xml-means to generate SVG-code.

Should i delete all the *.cpython-3?.py? files in directory
__pycache__ ?
[Soll ich ...]

a+
rb


Le Fri, 18 Dec 2015 21:59:26 +0100,
André Wobst <wo...@us...> a écrit :

> Hi René,
> 
> I never faced this problem, I don't really know where it comes from,
> but it seems a problem when mixing different python versions. See
> http://stackoverflow.com/questions/514371/whats-the-bad-magic-number-error
> for example. Maybe the answers to this question help you to resolve
> the issue.
> 
> I guess it's not really related to PyX. You could try to do a "from
> email import message" first. Does this work, or is this already
> broken?
> 
> Best,
> 
> 
> André
> 
> Am 18.12.2015 um 21:48 schrieb René Bastian
> <rba...@mu...>:
> 
> > De: René Bastian <rba...@mu...>
> > À: PyX User list <pyx...@li...>
> > Sujet: magic number
> > 
> > 
> > Salut all,
> > 
> > compiling old modules using PyX, i got these errors:
> > 
> > Traceback (most recent call last):
> >  File "pfb2pyx.py", line 9, in <module>
> >    from pyx import canvas, path, text, style
> >  File "/home/rbm/Python/PyX-0.14.1/pyx/__init__.py", line 48, in
> > <module>
> >    importlib.import_module('.' + module, package='pyx')
> >  File "/usr/local/lib/python3.4/importlib/__init__.py", line 109, in
> > import_module
> >    return _bootstrap._gcd_import(name[level:], package, level)
> >  File "/home/rbm/Python/PyX-0.14.1/pyx/canvas.py", line 29, in
> > <module> from . import attr, baseclasses, config, document, style,
> > trafo, svgwriter, unit
> >  File "/home/rbm/Python/PyX-0.14.1/pyx/document.py", line 24, in
> > <module>
> >    from . import bbox, pswriter, pdfwriter, svgwriter, trafo, style,
> > unit
> >  File "/home/rbm/Python/PyX-0.14.1/pyx/svgwriter.py", line 22, in
> > <module>
> >    import io, copy, time, xml.sax.saxutils
> >  File "/usr/local/lib/python3.4/xml/sax/saxutils.py", line 6, in
> > <module>
> >    import os, urllib.parse, urllib.request
> >  File "/usr/local/lib/python3.4/urllib/request.py", line 88, in
> > <module>
> >    import http.client
> >  File "/usr/local/lib/python3.4/http/client.py", line 69, in
> > <module> import email.parser
> >  File "/usr/local/lib/python3.4/email/parser.py", line 12, in
> > <module> from email.feedparser import FeedParser, BytesFeedParser
> >  File "/usr/local/lib/python3.4/email/feedparser.py", line 27, in
> > <module>
> >    from email import message
> >  File "/usr/local/lib/python3.4/email/message.py", line 10, in
> > <module> import uu
> > ImportError: bad magic number in 'uu': b'\x03\xf3\r\n'
> > 
> > ------------
> > 
> > I know nothing about magic numbers.
> > Do you need more infos?
> > 
> > a+
> > 
> > René
> > 
> > 
> > 
> > -- 
> > René Bastian
> > www.pythoneon.org
> > 
> > 
> > -- 
> > René Bastian
> > www.pythoneon.org
> > 
> > ------------------------------------------------------------------------------
> > _______________________________________________
> > PyX-user mailing list
> > PyX...@li...
> > https://lists.sourceforge.net/lists/listinfo/pyx-user
> 



-- 
René Bastian
www.pythoneon.org

Re: [PyX-user] magic number

[André W. <wo...@us...>]

Hi René,

I never faced this problem, I don't really know where it comes from, but it seems a problem when mixing different python versions. See http://stackoverflow.com/questions/514371/whats-the-bad-magic-number-error for example. Maybe the answers to this question help you to resolve the issue.

I guess it's not really related to PyX. You could try to do a "from email import message" first. Does this work, or is this already broken?

Best,


André

Am 18.12.2015 um 21:48 schrieb René Bastian <rba...@mu...>:

> De: René Bastian <rba...@mu...>
> À: PyX User list <pyx...@li...>
> Sujet: magic number
> 
> 
> Salut all,
> 
> compiling old modules using PyX, i got these errors:
> 
> Traceback (most recent call last):
>  File "pfb2pyx.py", line 9, in <module>
>    from pyx import canvas, path, text, style
>  File "/home/rbm/Python/PyX-0.14.1/pyx/__init__.py", line 48, in
> <module>
>    importlib.import_module('.' + module, package='pyx')
>  File "/usr/local/lib/python3.4/importlib/__init__.py", line 109, in
> import_module
>    return _bootstrap._gcd_import(name[level:], package, level)
>  File "/home/rbm/Python/PyX-0.14.1/pyx/canvas.py", line 29, in <module>
>    from . import attr, baseclasses, config, document, style, trafo,
> svgwriter, unit
>  File "/home/rbm/Python/PyX-0.14.1/pyx/document.py", line 24, in
> <module>
>    from . import bbox, pswriter, pdfwriter, svgwriter, trafo, style,
> unit
>  File "/home/rbm/Python/PyX-0.14.1/pyx/svgwriter.py", line 22, in
> <module>
>    import io, copy, time, xml.sax.saxutils
>  File "/usr/local/lib/python3.4/xml/sax/saxutils.py", line 6, in
> <module>
>    import os, urllib.parse, urllib.request
>  File "/usr/local/lib/python3.4/urllib/request.py", line 88, in
> <module>
>    import http.client
>  File "/usr/local/lib/python3.4/http/client.py", line 69, in <module>
>    import email.parser
>  File "/usr/local/lib/python3.4/email/parser.py", line 12, in <module>
>    from email.feedparser import FeedParser, BytesFeedParser
>  File "/usr/local/lib/python3.4/email/feedparser.py", line 27, in
> <module>
>    from email import message
>  File "/usr/local/lib/python3.4/email/message.py", line 10, in <module>
>    import uu
> ImportError: bad magic number in 'uu': b'\x03\xf3\r\n'
> 
> ------------
> 
> I know nothing about magic numbers.
> Do you need more infos?
> 
> a+
> 
> René
> 
> 
> 
> -- 
> René Bastian
> www.pythoneon.org
> 
> 
> -- 
> René Bastian
> www.pythoneon.org
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> PyX-user mailing list
> PyX...@li...
> https://lists.sourceforge.net/lists/listinfo/pyx-user

-- 
by  _ _      _    Dr. André Wobst, Amselweg 22, 85716 Unterschleißheim
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript and PDF figures
 (_/ \_)_/\_/     with Python & TeX: visit http://pyx.sourceforge.net/

[PyX-user] magic number

[René B. <rba...@mu...>]

De: René Bastian <rba...@mu...>
À: PyX User list <pyx...@li...>
Sujet: magic number


Salut all,

compiling old modules using PyX, i got these errors:

Traceback (most recent call last):
  File "pfb2pyx.py", line 9, in <module>
    from pyx import canvas, path, text, style
  File "/home/rbm/Python/PyX-0.14.1/pyx/__init__.py", line 48, in
<module>
    importlib.import_module('.' + module, package='pyx')
  File "/usr/local/lib/python3.4/importlib/__init__.py", line 109, in
import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "/home/rbm/Python/PyX-0.14.1/pyx/canvas.py", line 29, in <module>
    from . import attr, baseclasses, config, document, style, trafo,
svgwriter, unit
  File "/home/rbm/Python/PyX-0.14.1/pyx/document.py", line 24, in
<module>
    from . import bbox, pswriter, pdfwriter, svgwriter, trafo, style,
unit
  File "/home/rbm/Python/PyX-0.14.1/pyx/svgwriter.py", line 22, in
<module>
    import io, copy, time, xml.sax.saxutils
  File "/usr/local/lib/python3.4/xml/sax/saxutils.py", line 6, in
<module>
    import os, urllib.parse, urllib.request
  File "/usr/local/lib/python3.4/urllib/request.py", line 88, in
<module>
    import http.client
  File "/usr/local/lib/python3.4/http/client.py", line 69, in <module>
    import email.parser
  File "/usr/local/lib/python3.4/email/parser.py", line 12, in <module>
    from email.feedparser import FeedParser, BytesFeedParser
  File "/usr/local/lib/python3.4/email/feedparser.py", line 27, in
<module>
    from email import message
  File "/usr/local/lib/python3.4/email/message.py", line 10, in <module>
    import uu
ImportError: bad magic number in 'uu': b'\x03\xf3\r\n'

------------

I know nothing about magic numbers.
Do you need more infos?

a+

René



-- 
René Bastian
www.pythoneon.org


-- 
René Bastian
www.pythoneon.org

Re: [PyX-user] insert/include PDF

[André W. <wo...@us...>]

Hi,

well, you cannot embed EPS in PDF. (Somehow I have in mind that there actually is something like embedding postscript in PDF, which will not be rendered by a PDF renderer, but could be printed on Postscript printers, but I'm missing the details right now.)

What PyX really does for this case is to convert the EPS to a bitmap and put this bitmap in the PDF output. I added this years ago, as it was handy for me at some point in time. But it generates a warning and is by no means a proper embedding. (On the other side, yes, this is a way to go to somehow get other data embedded. Embed it as bitmap data. We can do so for Postscript, PDF and SVG, we support bitmap data for all those output formats.)

Still, our true goal is to be able embed PDF in PDF like we can embed Postscript in Postscript and SVG in SVG. (And for SVG we also have a parsed mode, which actually recreates the graphic data within PyX, with rather serious limitations though, but still quite useful in some cases.)

Right now we cannot embed PDF in PDF.

Best,


André

Am 05.12.2015 um 20:47 schrieb Alan G Isaac <ai...@am...>:

> If this is worth the effort to the OP, I wonder if a round trip would work?
> First convert the PDF to EPS:
> http://tex.stackexchange.com/questions/20883/how-to-convert-pdf-to-eps
> Then create your pyx image, importing the EPS with `epsinclude`.
> Then if PDF output is needed, could this be exported to PDF?
> 
> This is really a question rather than an answer.
> 
> Alan Isaac
> 
> ------------------------------------------------------------------------------
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
> _______________________________________________
> PyX-user mailing list
> PyX...@li...
> https://lists.sourceforge.net/lists/listinfo/pyx-user

-- 
by  _ _      _    Dr. André Wobst, Amselweg 22, 85716 Unterschleißheim
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript and PDF figures
 (_/ \_)_/\_/     with Python & TeX: visit http://pyx.sourceforge.net/

Re: [PyX-user] insert/include PDF

[Alan G I. <ai...@am...>]

If this is worth the effort to the OP, I wonder if a round trip would work?
First convert the PDF to EPS:
http://tex.stackexchange.com/questions/20883/how-to-convert-pdf-to-eps
Then create your pyx image, importing the EPS with `epsinclude`.
Then if PDF output is needed, could this be exported to PDF?

This is really a question rather than an answer.

Alan Isaac

Re: [PyX-user] insert/include PDF

[André W. <wo...@us...>]

Dear René,

well, I'm sorry, PyX cannot (yet) do that.

Best,


André

Am 05.12.2015 um 12:26 schrieb René Bastian <rba...@fr...>:

> 
> 2015.12.05
> 
> Guten Tage & Bonjour,
> 
> how to include PDF files ?
> 
> a+
> 
> René
> 
> -- 
> René Bastian
> www.pythoneon.org
> 
> 
> -- 
> René Bastian
> www.pythoneon.org
> 
> ------------------------------------------------------------------------------
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
> _______________________________________________
> PyX-user mailing list
> PyX...@li...
> https://lists.sourceforge.net/lists/listinfo/pyx-user

-- 
by  _ _      _    Dr. André Wobst, Amselweg 22, 85716 Unterschleißheim
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript and PDF figures
 (_/ \_)_/\_/     with Python & TeX: visit http://pyx.sourceforge.net/

[PyX-user] insert/include PDF

[René B. <rba...@fr...>]

2015.12.05

Guten Tage & Bonjour,

how to include PDF files ?

a+

René

-- 
René Bastian
www.pythoneon.org


-- 
René Bastian
www.pythoneon.org

Re: [PyX-user] Fw: pyx path

[René B. <rba...@fr...>]

No problem

/home/rbm/Python/PyX-0.14.1/pyx/ is False

/home/rbm/Python/PyX-0.14.1/ is True

rb


Le Fri, 27 Nov 2015 13:56:28 +0100,
René Bastian <rba...@fr...> a écrit :

> 
> 
> ----- Message Transféré -----
> 
> Date: Fri, 27 Nov 2015 13:30:31 +0100
> De: René Bastian <rba...@mu...>
> À: pyx...@li...
> Sujet: pyx path
> 
> 
> Was is gnorw ?
> 
> rbm@lenovo:~$ echo $PYTHONPATH
> :/home/rbm/pythoneon/:/home/rbm/bin/:/home/rbm/Python/PyX-0.14.1/pyx/
> rbm@lenovo:~$ cd Python/Pyx-0.14_Essais/
> rbm@lenovo:~/Python/Pyx-0.14_Essais$ python3 halign.py 
> Traceback (most recent call last):
>   File "halign.py", line 1, in <module>
>     from pyx import *
> ImportError: No module named pyx
> rbm@lenovo:~/Python/Pyx-0.14_Essais$ python3
> Python 3.2.3 (default, Feb 20 2013, 14:44:27) 
> [GCC 4.7.2] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import pyx
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
> ImportError: No module named pyx
> >>> 
> 
> gries & kiss
> 
> rb



-- 
René Bastian
www.pythoneon.org

[PyX-user] Fw: pyx path

[René B. <rba...@fr...>]

----- Message Transféré -----

Date: Fri, 27 Nov 2015 13:30:31 +0100
De: René Bastian <rba...@mu...>
À: pyx...@li...
Sujet: pyx path


Was is gnorw ?

rbm@lenovo:~$ echo $PYTHONPATH
:/home/rbm/pythoneon/:/home/rbm/bin/:/home/rbm/Python/PyX-0.14.1/pyx/
rbm@lenovo:~$ cd Python/Pyx-0.14_Essais/
rbm@lenovo:~/Python/Pyx-0.14_Essais$ python3 halign.py 
Traceback (most recent call last):
  File "halign.py", line 1, in <module>
    from pyx import *
ImportError: No module named pyx
rbm@lenovo:~/Python/Pyx-0.14_Essais$ python3
Python 3.2.3 (default, Feb 20 2013, 14:44:27) 
[GCC 4.7.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import pyx
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named pyx
>>> 

gries & kiss

rb
-- 
René Bastian
www.pythoneon.org


-- 
René Bastian
www.pythoneon.org

[PyX-user] ANN: PyX 0.14 released

[André W. <wo...@us...>]

Hi,

We've just released PyX 0.14.1. Starting from this release PyX is distributed at PyPI (see https://pypi.python.org/pypi), as pip will stop working with external hosted files in the near future (see https://www.python.org/dev/peps/pep-0470/). When installing via pip, no "--allow-external PyX" is needed anymore. Note that we completely stopped to distribute PyX on sourceforge. We also removed all file downloads and instead provide the previous releases on PyPI as well.

A very few bugs have also been fixed. See the full changelog below.

Happy PyXing,


Jörg and André


-------------

0.14.1 (2015/11/02):
  - distribution:
    - upload to PyPI (including old releases)
    - remove old releases from sourceforge
  - text module:
    - fix load_def message parser (reported by Mico Filós)
  - normpath:
    - fix intersect with empty normsubpaths (bug #62, thanks to Florent Hivert)

-- 
by  _ _      _    Dr. André Wobst, Amselweg 22, 85716 Unterschleißheim
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript and PDF figures
 (_/ \_)_/\_/     with Python & TeX: visit http://pyx.sourceforge.net/

Re: [PyX-user] bug in texter subsystem

[André W. <wo...@us...>]

Hi Michael,

first of all, thanks a lot for providing a simple example. Without it I probably wouldn't have started to take a look into that right now.

Now, lets see: skip1=True does not work here, as there is an denomsuffix, so it would be wrong to remove the fraction. skip1 is about removing the fraction.

For skipdenom1 there is some documentation in the code:

        - skipdenom1 (boolean) just prints the numerator instead of
          the hole fraction, when the denominator is one and none of the parameters
          denomprefix, denominfix and denomsuffix are set and minuspos is not -1 or the
          fraction is positive

To my understanding (well, I've written the code, but this is many, many years ago) the code does that. We have a denomsuffix, hence skipdenom1 does not work to remove the 1. And it is good that the condition is done that way. skipdenom1 is about skipping the denominator completely, which would also remove the 1/\pi, and this surely would be bad!

What you want is something like skip1 just on the denominator, but without removing the fraction. (skipdenom1 is about removing the fraction.) Note that this is different from skipnum1, which only controls the numerator, and will not remove the fraction by its own. This means, that with the flags available in the rational texter the output you want just cannot be expressed. I don't see an easy solution to fix it within the texter without adding another flag for this case. But I think it would be more harm than good, as it is already rather complicated, and the problem you're facing is very specific (and uncommon).

Still, I can easily think of (at least) two solutions to work around it. The first solution is simpler, but has the problem, that it can only be used, when you know that there will be a tick at 1/\pi. The other is to do it in TeX ... yes, you heard right, you'll see in a moment. It's quite simple in the end of the day.

First solution:

from pyx import *

texter = graph.axis.texter.rational(denomsuffix=r"\pi", skip1=True,
skipdenom1=True)
g = graph.graphxy(
   width = 8,
   x = graph.axis.lin(min=0, max=1),
   y = graph.axis.lin(texter=texter, min=0, max=1,
                      manualticks=[graph.axis.tick.tick(1, label="1\over\pi", labelattrs=[text.mathmode])]),

)
g.writePDFfile()

Second solution:

from pyx import *

text.preamble(r"\def\myover#1{\over{\def\onepi{1\pi}\def\value{#1}\ifx\value\onepi\pi\else#1\fi}}")

texter = graph.axis.texter.rational(denomsuffix=r"\pi", skip1=True,
skipdenom1=True, over=r"{{%s}\myover{%s}}")
g = graph.graphxy(
   width = 8,
   x = graph.axis.lin(min=0, max=1),
   y = graph.axis.lin(texter=texter, min=0, max=1),
)
g.writePDFfile()

Best,


André

PS: Note that you should have a divisor on the axis to match the values to the labels. I guess you just omitted it in this minimized example. You will need to change the value of the manual tick position to 1/pi in the first solution.

PPS: I kept skip1 and skipdenom1 in the code, just as you posted it, to keep the changes minimal, but both flags have no effect anyway.

Am 15.10.2015 um 22:19 schrieb Michael Hartmann <mi...@sp...>:

> Hello,
> 
> I think I found a bug in the texter subsystem. The rational class doesn't
> handle skipdenom=True correctly when denomsuffix is set.
> 
> I have a small example:
> 
> 
> from pyx import *
> 
> texter = graph.axis.texter.rational(denomsuffix=r"\pi", skip1=True, 
> skipdenom1=True)
> g = graph.graphxy(
>    width = 8,
>    x = graph.axis.lin(min=0, max=1),
>    y = graph.axis.lin(texter=texter, min=0, max=1)
> )
> g.writePDFfile()
> 
> 
> The label of the upmost tick is "1/1pi" instead of "1/pi". According to the
> documentation the "1" in the denominator should be omitted.
> 
> The bug is in the file pyx/graph/axis/texter.py, method labels, starting at
> line 389. Unfortuntely, I didn't fully understand the logic of the code, so I
> cannot send you a patch. I've used the latest PyX release 0.14 and Python
> 3.4.2.
> 
> Thank you very much for your help! 
> 
> Kind regards,
> 
> --Michael
> 
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> PyX-user mailing list
> PyX...@li...
> https://lists.sourceforge.net/lists/listinfo/pyx-user

-- 
by  _ _      _    Dr. André Wobst, Amselweg 22, 85716 Unterschleißheim
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript and PDF figures
 (_/ \_)_/\_/     with Python & TeX: visit http://pyx.sourceforge.net/

[PyX-user] bug in texter subsystem

[Michael H. <mi...@sp...>]

Hello,

I think I found a bug in the texter subsystem. The rational class doesn't
handle skipdenom=True correctly when denomsuffix is set.

I have a small example:


from pyx import *

texter = graph.axis.texter.rational(denomsuffix=r"\pi", skip1=True, 
skipdenom1=True)
g = graph.graphxy(
    width = 8,
    x = graph.axis.lin(min=0, max=1),
    y = graph.axis.lin(texter=texter, min=0, max=1)
)
g.writePDFfile()


The label of the upmost tick is "1/1pi" instead of "1/pi". According to the
documentation the "1" in the denominator should be omitted.

The bug is in the file pyx/graph/axis/texter.py, method labels, starting at
line 389. Unfortuntely, I didn't fully understand the logic of the code, so I
cannot send you a patch. I've used the latest PyX release 0.14 and Python
3.4.2.

Thank you very much for your help! 

Kind regards,

--Michael

Re: [PyX-user] text not as individual characters

[Gert-Ludwig I. <ger...@ph...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It seems that the list mailer had (or has) some problems. This is a retry:

Dear André,

thanks a lot for your detailed instructions. This seems to be precisely
what I was looking for. After playing a bit around with UnicodeText, I
would like to make a couple of remarks which might be useful to others
who want to make use of it.

If the texrunner originally was set up with texenc='utf-8', umlauts will
be handled transparently by LaTex and one might expect the same for
UnicodeText. However, it is not going to work with the Computer Modern
Font put as a default because no umlauts are present in this font and
the diaeresis is handled by TeX explicitly. No surprise there, but I
have to confess that I fell into the trap...

As you mentioned in your instructions, formatting parameters still need
to be taken care of. One should be aware though that the graph axis
painter will call text_pt with a list containing these parameters.
Therefore, UnicodeText.text_pt needs *args as an argument. Then, one
probably should take its content seriously and act accordingly, but
that is of course not the purpose of what you called a "crude example".

Thanks again for the help (and Jörg and Alan for the discussions),
best regards,
Gert

- -- 
 Gert-Ludwig Ingold     email: Ger...@Ph...
 Institut für Physik    Phone: +49-821-598-3234
 Universität Augsburg   Fax  : +49-821-598-3222
 D-86135 Augsburg       WWW  : www.physik.uni-augsburg.de/theo1/ingold
 Germany                PGP  : 86FF5A93, key available from homepage
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlWvKZIACgkQ4E2iM4b/WpN8PQCgx1T/OB49/oikJb5FskkaX0pm
WMMAnRcMo5sw9E7jIQzED2ZZkqNLVgnX
=+mFl
-----END PGP SIGNATURE-----

Re: [PyX-user] text not as individual characters

[Joerg L. <jo...@us...>]

Hi Alan,

I did so, of course :-) Ugly sounds to strong and I am sorry if this
came about to be dismissive. I know that matplotlib even tries to
reimplement TeX's boxing algorithm, and I am sure that this
implementation was a lot of work. I would strongly guess, however, that
in order to get proper results you need to have all the metric
information (and other things like virtual fonts), which are part of a
LaTeX distribution. And so you are back to square one.

And to make the PyX perspective more clear: We really tried to focus on
the (La)TeX integration, which I think is still quite unique because it
does not rely on any external tool besides the tex/latex binaries (and
maybe kpsewhich, depending on your configuration). This makes everything
very efficient, and the only drawback remains that a LaTeX distribution
has to be installed. Clearly, there are cases where this is a serious
contraint, but then I wonder in how many of those cases math typesetting
would be needed at all. Hence, I think that from our point of view, it
would be much more important to first support the bare minimum of
TeX-less typsetting. André just sent a mail, how this is possible right
now.

Cheers,

        Jörg

On 14.07.15, Alan G Isaac wrote:
> Understood.  But before you dismiss it as ugly,
> do give it a try.         ;-)
> Cheers,
> Alan
> 
> 
> -----Joerg Lehmann wrote:
> > We are aware of the solution in matplotlib. In my
> > opinion, however, we should not go in the direction of supporting some
> > kind of fake TeX-like math typesetting. It will anyway look somehow
> > ugly, at least if one does not go to the extreme of implementing Knuth's
> > math typesetting algorithm to the last detail. Rather, I would like to
> > see just plain text output, which in many cases would be enough for
> > labeling of graphs.
> 
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> PyX-user mailing list
> PyX...@li...
> https://lists.sourceforge.net/lists/listinfo/pyx-user
> 

Re: [PyX-user] text not as individual characters

[André W. <wo...@us...>]

Dear Gert,

first of all, as Jörg already wrote, as long as we use the TeX typesetting engine, we get told (from the dvi file we're reading) to output text at certain positions. Each character might be placed independently, or groups of characters might be output at once, but as soon as kerning corrections take place, a new text output box is created. It's just the way it is. We could try to combine those boxes, but we don't do that.

Due to some internal refactoring of the text handling code, we're getting closer to typeset text without TeX. Well, basically we have that already, we actually do have it for quite some time (many years) already. But starting with PyX 0.13 we are now able to replace the typesetting system transparently, that it also works for text typeset by the axis painter without changing anything in there, for example. Here is some crude example:

    from pyx import unit
    from pyx.config import open, format
    from pyx.font import T1font
    from pyx.font.t1file import from_PF_bytes
    from pyx.font.afmfile import AFMfile

    class UnicodeText:

        def __init__(self, fontname="cmr10", size=10):
            self.font = T1font(from_PF_bytes(open(fontname, [format.type1]).read()),
                               AFMfile(open(fontname, [format.afm], ascii=True)))
            self.size = size

        def preamble(self):
            raise NotImplemented()

        def reset(self):
            raise NotImplemented()

        def text_pt(self, x_pt, y_pt, text, **kwargs):
            return self.font.text_pt(x_pt, y_pt, text, self.size, **kwargs)

        def text(self, x, y, *args, **kwargs):
            return self.text_pt(unit.topt(x), unit.topt(y), *args, **kwargs)

Of course we would need to properly handle the formatting parameters like text.halign etc. from the text module ourself. Instead, in this example I pass additional parameters to the font text output creation, which makes it possible for me to access some features provided here. This is just for testing.

Let me show how to use it:

    from pyx import *

    text.set(cls=UnicodeText)

    c = canvas.canvas()
    c.text(0, 1, "Hello, world! AV")
    c.text(0, 0, "Hello, world! AV", kerning=True)
    c.writePDFfile(write_compress=False)

The result unicodetext.pdf is attached, and I disabled compression to make the page stream readable. As you can see, the text typeset without kerning is just a single output, but also the one with kerning is combined into a single text output with the kerning corrections embedded.

Now you can open this file in Illustrator. It will tell you (if you haven't installed CMR10), that the font is missing. Now you can just replace the font. I did so with Minion Pro Condensed as an example. Updating the artboard to the file content, which is another one-click operation, you get the attached output (without any retyping or the like). It nice to see, that this even works with kerning as we have inserted it as relative operations, but I guess the kerning correction just remains the one from the original font (to my understanding there is no option to do so differently, but in the end of the day I don't know that the Adobe Software really does here internally when changing the font). Anyway, the result looks promising as you can see in the second file. With this workflow (and using text output created on the font level, not via the TeX typesetting engine), I can alter the font without any retyping. By the way, I saved this second file without page stream compression as well, so you can just look inside and find out the commands used to typeset the text, which have been split here at kerning points by Illustrator, interestingly.

Note that all this will only work for simple text output, not for formulas. For the later typically the font and the font sizes are switched and the output is placed on various positions. This just needs to be redone for the other font. But for simple text like axis labels (without super-/sub-script) we could probably get this working that way. On the other hand this also means, that this workflow of replacing the font should already be possible also for text typeset by TeX when no kerning is active and you have single words only. In that case the DVI should contain groups of characters. However, every kerning and also every new word starts a new text output. However, you will notice that the output behavior of TeX in this respect depends on the font. For example the text in http://pyx.sourceforge.net/examples/text/font.html is typeset by placing each character separately, which however is not the case when using Computer Modern Roman. This was my observation some time ago. It might depend on the TeX installation in use ...

So, no solution for the moment, but it's interesting to have been informed about your problem and to do some tests. We probably can improve the situation somewhat, when typesetting with a single font and by not using TeX anymore will become a general feature. This is already in the making, but given the slow development speed of PyX, this will probably be still a few years in the future.

Best,


André

Am 13.07.2015 um 16:55 schrieb Gert-Ludwig Ingold <ger...@ph...>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Dear André, dear Jörg,
> 
> in a figure prepared with PyX, a professional designer had to replace the
> labels because the journal is using a non-free font which I do not own.
> Since PyX relies on (La)TeX for typesetting, each character is placed
> individually and (La)TeX ensures the proper kerning. Of course, for a
> different font the kerning will be different so that simply switching the
> font is not an option. Instead, the designer had to retype the text which
> not only costs time but also introduces a potential source of errors. In
> this special case, it would be advantageous if it were possible to set
> longer text in one single box so that the designer could just switch the
> font. This may well be impossible to do with PyX, but I wonder whether
> there exists a trick which could help in this situation. Or may be I just
> oversee something obvious? Any help is appreciated.
> 
> Best regards,
> Gert
> 
> - -- 
> Gert-Ludwig Ingold     email: Ger...@Ph...
> Institut für Physik    Phone: +49-821-598-3234
> Universität Augsburg   Fax  : +49-821-598-3222
> D-86135 Augsburg       WWW  : www.physik.uni-augsburg.de/theo1/ingold
> Germany                PGP  : 86FF5A93, key available from homepage
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> 
> iEYEARECAAYFAlWj0VoACgkQ4E2iM4b/WpPjDACeIlGDi5JSjbO96WWkyNxo5TLT
> 9tgAoJDDwo21nbqrClXeHWM/luPex2l5
> =Q1eg
> -----END PGP SIGNATURE-----
> 
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> PyX-user mailing list
> PyX...@li...
> https://lists.sourceforge.net/lists/listinfo/pyx-user

-- 
by  _ _      _    Dr. André Wobst, Amselweg 22, 85716 Unterschleißheim
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript and PDF figures
 (_/ \_)_/\_/     with Python & TeX: visit http://pyx.sourceforge.net/

Re: [PyX-user] text not as individual characters

[Alan G I. <ai...@am...>]

Understood.  But before you dismiss it as ugly,
do give it a try.         ;-)
Cheers,
Alan


-----Joerg Lehmann wrote:
> We are aware of the solution in matplotlib. In my
> opinion, however, we should not go in the direction of supporting some
> kind of fake TeX-like math typesetting. It will anyway look somehow
> ugly, at least if one does not go to the extreme of implementing Knuth's
> math typesetting algorithm to the last detail. Rather, I would like to
> see just plain text output, which in many cases would be enough for
> labeling of graphs.

Re: [PyX-user] text not as individual characters

[Joerg L. <jo...@us...>]

Hi Alan,

Thanks for the link. We are aware of the solution in matplotlib. In my
opinion, however, we should not go in the direction of supporting some
kind of fake TeX-like math typesetting. It will anyway look somehow
ugly, at least if one does not go to the extreme of implementing Knuth's
math typesetting algorithm to the last detail. Rather, I would like to
see just plain text output, which in many cases would be enough for
labeling of graphs.

Cheers,

        Jörg

On 13.07.15, Alan G Isaac wrote:
> Joerg Lehmann wrote:
> > I remember that André had been working on supporting some
> > primitive form of typesetting without (La)TeX.
> 
> 
> A lot of work has already been done in this direction:
> http://matplotlib.org/users/mathtext.html
> 
> fwiw,
> Alan Isaac
> 
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> PyX-user mailing list
> PyX...@li...
> https://lists.sourceforge.net/lists/listinfo/pyx-user

Re: [PyX-user] text not as individual characters

[Alan G I. <ai...@am...>]

Joerg Lehmann wrote:
> I remember that André had been working on supporting some
> primitive form of typesetting without (La)TeX.


A lot of work has already been done in this direction:
http://matplotlib.org/users/mathtext.html

fwiw,
Alan Isaac

Re: [PyX-user] text not as individual characters

[Gert-Ludwig I. <ger...@ph...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear Jörg,

> The "splitting" of the text happens in the (La)TeX -> DVI step. 
> Afterwards, one would need (by some heuristics, I would guess) to 
> assemble the different boxes again.
> 
> But I remember that André had been working on supporting some
> primitive form of typesetting without (La)TeX. That would probably the
> best for your use case...

I agree and somehow, I also vaguely remember that André mentioned
something like this at some point. However, I am not aware of anything
documented. But may be André can say more about it...

Best regards,
Gert

- -- 
 Gert-Ludwig Ingold     email: Ger...@Ph...
 Institut für Physik    Phone: +49-821-598-3234
 Universität Augsburg   Fax  : +49-821-598-3222
 D-86135 Augsburg       WWW  : www.physik.uni-augsburg.de/theo1/ingold
 Germany                PGP  : 86FF5A93, key available from homepage
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlWj3xgACgkQ4E2iM4b/WpMsyQCg1joIaKqI5HoQSD9w2X7301q+
x4cAoN8Wuh+KeCJCnMGQxZcmycNtReeE
=kTWy
-----END PGP SIGNATURE-----

Re: [PyX-user] text not as individual characters

[Joerg L. <jo...@us...>]

Dear Gert,

The "splitting" of the text happens in the (La)TeX -> DVI step.
Afterwards, one would need (by some heuristics, I would guess) to
assemble the different boxes again.

But I remember that André had been working on supporting some primitive
form of typesetting without (La)TeX. That would probably the best for
your use case...

Best regards,

        Jörg

On 13.07.15, Gert-Ludwig Ingold wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Dear André, dear Jörg,
> 
> in a figure prepared with PyX, a professional designer had to replace the
> labels because the journal is using a non-free font which I do not own.
> Since PyX relies on (La)TeX for typesetting, each character is placed
> individually and (La)TeX ensures the proper kerning. Of course, for a
> different font the kerning will be different so that simply switching the
> font is not an option. Instead, the designer had to retype the text which
> not only costs time but also introduces a potential source of errors. In
> this special case, it would be advantageous if it were possible to set
> longer text in one single box so that the designer could just switch the
> font. This may well be impossible to do with PyX, but I wonder whether
> there exists a trick which could help in this situation. Or may be I just
> oversee something obvious? Any help is appreciated.
> 
> Best regards,
> Gert
> 
> - -- 
>  Gert-Ludwig Ingold     email: Ger...@Ph...
>  Institut für Physik    Phone: +49-821-598-3234
>  Universität Augsburg   Fax  : +49-821-598-3222
>  D-86135 Augsburg       WWW  : www.physik.uni-augsburg.de/theo1/ingold
>  Germany                PGP  : 86FF5A93, key available from homepage
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> 
> iEYEARECAAYFAlWj0VoACgkQ4E2iM4b/WpPjDACeIlGDi5JSjbO96WWkyNxo5TLT
> 9tgAoJDDwo21nbqrClXeHWM/luPex2l5
> =Q1eg
> -----END PGP SIGNATURE-----
> 
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> PyX-user mailing list
> PyX...@li...
> https://lists.sourceforge.net/lists/listinfo/pyx-user

[PyX-user] text not as individual characters

[Gert-Ludwig I. <ger...@ph...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear André, dear Jörg,

in a figure prepared with PyX, a professional designer had to replace the
labels because the journal is using a non-free font which I do not own.
Since PyX relies on (La)TeX for typesetting, each character is placed
individually and (La)TeX ensures the proper kerning. Of course, for a
different font the kerning will be different so that simply switching the
font is not an option. Instead, the designer had to retype the text which
not only costs time but also introduces a potential source of errors. In
this special case, it would be advantageous if it were possible to set
longer text in one single box so that the designer could just switch the
font. This may well be impossible to do with PyX, but I wonder whether
there exists a trick which could help in this situation. Or may be I just
oversee something obvious? Any help is appreciated.

Best regards,
Gert

- -- 
 Gert-Ludwig Ingold     email: Ger...@Ph...
 Institut für Physik    Phone: +49-821-598-3234
 Universität Augsburg   Fax  : +49-821-598-3222
 D-86135 Augsburg       WWW  : www.physik.uni-augsburg.de/theo1/ingold
 Germany                PGP  : 86FF5A93, key available from homepage
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlWj0VoACgkQ4E2iM4b/WpPjDACeIlGDi5JSjbO96WWkyNxo5TLT
9tgAoJDDwo21nbqrClXeHWM/luPex2l5
=Q1eg
-----END PGP SIGNATURE-----

Re: [PyX-user] ANN: PyX 0.14 released

[André W. <wo...@us...>]

Hi Simon,

looks like the same error we had recently, to be fixed by:

andre@mbp:~/python/pyx$ svn diff
Index: pyx/text.py
===================================================================
--- pyx/text.py	(revision 3627)
+++ pyx/text.py	(working copy)
@@ -318,7 +318,7 @@
             while m:
                 if not os.path.isfile(config.get("text", "chroot", "") + m.group("filename")):
                     return msg
-                r, m = remove_pattern(texmessage.quoted_file_pattern, r)
+                r, m = remove_pattern(p, r)
         return r
 
     quoted_graphics_pattern = re.compile(r'<"(?P<filename>[^"]+\.eps)">')


I'll make a new PyX release as soon as possible to fix the issue. In the mean time please edit the text.py as indicated.

Best,


André

Am 27.06.2015 um 03:15 schrieb Simon Burton <si...@ar...>:

> 
> On Thu, 30 Apr 2015 23:48:51 +0200
> André Wobst <wo...@us...> wrote:
> 
>> 
>> List of changes
>> ===============
>> 
>> 0.14 (2015/04/30):
>>  - new svgwriter module:
>>    - complete SVG output
>>    - SVG font output disabled by default due to missing support by
>>      most browsers, fallback by rendering fonts as paths
> 
> I'm very excited to read this as I have been looking for a way
> to render beautiful PyX figures in web pages (including scalable
> math, etc.) Is this possible now ?
> 
> I had a go at making an svg figure, but when I include math I get the
> following error (this works fine with the pdf backend):
> 
> Traceback (most recent call last):
>  File "./render.py", line 228, in <module>
>    c.text(0., 0., r"hi there! $1+1=2$")
>  File "/usr/local/lib/python3.2/dist-packages/pyx/canvas.py", line 409, in text
>    return self.insert(self.texrunner.text(x, y, atext, *args, **kwargs))
>  File "/usr/local/lib/python3.2/dist-packages/pyx/text.py", line 1428, in wrapped
>    return f(self, *args, **kwargs)
>  File "/usr/local/lib/python3.2/dist-packages/pyx/text.py", line 1464, in text
>    return self.instance.text(*args, **kwargs)
>  File "/usr/local/lib/python3.2/dist-packages/pyx/text.py", line 1304, in text
>    return self.text_pt(unit.topt(x), unit.topt(y), *args, **kwargs)
>  File "/usr/local/lib/python3.2/dist-packages/pyx/text.py", line 1278, in text_pt
>    left_pt, right_pt, height_pt, depth_pt = self.do_typeset(expr, self.texmessages_run_default + self.texmessages_run + texmessages)
>  File "/usr/local/lib/python3.2/dist-packages/pyx/text.py", line 1204, in do_typeset
>    return self._execute(expr, texmessages, STATE_TYPESET, STATE_TYPESET)
>  File "/usr/local/lib/python3.2/dist-packages/pyx/text.py", line 1125, in _execute
>    raise e
>  File "/usr/local/lib/python3.2/dist-packages/pyx/text.py", line 1114, in _execute
>    raise TexResultError("unhandled TeX response (might be an error)")
> pyx.text.TexResultError: unhandled TeX response (might be an error)
> The expression passed to TeX was:
>  \ProcessPyXBox{hi there! $1+1=2$%
>  }{1}%
>  \PyXInput{6}%
> After parsing the return message from TeX, the following was left:
>  *
>  *
>  (/usr/share/texmf-texlive/tex/latex/amsfonts/umsb.fd)
> 
> 
>  (cut after 5 lines; use errordetail.full for all output)
> 
> 
> ------------------------------------------------------------------------------
> Monitor 25 network devices or servers for free with OpManager!
> OpManager is web-based network management software that monitors 
> network devices and physical & virtual servers, alerts via email & sms 
> for fault. Monitor 25 devices for free with no restriction. Download now
> http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
> _______________________________________________
> PyX-user mailing list
> PyX...@li...
> https://lists.sourceforge.net/lists/listinfo/pyx-user

-- 
by  _ _      _    Dr. André Wobst, Amselweg 22, 85716 Unterschleißheim
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript and PDF figures
 (_/ \_)_/\_/     with Python & TeX: visit http://pyx.sourceforge.net/

Re: [PyX-user] ANN: PyX 0.14 released

[Simon B. <si...@ar...>]

On Thu, 30 Apr 2015 23:48:51 +0200
André Wobst <wo...@us...> wrote:

> 
> List of changes
> ===============
> 
> 0.14 (2015/04/30):
>   - new svgwriter module:
>     - complete SVG output
>     - SVG font output disabled by default due to missing support by
>       most browsers, fallback by rendering fonts as paths

I'm very excited to read this as I have been looking for a way
to render beautiful PyX figures in web pages (including scalable
math, etc.) Is this possible now ?

I had a go at making an svg figure, but when I include math I get the
following error (this works fine with the pdf backend):

Traceback (most recent call last):
  File "./render.py", line 228, in <module>
    c.text(0., 0., r"hi there! $1+1=2$")
  File "/usr/local/lib/python3.2/dist-packages/pyx/canvas.py", line 409, in text
    return self.insert(self.texrunner.text(x, y, atext, *args, **kwargs))
  File "/usr/local/lib/python3.2/dist-packages/pyx/text.py", line 1428, in wrapped
    return f(self, *args, **kwargs)
  File "/usr/local/lib/python3.2/dist-packages/pyx/text.py", line 1464, in text
    return self.instance.text(*args, **kwargs)
  File "/usr/local/lib/python3.2/dist-packages/pyx/text.py", line 1304, in text
    return self.text_pt(unit.topt(x), unit.topt(y), *args, **kwargs)
  File "/usr/local/lib/python3.2/dist-packages/pyx/text.py", line 1278, in text_pt
    left_pt, right_pt, height_pt, depth_pt = self.do_typeset(expr, self.texmessages_run_default + self.texmessages_run + texmessages)
  File "/usr/local/lib/python3.2/dist-packages/pyx/text.py", line 1204, in do_typeset
    return self._execute(expr, texmessages, STATE_TYPESET, STATE_TYPESET)
  File "/usr/local/lib/python3.2/dist-packages/pyx/text.py", line 1125, in _execute
    raise e
  File "/usr/local/lib/python3.2/dist-packages/pyx/text.py", line 1114, in _execute
    raise TexResultError("unhandled TeX response (might be an error)")
pyx.text.TexResultError: unhandled TeX response (might be an error)
The expression passed to TeX was:
  \ProcessPyXBox{hi there! $1+1=2$%
  }{1}%
  \PyXInput{6}%
After parsing the return message from TeX, the following was left:
  *
  *
  (/usr/share/texmf-texlive/tex/latex/amsfonts/umsb.fd)
  
  
  (cut after 5 lines; use errordetail.full for all output)