New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add explicit invocation of fontspec and Source Code Pro #537
base: main
Are you sure you want to change the base?
Conversation
@michaelpacer I'm not an expert on this, so maybe I did something wrong. Anyway, here's the output of my testpdf:
So there is some progress, as unicode in markdown cells now output correctly! :) However, in verbatim and code cells, the hat now appears, but nothing under it. Strange. By the way, I installed with |
Palatino does not seem to be installed on travis. |
@Ken-B So now the markdown stuff probably won't work, but it should work for the monospace font. The combining character doesn't actually combine, but I don't know how many fonts will be able to support that. Regardless, I figure this is a big enough improvement it's worth including even if its not enough. For details about what's going on check out: http://tex.stackexchange.com/questions/355081/fonts-using-xetex-why-do-fontspec-and-setmonofont-versus-sourcecodepro-differ/355269?noredirect=1#comment874662_355269 |
@Ken-B I'm specifically trying to avoid anyone needing to download a custom font, so no, the more barebones your system the easier it will be for me to ensure that I'm not relying on my local setup to solve these problems. |
@michaelpacer Ok. I just tested again and got the same output as last time (with the crossed boxes). I'm on osx 10.12.3 by the way. Let me know what I can do to help. |
@Ken-B first try a conversion to |
@Ken-B If you run the tests on your end, are they failing? |
5683ba7
to
a177dd3
Compare
Good morning, @michaelpacer , With 5f5d297 it errors because it can't find the Tex Gyre Pagella font (full output here) The latest (a177dd3) gives following output: So unicode output is back, but still nothing in the code cells. This is running The nbconvert tests have 3 fails for test_latex and 1 test_pdf. See output here. I'm impressed with the efforts here, I feel we're getting closer, thanks! :) |
…ey're set explicitly
@michaelpacer , your latest commit 059b0b5 fails locally with output below. Let me know what I can do to help.
|
@Ken-B: Could you switch that line to use `\usepackage{tgpagella}` and use
the `\XeTeXtracingfonts` to tell me what the name of the texgyrepagella
fonts is on your system?
…On Tue, Mar 7, 2017 at 8:35 AM, Ken-B ***@***.***> wrote:
@michaelpacer <https://github.com/michaelpacer> , your latest commit
059b0b5
<059b0b5>
fails locally with output below. Let me know what I can do to help.
(/usr/local/texlive/2015/texmf-dist/tex/latex/unicode-math/unicode-math-table.t
ex)))
kpathsea: Running mktextfm texgyrepagella
mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input texgyrepagella
This is METAFONT, Version 2.7182818 (TeX Live 2015) (preloaded base=mf)
kpathsea: Running mktexmf texgyrepagella
! I can't find file `texgyrepagella'.
<*> ...; mag:=1; nonstopmode; input texgyrepagella
Please type another input file name
! Emergency stop.
<*> ...; mag:=1; nonstopmode; input texgyrepagella
Transcript written on mfput.log.
grep: texgyrepagella.log: No such file or directory
mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input texgyrepagella' failed to make texgyrepagella.tfm.
kpathsea: Appending font creation commands to missfont.log.
*************************************************
* fontspec warning: "icu-feature-not-exist-in-font"
*
* OpenType feature 'Numbers=OldStyle,Monospaced' (+tnum) not available for
* font 'SourceCodePro-Regular' with script 'Latin' and language 'Default'.
*************************************************
*************************************************
* fontspec warning: "icu-feature-not-exist-in-font"
*
* OpenType feature 'Numbers=OldStyle,Monospaced' (+tnum) not available for
* font 'SourceCodePro-Regular' with script 'Latin' and language 'Default'.
*************************************************
*************************************************
* fontspec warning: "icu-feature-not-exist-in-font"
*
* OpenType feature 'Numbers=OldStyle,Monospaced' (+tnum) not available for
* font 'SourceCodePro-Bold' with script 'Latin' and language 'Default'.
*************************************************
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! fontspec error: "font-not-found"
!
! The font "texgyrepagella" cannot be found.
!
! See the fontspec documentation for further information.
!
! For immediate help type H <return>.
!...............................................
l.32 ...hsfont(Latin,Greek,Digits){texgyrepagella}
?
! Emergency stop.
!...............................................
l.32 ...hsfont(Latin,Greek,Digits){texgyrepagella}
No pages of output.
Transcript written on notebook.log.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#537 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACXg6NyN0y9UFKci-NKpBpPFh7co_qIJks5rjYc1gaJpZM4MIJQm>
.
|
I've added the Afterwards it threw a different error message (it doesn't seem to write the log anymore).
|
@michaelpacer anything I can do to help? Does it work for you locally? |
Hi @Ken-B what I pushed works locally, however I have a really up to date
tex live (in that I just upgraded all the packages) I'm wondering if the
font features that have been distributed with those fonts differ between
the years
Comment the font declarations that are failing in your TeX file and only
use the tgpagella package and then tell me what it's font loading commands
are.
Sorry that this is taking so long but figuring all of this out in a system
agnostic way is proving to be much more challenging than I expected.
…On Sun, Mar 12, 2017 at 13:17 Ken-B ***@***.***> wrote:
@michaelpacer <https://github.com/michaelpacer> anything I can do to
help? Does it work for you locally?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#537 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACXg6Hb1lOYGZvDEkO3J833jwLMdxHWlks5rlFLjgaJpZM4MIJQm>
.
|
@mpacer There was an informative post on the julia forum on typesetting with unicode for latex that might help with this issue: |
This makes unicode characters more generally available in plaintext.
It doesn't technically handle #533 (although it does now seem to catch the combining characters), since it doesn't address the monospace font issue.
@Ken-B could you check to see whether you also see the â because that (now) does seem to work locally for me.