[texworks] new experimental builds
jfkthame at googlemail.com
Sun Dec 20 17:41:08 CET 2009
On 20 Dec 2009, at 16:30, Bruno Voisin wrote:
> Le 20 déc. 2009 à 17:11, Helge Baumann a écrit :
>> So, I'll stay in touch with TeXWorks on my other account and keep on trying all new versions on my standard account until either Qt or Apple solves the problem by accident (or the hell freezes over, whatever comes first ...).
> I don't remember exactly what you've tried, but regarding possible involvement of fontconfig (since this is what TeXworks uses for fonts if I'm not mistaken)
No, for once you're mistaken - fontconfig is only used in Linux or similar (X11) environments, not on OS X or Windows.
(Hmm, it might be used on Windows if people are using personal builds along with libraries from KDE/Win or whatever.... I'm not entirely sure. It's not used by the builds I distribute, though.)
> : for a long time I've been puzzled by seeing files
> created mysteriously in all the fonts-related dirs (/System/Library/Fonts, /Library/Fonts and ~/Library/Fonts) and all of their subdirs if any. Then one day I saw indications somewhere (I don't remember exactly where) that these mysterious files are created by fontconfig.
Yes, that's correct.
> They are created, for example, if you install MPlayer which calls fontconfig. I don't know if they are normally there otherwise, namely if OS X Snow Leopard includes fontconfig and creates these files by default.
I don't think so; I'd be very surprised if that were the case. I think this indicates that you've installed something - such as MPlayer - that was ported from an X11 environment, and not adapted to use native Mac font management. Perhaps even something that runs within the X11 environment on OS X.
Truly "native" Mac programs will not be affected by these files, however.
> Hence, since you obviously already deleted the standard font caches and that didn't solve your problem, did you also try to erase all the encodings.* and fonts.* files in ~/Library/Fonts and its subdirs, log out and back on again, and see whether that has any influence on your problem?
> Bruno Voisin
More information about the texworks