X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 12 Dec 2011 14:26:33 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] CALL FOR TESTING: Cygwin 1.7.10 Message-ID: <20111212132633.GC23590@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <566vd7hfmi3j980ic4m64d7bv91b5qm6uh AT 4ax DOT com> <20111207173808 DOT GA25743 AT calimero DOT vinschen DOT de> <20111207180653 DOT GB25743 AT calimero DOT vinschen DOT de> <20111208083935 DOT GC6602 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 Dec 8 14:31, Enrico Forestieri wrote: > Enrico Forestieri writes: > > > > However, I experimented a bit with the last snapshot, and even using Greek > > or Japanese characters in file names, lyx seems to be working fine. > > Sorry, it was a cursory test. Actually, cygwin_conv_path is only called > for absolute paths. Using an absolute Windows path containing any nonascii > character, makes lyx fail miserably. > > I know this is a no-no for you (even if absolute Windows paths can sneak in > by opening a document created by a Windows version), so I will not insist, > but knowlingly breaking backward compatibility is not nice. I'm not sure what to do here. Breaking backward compatibility is not nice, you're right, but the current behaviour really doesn't make much sense. The easiest way to handle this is to revert the change, but still... Would it be ok if it works the old way (WIN_A uses the Cygwin codeset) for applications built under 1.7.9 and earlier, and the new way (WIN_A uses Win32 ANSI/OEM codepage) for applications built under 1.7.10 and later? That means the current lyx continues to work and you can patch lyx upstream accordingly to follow the new behaviour. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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