Am Tue, 28 May 2013 19:17:21 +0200 schrieb Philipp Gesang: >> But I was more thinking about a way to handle the configuration more >> centralized. I have e.g. currently miktex, TL12 and TL13. All three >> tex-systems have access to the same local texmf-tree where I have >> stored some local fonts, blacklists for luaotfload etc. I think it >> would be useful to have there some configuration file, where I could >> put instructions like "if libertine is in the texmf-tree then use >> it". > This would be a simple matter of drawing up some DSL for > configuration. Then we keep extending it with every feature > request and in a couple years from now we’d end up with some > informally specified bug-ridden implementation of SQL.
;-). Actually I was thinking about a simple way to blacklist a folder or a font. And when I worded it in this way I realized that perhaps the blacklist configuration file could be used. Can one use kpse-Variables and "Wildcards" in the blacklist configuration file? > Also, if we got rid of the ban on “write18”, we could use > fontconfig instead of the database. But on the other side would fontconfig give back a much information as does the current database (which I find quite useful)? > It allows you to write rules > for matching fonts against different criteria. (E.g. I have a > personal substitution set that eliminates the ms core fonts from > about every graphical application except when they are embedded > in pdfs.) > [1] I’m aware that fontconfig probably won’t be available on > Windows. But there should be some equivalent functionality > that other programs use when they “access system fonts”. As I wrote somewhere in the beginning I'm using fontconfig to avoid clashed when using xelatex. On windows fontconfig comes with the TeX-System. But miktex and texlive differ in the locations and the naming for local configuration files: miktex uses fontconfig/config/localfonts2.conf, texlive as far as I can see fonts/conf/local.conf -- Ulrike Fischer http://www.troubleshooting-tex.de/
