[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Codepages and shell function on w32

From: Lennart Borgman (gmail)
Subject: Re: Codepages and shell function on w32
Date: Mon, 01 Jan 2007 04:05:23 +0100
User-agent: Thunderbird (Windows/20061207)

Eli Zaretskii wrote:
Date: Sun, 31 Dec 2006 14:22:09 +0100
From: "Lennart Borgman (gmail)" <address@hidden>

              (cp-out (read (format "cp%s" (w32-get-console-output-codepage))))
              (cp-in  (read (format "cp%s" (w32-get-console-codepage)))))
            (set-process-coding-system proc cp-out cp-in))

This is wrong: w32-fns.el sets this as follows:

  (setq default-process-coding-system
        (if default-enable-multibyte-characters
            '(undecided-dos . undecided-unix)
          '(raw-text-dos . raw-text-unix)))

The output encoding uses *-unix for a good reason.

Can you please explain a bit more? How should it look? In the case cmdproxy case (the case above) it works for me with this code using Swedish characters in file names for example.

            ;; MSYS: fix-me, does not work
            (set-process-coding-system proc 'windows-1252 'windows-1252))
           ((string-match "/cygwin/" fullprog)
            (message "think it is Cygwin...")
            ;; Cygwin: fix-me, does not work
            (set-process-coding-system proc 'windows-1252 'windows-1252))

Does Cygwin at all support anything beyond the C locale?  If not,
that's the reason why windows-1252 doesn't work for you.

I have no idea. I just sent this code in the hope that someone knew and could correct it. It would be nice if we got it correct in the release. What do I write to test with the C locale?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]