X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-3.1 required=5.0	tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Enrico Forestieri <forenr AT lyx DOT org>
Subject: Re: [ANNOUNCEMENT] CALL FOR TESTING: Cygwin 1.7.10
Date: Thu, 8 Dec 2011 14:48:09 +0000 (UTC)
Lines: 25
Message-ID: <loom.20111208T153653-206@post.gmane.org>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: Loom/3.14 (http://gmane.org/)
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

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 ...

-- 
Enrico


--
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