public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: tmacchant <tmacchant@yahoo.co.jp>
To: cygwin@cygwin.com
Subject: Re: building octave-4.0.0-rcx on Cygwin
Date: Sat, 09 May 2015 00:38:00 -0000	[thread overview]
Message-ID: <1431131511826-118140.post@n5.nabble.com> (raw)
In-Reply-To: <1431082205600-118123.post@n5.nabble.com>

>> Hi Tatsuro, 
>> you can test my build of rc4 
>>    setup-x86_64.exe -X -O -s http://matzeri.altervista.org
>> 
>> http://matzeri.altervista.org/x86_64/octave/

> Macro 
> 
> I can install them and see the octave-gui and confirm that I can handle
> non-ascii characters in path and > file names. I will test tomorrow
> further. 
> Windows native version cannot handle non-ascii characters in path and file
> names :-(. 

> Thank you for your good job and kindness!!!. 

I can handle multibyte characters encoded utf8 (octave editor uses only utf8
encoding) on terminal window.
(Windows native version uses the codepage. Setting codepage to 65001 does
not solve the problem.)

I am glad the cygwin version octave-4.0 does not suffer the problem as
expected.

Tatsuro



--
View this message in context: http://cygwin.1069669.n5.nabble.com/building-octave-4-0-0-rcx-on-Cygwin-tp118121p118140.html
Sent from the Cygwin list mailing list archive at Nabble.com.

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

      parent reply	other threads:[~2015-05-09  0:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 10:12 tmacchant
2015-05-08 10:50 ` Marco Atzeri
2015-05-08 11:09   ` tmacchant
2015-05-08 17:04     ` Achim Gratz
2015-05-09  2:04       ` tmacchant
2015-05-09  0:38     ` tmacchant [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=1431131511826-118140.post@n5.nabble.com \
    --to=tmacchant@yahoo.co.jp \
    --cc=cygwin@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).