On 7 October 2016 at 22:53, Jonas Baggett wrote:
Hello,
I am using debian testing and I am trying to use Martin Vogels Symbols with no success so far. I have compiled a file containing the following : \usesymbols[mvs] \setupsymbolset [martinvogel 2] \starttext Telephone : \symbol[Telephone] \stoptext
But it failed to show the telephone symbole in the pdf, unless compiled with texexec instead of context. I have the following lines in the log file (in attachement) : fonts > defining > forced type 'ttf' of 'marvosym' not found fonts > defining > font with asked name 'marvosym' is not found using lookup 'file' fonts > defining > unknown font 'marvosym', loading aborted fonts > defining > unable to define 'marvosym.ttf' as 'currentsymbolfont--0'
marvosym.ttf is located here : /usr/share/fonts/truetype/ttf-marvosym/marvosym.ttf. Then I tried to reload manually the fonts like this : $ export OSFONTDIR="/usr/share/fonts" $ mtxrun --script fonts --reload $ context --generate
Normally marvosym.ttf should be found but it isn't the case as showed by the following command : $ mtxrun --script fonts --list --all --pattern=marvosym* marvosym marvosym marvosym.afm marvosymwithtexsupport marvosym marvosym.afm marvosymwithtexsupportnormal marvosym marvosym.afm
I would suspect that OSFONTDIR or something else in the process doesn't work correctly. ConTeXt will only be able to typeset the document if it can find the font. All the Debian developer can do is add the font to the equivalent of /usr/local/texlive/2016/texmf-dist/fonts/truetype/public/marvosym/marvosym.ttf (not sure where exactly that is), but it might be that their policy is not to duplicate fonts, who knows. So independent of whether or not this gets resolved in Debian, you should figure out why the font isn't found by ConTeXt. It might also be that ConTeXt only finds the Type1 fonts and then stops searching any further. Mojca