-
Notifications
You must be signed in to change notification settings - Fork 161
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
User feedback when trying to use Unicode without necessary fonts #173
Comments
Thanks for reporting. What happens if you remove the |
Without the |
How about if you add Assuming that's correct, I didn't realize that |
(I composed this before you wrote that last comment:) If I run
Output of
|
Yes! Adding
Thanks! |
OK. I'm going to repurpose this issue to be about the user experience: if someone is doing what you initially tried, there should be some feedback suggesting that fontspec be loaded. |
Note to self: the right place to do this might be the |
…encountered I've recently gotten a few bug reports from people exploring Tectonic's Unicode capabilities that are not aware of the need to use the `fontspec` package and to choose an appropriate font. Here we add a Tectonic warning message that will hopefully point them in the right direction. In plain XeTeX, the warning is only printed if \tracelostchars is activated, but this seems like a big enough issue (and one that I don't think will happen spuriously?) that I think it is reasonable to always print a message. I can revisit if there are cases where the message gets annoying. I hope that the help message is actually helpful for non-experts. If not, perhaps we should create a dedicated forum thread and point people to it. Closes tectonic-typesetting#173.
With these contents in a file
test.tex
:When I run
tectonic test.tex
, the output pdf says "Strende Heiluft". To make sure, I also triedlatex test.tex; xdvipdfmx test.dvi
, and that result says "Störende Heißluft", as expected.The output of
tectonic --version
isTectonic 0.1.7
. Any other output I should paste?The text was updated successfully, but these errors were encountered: