https://bugzilla.novell.com/show_bug.cgi?id=635446 https://bugzilla.novell.com/show_bug.cgi?id=635446#c4 --- Comment #4 from Holger Arnold <contact@holgerarnold.net> 2010-11-15 21:28:46 UTC --- Werner, I did not question your efforts, which I really appreciate. Thank you for the repository link. Anyway, I still think it *is* a problem that should be fixed in some way. Do you really want to call a problem a "minor" that makes Inkscape nearly unusable for most users that have texlive installed (and most of them will probably not notice at all that this is related to their texlive installation). In my opinion, whether Inkscape is broken is not relevant for this problem. It is conceptually wrong to put these font files under fontconfig control because these font files are simply not intended to be used by applications other than TeX: - When the TeX fonts are available to fontconfig, then loading any program that does some font handling using fontconfig takes noticeably longer and font lists are cluttered by a large number of incomprehensible font names like "xcmbxsl10". - Contrary to what you said, these fonts are *not* required to display or print documents produced by TeX. PDF documents created by TeX contain embedded fonts, and for DVI documents, TeX fonts are generated on-demand using Metafont. (Otherwise, these files would not be viewable on systems without TeX installed.) To summarize, making the TeX fonts available to fontconfig creates one big problem for Inkscape users and creates small annoyances for everybody. On the other hand, nothing is gained. Why is the size of the texlive package a problem? I assumed that zypp can do incremental updates (aka. patches)? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.