@DavidCarlisle I saw you removed your last comment from tex.stackexchange.com/questions/712051. Right now, I would finally be able to try it out. Might I ask you to tell us which line to add to a local copy of psfonts_t1.map for dvips -u local_copy_of_psfonts_t1.map? Is it usyr SymbolMT <usyr.pfb or something else? I know that these changes are less likely to be useful as TeX Live gets updated, but I'd like to try it out just for the purpose of an experiment.
@DavidCarlisle This line alone is probably insufficient or wrong. Though the error message of dvips is gone after appending usyr SymbolMT <usyr.pfb to local_copy_of_psfonts_t1.map and running dvips -u local_copy_of_psfonts_t1.map, the viewer gv still displays boxes where glyphs for the logical and, or, and not should be present. Interestingly, the viewer evince run on the resulting PS file does display these glyphs.
@AlMa1r i deleted comment as I wasn't sure I had the syntax right and didn't want to test (and don't want to test at this time of night:-) you could ask a new question rather than ping here someone else may be awake:-)
@DavidCarlisle I see. No problem, thank you anyway. I realized that two issues overlapped in that question: the warning by dvips/dvipdf and the glyphs not being shown by gv (but being shown by evince for the same PostScript and EPS files, though evince is an unusual viewer for (Encapsulated) PostScript anyway). Now I think that me redrawing the diagram in pstricks (which is used for other diagrams in the document anyway) would be easier.
@Skillmon Nice! I made it a bit of a task for myself to better understand how things work ... I will try to make my way though it, but it is a real challenge =D
@UlrikeFischer writing some installation instructions. When adding map files to miktex do users still use initexmf --edit-config-file updmap and then add one line per map file?
Has anything changed in xelatex in the last year? Regarding the font stuff from last week. Xelatex works just fine on my local TL23. But in overleaf using TL23-xelatex the symbols does not show up in the pdf. They do under lualatex. There does not seem to be any errors or warnings in the log.
I am searching for a TeXworks icon in SVG format (due to some internal code reasons). In the repository, I just found .png. Anyone knowing of some other icons?
This is XeTeX, Version 3.141592653-2.6-0.999995 (TeX Live 2023) (preloaded format=xelatex 2023.8.28) 4 MAR 2024 14:57 entering extended mode \write18 enabled. %&-line parsing enabled. **main.tex (./main.tex LaTeX2e <2023-06-01> patch level 1 L3 programming layer <2023-06-30> (/usr/local/texlive/2023/texmf-dist/tex/latex/base/article.cls Document Class: article 2023/05/17 v1.4n Standard LaTeX document class (/usr/local/texlive/2023/texmf-dist/tex/latex/base/size10.clo File: size10.clo 2023/05/17 v1.4n Standard LaTeX file (size option)
When looking at listfiles I only see differences in the expl3 stuff.
Downloading the PDF from OL we can see it refers to AULogo, but there is no "prefix" in pdffonts and it is not marked as embedded. It is when compiled locally.
@daleif I didn't really believe that this is the reason. The only reason I can imagine that xdvipdfmx doesn't embed the font is a licensing flag. But then it would imho affect the local call too (assuming that you really have the same font and that you didn't change the xetex options).
@UlrikeFischer as I never use xelatex I don't know how to change the settings ;-)
But then why should the other font work?
It is just this font that has issues and it is the only one using these private slots (and does not have a space char, which really should not do anything).
Is it better to send it to OL support? Perhaps they know exactly which settings are used?
@daleif Yes I think you should contact OL support. Locally I would do something like xelatex --output-driver="xdvipdfmx -vv" file to get some terminal info about what xdvipdfmx is doing, but I don't know if/how one can do that on overleaf.
@daleif xdvipdfmx is the normal driver, and the options looks ok. The main question is if you can access the debugging info from the option -vv somehow.
ChkTeX v1.7.6 - Copyright 1995-96 Jens T. Berger Thielemann. Compiled with PCRE regex support. One error printed; No warnings printed; 29 user suppressed warnings; No line suppressed warnings. See the manual for how to suppress some or all of these warnings/errors. output.xdv -> output.pdf [1] xdvipdfmx:warning: Creating ToUnicode CMap failed for "./AULogoRegular.ttf" xdvipdfmx:warning: Failed to load ToUnicode CMap for font "./AULogoRegular.ttf"
2562 bytes written Latexmk: ====List of undefined refs and citations:
The strange thing is, this
xelatex --output-driver="xdvipdfmx" main.tex
fails locally
But this
xelatex main.tex
works locally, where is the difference?
I understand now that this is a bit of a beast to debug.
Fails locally = generate a pdf that is missing a char.
I'm assuming here that things fail because this is a "private slots" only kinda font.
@daleif well the flag only says not to subset not that it can't be embedded, since it only has a few characters anyway that's hardly a restriction but presumably xdvipdfmx doesn't have a code path not to subset fonts of this form so flags that as an error