public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: packages rebuilt for libpng16, tiff-4
Date: Thu, 12 Feb 2015 04:06:00 -0000 [thread overview]
Message-ID: <54DC26B0.2080907@cornell.edu> (raw)
In-Reply-To: <1423701570.12472.120.camel@cygwin.com>
On 2/11/2015 7:39 PM, Yaakov Selkowitz wrote:
> On Wed, 2015-02-11 at 18:12 -0500, Ken Brown wrote:
>> On 2/8/2015 9:56 PM, Yaakov Selkowitz wrote:
>>> * fontconfig-2.11.1-2
>>
>> I see that you decided not to restore the TeX Live font directories to
>> /etc/fonts/fonts.conf. If that's your actual decision, and not just an
>> oversight,
>
> It was an oversight; thanks for the reminder. As for a decision:
>
> AFAICS these fonts aren't intended for general usage (e.g. within X), so
> I've tried to understand how fontconfig should be used within TeX Live.
> In Fedora, for instance, the texlive font directories are not in
> fonts.conf:
>
> http://pkgs.fedoraproject.org/cgit/fontconfig.git/tree/fontconfig.spec#n66
>
> and the texlive package doesn't include any references to conf.d or
> conf.avail:
>
> http://pkgs.fedoraproject.org/cgit/texlive.git/tree/texlive.spec
>
> However, Arch Linux's documentation actually addresses this clearly:
>
> https://wiki.archlinux.org/index.php/TeX_Live#Fonts
>
> and suggests a solution similar to yours by providing the file in
> conf.avail without automatically creating the symlink.
>
> The TeX Live manual further suggests that such a file may already
> included in xetex:
>
> https://www.tug.org/texlive/doc/texlive-en/texlive-en.html#x1-350003.4.4
>
> But I don't see such a file on my system, nor is it mentioned in
> Fedora's texlive.spec. Besides the location, though, the solution is
> the same.
>
>> then I guess one of the TeX Live packages should add a
>> suitable file to /usr/share/fontconfig/conf.avail, with a link to it in
>> /etc/fonts/conf.d. Or I could just add the file directly to
>> /etc/fonts/conf.d and skip the symlink, whichever you prefer. The
>> contents would be
>>
>> <?xml version="1.0"?>
>> <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
>> <fontconfig>
>> <dir>/usr/share/texmf-dist/fonts/opentype</dir>
>> <dir>/usr/share/texmf-dist/fonts/truetype</dir>
>> <dir>/usr/share/texmf-dist/fonts/type1</dir>
>> </fontconfig>
>>
>> and I would call it 09-texlive.conf, as suggested in the TeX Live manual.
>>
>> Is this how you want me to handle it?
>
> Based on the above, and various mailing list discussions on the topic, I
> think we should provide that file but NOT the symlink, and document this
> in an appropriate place.
That sounds reasonable. I think I'll provide the file in
texlive-collection-basic, and I'll put the documentation in a suitable README
file and in the release announcement.
Ken
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
prev parent reply other threads:[~2015-02-12 4:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 3:00 Yaakov Selkowitz
2015-02-11 23:12 ` Ken Brown
2015-02-12 0:39 ` Yaakov Selkowitz
2015-02-12 4:06 ` Ken Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54DC26B0.2080907@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-xfree@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).