Bug#478704: texlive-xetex: 478704: fontconfig instead
Hi Hilmar, On Tue, 26 Mar 2019, Hilmar Preuße wrote: > > - drop a conf file into /etc/fonts/conf.avail plus the link > > - file a bug against fontconfig to have interest (trigger) on > > /usr/share/texmf-texlive/fonts, too. > > > > The reason, there is already > > /usr/share/texmf/fonts > > in the triggers of fontconfig ... > > > > That sounds like a nice idea, and easy to implement. > > > Ping! > > I guess that was never implemented, right? Which one? The second one is not up to us, but the fontconfig maintainers. Still, I don't think it is a good idea ... I am pretty sure that some fonts will break fontconfig and font selection ... The first version would only allow the admin to activate the fonts on his own responability, ... Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#478704: texlive-xetex: 478704: fontconfig instead
On 05.12.09 16:25, Norbert Preining wrote: > On Sa, 05 Dez 2009, Paul Wise wrote: >> Perhaps adding /usr/share/texmf-texlive/fonts to the fontconfig >> configuration and triggers is the way to go? It would suck to have to > > Hmm, looking into the fontconfig package I find a different solution > even better: > > - drop a conf file into /etc/fonts/conf.avail plus the link > - file a bug against fontconfig to have interest (trigger) on > /usr/share/texmf-texlive/fonts, too. > > The reason, there is already > /usr/share/texmf/fonts > in the triggers of fontconfig ... > > That sounds like a nice idea, and easy to implement. > Ping! I guess that was never implemented, right? Hilmar -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
Bug#478704: texlive-xetex: 478704: fontconfig instead
Norbert Preining prein...@logic.at wrote: So simply linking the top level dirs does not help ... dpkg only sees that I drop file sinto /usr/share/texmf-texlive/... and not into /usr/share/fonts/..., so it will never execute the trigger. Isn't it possible to manually call every trigger in postinst? Again nothing that can be done in the next upload, but it wouldn't be hard in our packaging infrastructure. Regards, Frank -- Dr. Frank Küster Debian Developer (TeXLive) VCD Aschaffenburg-Miltenberg, ADFC Miltenberg B90/Grüne KV Miltenberg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#478704: texlive-xetex: 478704: fontconfig instead
Hi Paul,
long time has passed, but slowly we are reaching TL2009 for Debian
status.
On Mo, 23 Feb 2009, Paul Wise wrote:
It would be much better to export them to fontconfig instead, I plan to
remove defoma from Debian for squeeze.
That sounds a good idea. So I have some questions (since I want to
do that for TL2009, but also for lmodern)
Install the fonts in /usr/share/fonts/opentype/something instead.
links would do it?
Add a config file /etc/fonts/conf.avail/90-something.conf and a symlink
to it in /etc/fonts/conf.d/. The config file should contain this:
Sounds easier.
Some questions:
?xml version=1.0?
!DOCTYPE fontconfig SYSTEM /etc/fonts/fonts.dtd
fontconfig
dir/usr/share/texmf-texlive/fonts/opentype/public/dir
/fontconfig
Does that mean that all fonts in *all* directories *below*
/usr/share/texmf-texlive/fonts/opentype/public
are added?
That way we simply can add that config file in texlive-common and have
all the fonts, whenever they are installed, automatically included?
Probably some fc-cache call are necessary?
Is there a debhelper dh_* for that?
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, JapanTU Wien, Austria Debian TeX Task Force
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
SCOPWICK (n.)
The flap of skin which is torn off you lip when trying to smoke an
untipped cigarette.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#478704: texlive-xetex: 478704: fontconfig instead
The plan for defoma removal is here BTW: http://wiki.debian.org/OldPkgRemovals#defoma On Sat, 2009-12-05 at 12:44 +0100, Norbert Preining wrote: On Mo, 23 Feb 2009, Paul Wise wrote: Install the fonts in /usr/share/fonts/opentype/something instead. links would do it? I guess so, it would be a bit hacky though. That said, it will be a while before Xorg supports fontconfig. The initial plan for Xorg is to teach it about subdirectories (#539338) and have it use /usr/share/fonts for the default FontPath like Fedora/etc do. So, linking might be better for now if you care about apps using fonts registered with the X server. Alternatively you could get /usr/share/texmf-texlive/fonts added to the default FontPath for xserver-xorg-core. Add a config file /etc/fonts/conf.avail/90-something.conf and a symlink to it in /etc/fonts/conf.d/. The config file should contain this: Sounds easier. Some questions: ?xml version=1.0? !DOCTYPE fontconfig SYSTEM /etc/fonts/fonts.dtd fontconfig dir/usr/share/texmf-texlive/fonts/opentype/public/dir /fontconfig Does that mean that all fonts in *all* directories *below* /usr/share/texmf-texlive/fonts/opentype/public are added? Correct, I think that is how fontconfig knows about /usr/share/fonts. That way we simply can add that config file in texlive-common and have all the fonts, whenever they are installed, automatically included? Right. Probably some fc-cache call are necessary? Correct for now, IIRC upstream/Fedora had a plan for fontconfig to automatically notice new fonts. I think that is in 2.8.0, which isn't yet in Debian (Keith Packard is working on it apparently). I would suggest using triggers to do that, fontconfig uses them to notify it about new fonts in these 3 directories: $ cat /var/lib/dpkg/info/fontconfig.triggers interest /usr/share/fonts interest /usr/share/ghostscript/fonts interest /usr/share/texmf/fonts Actually, you might just be able to get the directory added to fontconfig itself and let its triggers deal with that. Or move the fonts to /usr/share/texmf/fonts instead of /usr/share/texmf-texlive/fonts. Is there a debhelper dh_* for that? Not AFAIK. My recommendations from the above: * Poke the Debian XSF about the status of #539338 * Ask the Debian XSF to add your fonts to the Xorg default FontPath * Ask the fontconfig maintainers to add your font paths to the default configuration and add your font paths to the fontconfig triggers. OR * Move all your fonts into /usr/share/fonts -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#478704: texlive-xetex: 478704: fontconfig instead
Hi Paul,
thanks for the long and helpful email.
On Sa, 05 Dez 2009, Paul Wise wrote:
My recommendations from the above:
...
OR
* Move all your fonts into /usr/share/fonts
So a simple
ln -s /usr/share/texmf-texlive/fonts/type1 \
/usr/share/fonts/type1/texlive
ln -s /usr/share/texmf-texlive/fonts/opentype \
/usr/share/fonts/truetype/texlive
would suffice?
That sounds nice. I mean, we haven't registered *any* font with
defoma/fontconfig for now, so we can even wait for triggers
and let it stay there without any other changes to the postinst
scripts, or hack a bit and add fc-cache call to those putting
files into fonts/type1 or fonts/opentype.
Would (one or the other or both) be a valid option?
If I don't have to do anything else to do but add the above two links
that I can already do for the upload to unstable which is imminent
(we have hopefully fixed the most serious bugs by now).
Again, thanks a lot and all the best
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, JapanTU Wien, Austria Debian TeX Task Force
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
MUGEARY (n. medical)
The substance from which the unpleasant little yellow globules in the
corners of a sleepy person's eyes are made.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#478704: texlive-xetex: 478704: fontconfig instead
On Sat, 2009-12-05 at 13:22 +0100, Norbert Preining wrote: On Sa, 05 Dez 2009, Paul Wise wrote: My recommendations from the above: ... OR * Move all your fonts into /usr/share/fonts So a simple ln -s /usr/share/texmf-texlive/fonts/type1 \ /usr/share/fonts/type1/texlive ln -s /usr/share/texmf-texlive/fonts/opentype \ /usr/share/fonts/truetype/texlive would suffice? I think you want this directory instead, but yeah: /usr/share/fonts/opentype/texlive Please test it with fc-match before doing it though, obviously. That sounds nice. I mean, we haven't registered *any* font with defoma/fontconfig for now, so we can even wait for triggers and let it stay there without any other changes to the postinst scripts, or hack a bit and add fc-cache call to those putting files into fonts/type1 or fonts/opentype. Would (one or the other or both) be a valid option? Both would be fine, I think it would be better to wait for fontconfig to add the triggers. Once you add the symlinks above the fontconfig trigger stuff isn't needed though because fontconfig already has a trigger on /usr/share/fonts. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#478704: texlive-xetex: 478704: fontconfig instead
Hi Paul,
sorry, didn't get that one ...
On Sa, 05 Dez 2009, Paul Wise wrote:
I think you want this directory instead, but yeah:
/usr/share/fonts/opentype/texlive
There are already loads of .otf fonts in fonts/truetype, that is
the reason I thought I use that one.
Please test it with fc-match before doing it though, obviously.
Will try.
Both would be fine, I think it would be better to wait for fontconfig to
add the triggers.
Once you add the symlinks above the fontconfig trigger stuff isn't
needed though because fontconfig already has a trigger
on /usr/share/fonts.
So I simply wait for fontconfig getting the trigger, and then add the
above symlink to texlive-common (or tex-common) and that's it.
Good plan (because it means nothing to do for now ;-)
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, JapanTU Wien, Austria Debian TeX Task Force
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
EPPING (participial vb.)
The futile movements of forefingers and eyebrows used when failing to
attract the attention of waiters and barmen.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#478704: texlive-xetex: 478704: fontconfig instead
On Sat, 2009-12-05 at 13:55 +0100, Norbert Preining wrote: On Sa, 05 Dez 2009, Paul Wise wrote: I think you want this directory instead, but yeah: /usr/share/fonts/opentype/texlive There are already loads of .otf fonts in fonts/truetype, that is the reason I thought I use that one. Yeah, they aren't particularly well standardised. I don't think it matters much which you use. So I simply wait for fontconfig getting the trigger, and then add the above symlink to texlive-common (or tex-common) and that's it. Uh, no. I'll elaborate the options a bit more: You add the symlinks now and then not worry about the fontconfig stuff at all. Xorg will probably get your fonts when #539338 is fixed, the patch needs testing/checking though, not sure if it follows symlinks. OR Install all your fonts to /usr/share/fonts instead of the current paths and then not worry about the fontconfig stuff at all. Xorg will get your fonts when #539338 is fixed. OR File a bug on fontconfig to get your font paths added to its configuration and triggers. Also file a bug on Xorg to get your font paths added to the default FontPath. The latter is needed to get your fonts into Xorg during the period where it doesn't support fontconfig, which will be quite a while. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#478704: texlive-xetex: 478704: fontconfig instead
Hi Paul,
On Sa, 05 Dez 2009, Paul Wise wrote:
Yeah, they aren't particularly well standardised. I don't think it
matters much which you use.
Hmm, is there no FHS or policy on that?
You add the symlinks now and then not worry about the fontconfig stuff
at all. Xorg will probably get your fonts when #539338 is fixed, the
patch needs testing/checking though, not sure if it follows symlinks.
The discussion on the bug report shows that it goes down 100 levels
of dirs including symlinks.
OR
Install all your fonts to /usr/share/fonts instead of the current paths
and then not worry about the fontconfig stuff at all. Xorg will get your
fonts when #539338 is fixed.
No, I don't want to create links for each and every font.
OR
File a bug on fontconfig to get your font paths added to its
configuration and triggers. Also file a bug on Xorg to get your font
paths added to the default FontPath. The latter is needed to get your
fonts into Xorg during the period where it doesn't support fontconfig,
which will be quite a while.
Hmm, again I am a bit puzzled.
As far as I see there are two things involved:
1. fontconfig accessing the fonts
2. X accessing the fonts
For 1. I can simply wait until fontconfig is trigger-enabled, at which
point the fonts will be available to fontconfig immediately.
For 2. we need mkfontscale be recursively and trigger enabled, as
discussed in bug #539338, but that seems to take ages, right?
But when I put the fonts below truetype and type1 in /u/s/fonts
they are already in the default font path, so the only thing
that would be needed is fixing mkfontscale, and there is already
a bug.
So for what I see there are two options. In both cases I drop
links below /u/s/f/truetype and /u/s/f/type1.
Then
A. I call fc-cache in every font shipping package
B. I do NOT call fc-cache ...
Doing A. would do 1. from above, while doing B. would mean that we
have to wait for font config triggers to be implemented to get
fontconfig accessing the fonts
Regarding 2. X accessing the fonts there are again some options:
- short term solution:
register all the fonts manually with X
- mid term solution:
fix #539338 and the fonts will be available
- long term solution:
Xorg gets fontconfig support built in
The only thing I can take is the short term solution, but I will not
do that, since that are too many fonts and I don't want to do that
for all the directories.
So my proposal is: link as described above and do nothing else for now
Effect: fonts will not be available to X, and to fontconfig only after
someone else has called fc-cache.
After that is in unstable and we have fixed the billions of RC bugs
coming in after the first upload to unstable, I will try to add
the fc-cache calls to the font shipping packages' postinst and postrm
scripts, which will make the fonts available automatically for fontconfig.
On the X front I wait for the above to be fixed, or any other solution,
and do nothing.
Better?
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, JapanTU Wien, Austria Debian TeX Task Force
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
You're one hundred percent positive that the ship which is
crashed on the bottom of this ocean is the ship which you
said you were one hundred percent positive could one
hundred percent positively never crash?
--- Douglas Adams, The Hitchhikers Guide to the Galaxy
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#478704: texlive-xetex: 478704: fontconfig instead
On Sat, 2009-12-05 at 15:27 +0100, Norbert Preining wrote:
On Sa, 05 Dez 2009, Paul Wise wrote:
Yeah, they aren't particularly well standardised. I don't think it
matters much which you use.
Hmm, is there no FHS or policy on that?
Not sure about that.
You add the symlinks now and then not worry about the fontconfig stuff
at all. Xorg will probably get your fonts when #539338 is fixed, the
patch needs testing/checking though, not sure if it follows symlinks.
The discussion on the bug report shows that it goes down 100 levels
of dirs including symlinks.
Cool. That should be enough levels too.
Install all your fonts to /usr/share/fonts instead of the current paths
and then not worry about the fontconfig stuff at all. Xorg will get your
fonts when #539338 is fixed.
No, I don't want to create links for each and every font.
Why would you need to do that?
File a bug on fontconfig to get your font paths added to its
configuration and triggers. Also file a bug on Xorg to get your font
paths added to the default FontPath. The latter is needed to get your
fonts into Xorg during the period where it doesn't support fontconfig,
which will be quite a while.
Hmm, again I am a bit puzzled.
As far as I see there are two things involved:
1. fontconfig accessing the fonts
2. X accessing the fonts
For 1. I can simply wait until fontconfig is trigger-enabled, at which
point the fonts will be available to fontconfig immediately.
fontconfig is already trigger-enabled, but it doesn't know about the
non-standard path TeXLive uses for fonts.
For 2. we need mkfontscale be recursively and trigger enabled, as
discussed in bug #539338, but that seems to take ages, right?
But when I put the fonts below truetype and type1 in /u/s/fonts
they are already in the default font path, so the only thing
that would be needed is fixing mkfontscale, and there is already
a bug.
Right.
So for what I see there are two options. In both cases I drop
links below /u/s/f/truetype and /u/s/f/type1.
Then
A. I call fc-cache in every font shipping package
B. I do NOT call fc-cache ...
You should do B
Doing A. would do 1. from above, while doing B. would mean that we
have to wait for font config triggers to be implemented to get
fontconfig accessing the fonts
...because fontconfig already has triggers for /u/s/f/
Regarding 2. X accessing the fonts there are again some options:
- short term solution:
register all the fonts manually with X
- mid term solution:
fix #539338 and the fonts will be available
- long term solution:
Xorg gets fontconfig support built in
Right.
The only thing I can take is the short term solution, but I will not
do that, since that are too many fonts and I don't want to do that
for all the directories.
Fair enough.
So my proposal is: link as described above and do nothing else for now
Sounds fine to me I guess.
I guess moving all the fonts to the standard /u/s/f/{t,o}/ directory is
out of the question?
Effect: fonts will not be available to X, and to fontconfig only after
someone else has called fc-cache.
The fonts missing from X isn't a regression though, so that is fine.
fontconfig will call fc-cache from the trigger in its postinst, so the
fonts should be available to fontconfig-supporting apps immediately.
After that is in unstable and we have fixed the billions of RC bugs
coming in after the first upload to unstable, I will try to add
the fc-cache calls to the font shipping packages' postinst and postrm
scripts, which will make the fonts available automatically for fontconfig.
That isn't needed because of the existing fontconfig triggers.
On the X front I wait for the above to be fixed, or any other solution,
and do nothing.
Correct.
--
bye,
pabs
http://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Bug#478704: texlive-xetex: 478704: fontconfig instead
On Sa, 05 Dez 2009, Paul Wise wrote:
The discussion on the bug report shows that it goes down 100 levels
of dirs including symlinks.
Cool. That should be enough levels too.
Definitely ;-)
fontconfig is already trigger-enabled, but it doesn't know about the
non-standard path TeXLive uses for fonts.
A I didn't get that one ... so only in case I put the fonts
somewhere else but under /u/s/f/... I would need some action.
A. I call fc-cache in every font shipping package
B. I do NOT call fc-cache ...
You should do B
Got that now.
I guess moving all the fonts to the standard /u/s/f/{t,o}/ directory is
out of the question?
Yes. Many of the fonts are already in the 2007 packages under
/u/s/texmf-texlive/fonts/ as files. We need them *there* (as links or
files) because of mktexlsr is searching only there. So moving the
actual fonts there would mean converting the font files under
/u/s/texmf-texlive/fonts/... into links, and you know what that means
wrt preinst/postinst scripts, PITA.
Thinking about the way triggers work I guess I have to actually
*link* each font file to its respective place in under /u/s/fonts/...
Why? Becasue if we only link
/u/s/fonts/type1/texlive - /u/s/texmf-texlvie/fonts/type1
in texlive-common, then fc-cache will be triggered when texlive-common
is installed/upgraded, but NOT if any other package drops files into
/usr/share/texmf-texlive/fonts/type1.
Bummer.
So simply linking the top level dirs does not help ... dpkg only
sees that I drop file sinto /usr/share/texmf-texlive/... and not
into /usr/share/fonts/..., so it will never execute the trigger.
I guess I have to implement the Link every .otf and pfb file
feature in our meta scripts. (hmmm, maybe that is as simple
as adding two lines to our tpm2deb.cfg file ... I have to try.)
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, JapanTU Wien, Austria Debian TeX Task Force
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
POONA (n.)
Satisfied grunting noise made when sitting back after a good meal.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#478704: texlive-xetex: 478704: fontconfig instead
On Sat, 2009-12-05 at 16:08 +0100, Norbert Preining wrote: So simply linking the top level dirs does not help ... dpkg only sees that I drop file sinto /usr/share/texmf-texlive/... and not into /usr/share/fonts/..., so it will never execute the trigger. I guess I have to implement the Link every .otf and pfb file feature in our meta scripts. (hmmm, maybe that is as simple as adding two lines to our tpm2deb.cfg file ... I have to try.) Bummer :( Perhaps adding /usr/share/texmf-texlive/fonts to the fontconfig configuration and triggers is the way to go? It would suck to have to link every file, which was basically what defoma was doign. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#478704: texlive-xetex: 478704: fontconfig instead
On Sa, 05 Dez 2009, Paul Wise wrote:
Perhaps adding /usr/share/texmf-texlive/fonts to the fontconfig
configuration and triggers is the way to go? It would suck to have to
link every file, which was basically what defoma was doign.
What I don' understand, does font-config have a trigger also on files
in /etc/fonts/conf.d ?
That would be the easiest way, no? One drops a file there, and every
time it is updated/upgraded (or even unchanged) fc-cache would be
called automatically.
THe other option is, as you said, that texlive-common drops the conf
file there (to fonts.avail and a link to .d), and registeres itself
a file trigger on /usr/share/texmf-texlive/fonts/{type1,opentype}.
I think about it.
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, JapanTU Wien, Austria Debian TeX Task Force
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
SLIGO (n.)
An unnamed and exotic sexual act which people like to believe that
famous films stars get up to in private. 'To commit sligo.'
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#478704: texlive-xetex: 478704: fontconfig instead
On Sa, 05 Dez 2009, Paul Wise wrote:
Perhaps adding /usr/share/texmf-texlive/fonts to the fontconfig
configuration and triggers is the way to go? It would suck to have to
Hmm, looking into the fontconfig package I find a different solution
even better:
- drop a conf file into /etc/fonts/conf.avail plus the link
- file a bug against fontconfig to have interest (trigger) on
/usr/share/texmf-texlive/fonts, too.
The reason, there is already
/usr/share/texmf/fonts
in the triggers of fontconfig ...
That sounds like a nice idea, and easy to implement.
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, JapanTU Wien, Austria Debian TeX Task Force
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
KINGSTON BAGPUISE (n.)
A forty-year-old sixteen-stone man trying to commit suicide by
jogging.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#478704: texlive-xetex: 478704: fontconfig instead
It would be much better to export them to fontconfig instead, I plan to remove defoma from Debian for squeeze. To add support for fontconfig you have two options: Install the fonts in /usr/share/fonts/opentype/something instead. Add a config file /etc/fonts/conf.avail/90-something.conf and a symlink to it in /etc/fonts/conf.d/. The config file should contain this: ?xml version=1.0? !DOCTYPE fontconfig SYSTEM /etc/fonts/fonts.dtd fontconfig dir/usr/share/texmf-texlive/fonts/opentype/public/dir /fontconfig -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
