X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=PmjFq3YRJgirjrRolsf/zwwW851GpHonqBmBCUu29/s
	1wVixDqIY2K8Cuba68tbAk6bHD/kgIxov/PR999Rqsylu/9VAtchwifCsWaO7Ak+
	ETfTYF59trQ6OUrKQzbUDvWluFG7vKv/kRDB5ykjBw+IoqiIByik/75xFnN4kcgo
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=oQgLyhTWgYCJTdHdye20JQxyBI4=; b=gJbM+JSDjGvr6/Le+
	mjGJEaQp2JwaFu5C7Wj16x0oCVAfQyiXqJ/Z+XlNQXAQmzPNdhnrj35B9lI0TqEQ
	R7oPbIvmIXKCBfipp1DvJWKGSkMD/rNWjiUOPKc+1Xpx4HdPjYkgFLjlT9KDJcfP
	ZzTdQ7C/rqDvel5szEMm9mqMEI=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2
X-HELO: limerock01.mail.cornell.edu
X-CornellRouted: This message has been Routed already.
Message-ID: <54628A76.6000107@cornell.edu>
Date: Tue, 11 Nov 2014 17:15:18 -0500
From: Ken Brown <kbrown AT cornell DOT edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Latex font problem
References: <636218817 DOT 214922 DOT 1415654556287 DOT JavaMail DOT yahoo AT jws10713 DOT mail DOT gq1 DOT yahoo DOT com> <1819016745 DOT 81408 DOT 1415741486929 DOT JavaMail DOT yahoo AT jws10745 DOT mail DOT gq1 DOT yahoo DOT com>
In-Reply-To: <1819016745.81408.1415741486929.JavaMail.yahoo@jws10745.mail.gq1.yahoo.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 11/11/2014 4:31 PM, phil rosenberg wrote:
>
>> This is discussed in the texlive release announcement
>
>>   https://cygwin.com/ml/cygwin-announce/2014-07/msg00000.html
>
>> under the heading "Fontconfig".  See also
>
>>   https://cygwin.com/ml/cygwin-xfree/2014-05/msg00020.html
>
>> Yaakov, could we get a fontconfig update that fixes this?
>
>> Thanks.
>
>> Ken
>
>
> Having read that post and already seen the discussion about the Windows fonts folder I can understand that it should not be the responsibility of fontconfig to include (and by implication keep up to date) the latex fonts.

The situation with the Windows fonts folder is completely different. 
It's not maintained by Cygwin, and it can be changed without the user 
even being aware of it.  Cygwin apps might try to use fonts in that 
folder without knowing that the font cache is out of date.

Fonts installed by texlive are different because the texlive postinstall 
scripts call fc-cache whenever fonts are installed.  So the font caches 
are kept up to date.  All that's needed for this to work is for 
/etc/fonts/fonts.conf to list the appropriate directories, as they used to.

> Maybe I could suggest the texlive-collection-* packages add the appropriate folder in a file/symlinked file in /etc/fonts/conf.d

That's certainly another option, and I'll do it that way if Yaakov (the 
fontconfig maintainer) prefers it.

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple