command line argument locale for a guile script

command line argument locale for a guile script

[cong gu]

When guile 2.0 is used to write scripts, one have to manually do a
setlocale at the beginning of the script to enable non-asciiI
character support (why not by default?).

My question is that the command line arguments seems to be parsed
before any code in the script is executed (including the setlocale).
Thus non-ascii arguments are not read correctly.  Do I miss something
or can anybody tell me how to read arguments correctly?

My locale is en_US.UTF-8.  Guile 1.8 works just fine.

$ cat test.scm
#!/usr/bin/guile
!#
(setlocale LC_ALL "")
(write (command-line))

$ ./test.scm 跪了
("./test.scm" "??????")

Re: command line argument locale for a guile script

[David Pirotte]

Hello,

> My question is that the command line arguments seems to be parsed
> ... ... or can anybody tell me how to read arguments correctly?

You must also set port encoding, see manual section 6.14.1 for details:

	(set-port-encoding! (current-output-port) "utf-8")

Cheers,
David

Re: command line argument locale for a guile script

[cong gu]

On Mon, Nov 7, 2011 at 6:59 AM, David Pirotte <david@altosw.be> wrote:
> You must also set port encoding, see manual section 6.14.1 for details:
>
>        (set-port-encoding! (current-output-port) "utf-8")
>

Thanks for responding.

But after a setlocale, utf-8 output is already fine.  The problem is
argument parsing still not work for non-ascii characters.

#!/usr/bin/guile
!#
(setlocale LC_ALL "")
(set-port-encoding! (current-input-port) "utf-8")
(set-port-encoding! (current-output-port) "utf-8")
(write "跪了") ;; fine
(write (command-line)) ;; not work


After I add a setlocale to boot-9.scm, all things works.  But is there
a "normal" way to fix this?

Re: command line argument locale for a guile script

[Nala Ginrut]

[-- Attachment #1: Type: text/plain, Size: 941 bytes --]

On Mon, Nov 7, 2011 at 11:31 PM, cong gu <gucong43216@gmail.com> wrote:

> On Mon, Nov 7, 2011 at 6:59 AM, David Pirotte <david@altosw.be> wrote:
> > You must also set port encoding, see manual section 6.14.1 for details:
> >
> >        (set-port-encoding! (current-output-port) "utf-8")
> >
>
> Thanks for responding.
>
> But after a setlocale, utf-8 output is already fine.  The problem is
> argument parsing still not work for non-ascii characters.
>
> #!/usr/bin/guile
> !#
> (setlocale LC_ALL "")
> (set-port-encoding! (current-input-port) "utf-8")
> (set-port-encoding! (current-output-port) "utf-8")
> (write "跪了") ;; fine
> (write (command-line)) ;; not work
>
>
> After I add a setlocale to boot-9.scm, all things works.  But is there
> a "normal" way to fix this?
>
>
hi, we've talked about this problem and we think it's a real bug.
I sent a patch just now, it is solved. You may see it work soon.

[-- Attachment #2: Type: text/html, Size: 1438 bytes --]

Re: command line argument locale for a guile script

[Thien-Thi Nguyen]

() cong gu <gucong43216@gmail.com>
() Mon, 7 Nov 2011 09:31:49 -0600

   After I add a setlocale to boot-9.scm, all things works.
   But is there a "normal" way to fix this?

Besides boot-9.scm, guile also runs init.scm (in ‘%load-path’).
Perhaps you can experiment with calling ‘setlocale’ there.

Re: command line argument locale for a guile script

[Nala Ginrut]

[-- Attachment #1: Type: text/plain, Size: 574 bytes --]

On Tue, Nov 8, 2011 at 3:16 AM, Thien-Thi Nguyen <ttn@gnuvola.org> wrote:

> () cong gu <gucong43216@gmail.com>
> () Mon, 7 Nov 2011 09:31:49 -0600
>
>   After I add a setlocale to boot-9.scm, all things works.
>   But is there a "normal" way to fix this?
>
> Besides boot-9.scm, guile also runs init.scm (in ‘%load-path’).
> Perhaps you can experiment with calling ‘setlocale’ there.
>
>
I think it's too early to call setlocale so that "locale_charset" can not
realize current locale in time.
I didn't test this method, but it's no hurt to try. ;-)

[-- Attachment #2: Type: text/html, Size: 1046 bytes --]

Re: command line argument locale for a guile script

[Andy Wingo]

On Mon 07 Nov 2011 01:19, cong gu <gucong43216@gmail.com> writes:

> When guile 2.0 is used to write scripts, one have to manually do a
> setlocale at the beginning of the script to enable non-asciiI
> character support (why not by default?).

For the record, this will be fixed in the upcoming 2.0.4.

Thanks for the report and discussion.

Andy
-- 
http://wingolog.org/