With Ubuntu and fonts there are several things going on. Generally, the system-wide fonts are kept under /usr/share/fonts An alternate place could be /usr/local/fonts That, however, is usually empty because packages put fonts in named directories, e.g., in the ttf dir in /usr/share/fonts TeX-related fonts basically sit in the texmf tree, usually in /usr/share/texmf-texlive/fonts You can also add your own into /usr/share/texmf/fonts Or you can put fonts into ~/.fonts and into your (correct me if I err) ~/.texmf-var/fonts THEN there's defoma, the Debian Font Manager, and I am not sure what ramifications exist there. There is a way to make things like otf fonts in your texmf trees visible to defoma, but I have yet to RTFMP, except to install the cm-super XII package. HTH Charles On Fri, 2008-07-18 at 23:22 +0200, Diego Depaoli wrote:
2008/7/18 Wolfgang Schuster
: but this issue still exists in Ubuntu with such fonts imported from Windows. Where mtxrun catches fonts filenames?
Hi Diego, Hello Wolfgang,
we are talking about two differents things, what you mean is the filename of the fonts you could access with [file:...] in typescripts and which is different on Windows (and all other where the core font packages are used) and on Mac. The font name is another thing and can be different from the file name, you could access fonts by font name with [name:...] in MkIV and this name should (not sure if this is so) be the same on both systems.
That's clear to me, but my question was about the wrong correspondence between font names and filename. As I wrote mtxrun --script fonts --lists showed filenames which I didn't find anywhere, so I thought mtxrun rewrote them. Repeating the same procedure under FreeBSD all goes right. Perhaps in my Ubuntu system there is more than one Times New Roman, Arial..., (even I don't know where they live) and this confused ConTeXt. Next time I boot Ubuntu, I'll search in the whole filesystem. Thanks for the answer and sorry for the noise.