X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.3 required=5.0	tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_NEUTRAL
X-Spam-Check-By: sourceware.org
Message-ID: <4EE0D2F3.1090606@cornell.edu>
Date: Thu, 08 Dec 2011 10:08:35 -0500
From: Ken Brown <kbrown AT cornell DOT edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] CALL FOR TESTING: Cygwin 1.7.10
References: <announce DOT 20111206093746 DOT GA6222 AT calimero DOT vinschen DOT de>	<566vd7hfmi3j980ic4m64d7bv91b5qm6uh AT 4ax DOT com>	<20111207173808 DOT GA25743 AT calimero DOT vinschen DOT de>	<lq9vd7hue8mef2rkdjpnljn12bm0r6ftum AT 4ax DOT com>	<20111207180653 DOT GB25743 AT calimero DOT vinschen DOT de>	<loom DOT 20111208T012903-910 AT post DOT gmane DOT org> <CAHWeT-ardWG6ExK+p7Jvx6SCRs9+7zGHnVEip3PapnMhTLcw4g AT mail DOT gmail DOT com> <loom DOT 20111208T153653-206 AT post DOT gmane DOT org>
In-Reply-To: <loom.20111208T153653-206@post.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
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

On 12/8/2011 9:48 AM, Enrico Forestieri wrote:
> Andy Koppe writes:
>>
>> On 8 December 2011 00:33, Enrico Forestieri wrote:
>>> Corinna Vinschen writes:
>>>>
>>>> Just so it's clear why I did that, maybe you want to have a look into
>>>> the brief discussion on the cygwin-developers list:
>>>> http://cygwin.com/ml/cygwin-developers/2011-11/msg00000.html
>>>
>>> All good reasons, but you are going to break backward compatibility.
>>> At least, lyx is going to be affected. It currently works with unicode
>>> without a glitch
>>
>> That's impossible if it's using Ansi APIs.
>
> That is not the issue. No Windows API is directly used, but there is the
> need to convert from posix to Windows paths when the TeX engine is native
> Windows. The assumption that cygwin_conv_path does not change the encoding
> is made (this is so until 1.7.9) and if this is going to change it will cause
> havoc. Indeed, the path should be written to the latex file according to the
> encoding used (e.g., \usepackage[cp852]{inputenc}), and lyx takes care of the
> needed conversion. But, if the encoding is changed by cygwin_conv_path ...

I don't use lyx (though I use tex extensively), so maybe there's 
something I don't understand.  But is it really necessary for Cygwin's 
lyx to support a native Windows tex?  Wouldn't it be more reasonable for 
users of a native Windows tex to use a native Windows lyx?

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