textext: Textext (develop branch) not working with Inkscape 1.0 beta on MAC running Catalina

SW versions: Inkscape: 1.0beta1 version MAC OS: Catalina (10.15.1) Textext - develop branch version

Description:

In Inkscape, upon clicking Extensions -> Tex Text, it complains that pdflatex not in path (“pdflatex is NOT found in PATH”). However, pdflatex is in path (“which pdflatex” in the terminal yields “/opt/local/bin/pdflatex”).
I then changed “path = [”/Applications/Inkscape.app/Contents/Resources"]" in requirements_check.py to “path = [”/Applications/Inkscape.app/Contents/Resources",“/opt/local/bin”] ", relaunched Inkscape, and now upon Extensions -> Tex Text, the “TexText 0.11.0” windows opens and when entering a Latex code at the appropriate place (e.g. $\alpha$) and clicking OK, I get a window with the following : 2019-11-10 15:14:48.767 Python[36004:1024964] CoreText note: Client requested name “.SFNSMono-Regular”, it will get Times-Roman rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[NSFont systemFontOfSize:]. 2019-11-10 15:14:48.767 Python[36004:1024964] CoreText note: Set a breakpoint on CTFontLogSystemFontNameRequest to debug. 2019-11-10 15:14:48.768 Python[36004:1024964] CoreText note: Client requested name “.SF NS Mono”, it will get Times-Roman rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[NSFont systemFontOfSize:]. 2019-11-10 15:14:48.851 Python[36004:1024964] CoreText note: Client requested name “.SFNSMono-Regular”, it will get Times-Roman rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[NSFont systemFontOfSize:]. 2019-11-10 15:14:48.851 Python[36004:1024964] CoreText note: Client requested name “.SF NS Mono”, it will get Times-Roman rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[NSFont systemFontOfSize:]. 2019-11-10 15:14:48.851 Python[36004:1024964] CoreText note: Client requested name “.SFNSMono-Regular”, it will get Times-Roman rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[NSFont systemFontOfSize:].

clicking OK I get “The output from the extension could not be parsed”.

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 55 (7 by maintainers)

Most upvoted comments

Summing up: You have to ensure that the python interpreter called by Inkscape contains the Python gtk bindings.

TK and Gtk bindings are confirmed, see my screenshot above. You need to use latest 1.0beta2 though, as linked to above, which contains all the fixes that have happened since the initial 1.0beta2 release.

That said a change of the interpreter in preferences.xml should solve the problem of lunaching the GUI as dicovered by @yoramzarai .

My priority is to make everything work with the interpreter supplied by Inkscape, if possible. I would strongly encourage using that for everything one does related to Inkscape. If something does not work, I need to know about it.

People are still free to use their own interpreter via preferences.xml, but they’ll also be on their own getting this to work. That also applies to changes to the application bundle - should not be necessary and is discouraged.

@zydeon

You are not using the latest Inkscape 1.0beta2 as I linked to above. I can tell because the latest one has Python 3.7.6 and your test shows 3.7.4, please test import tkinter again. (Also, there is Inkscape.app/Contents/Resources/bin/python3 for convenience.)
Are you saying python-interpreter="/usr/bin/python2.7" is not respected by Inkscape? That would be a bug I need to look at.

dehesselle on Feb 18, 2020