[Octave-bug-tracker] [bug #47571] Problem with umlaut in command line

[anonymous]

Follow-up Comment #8, bug #47571 (project octave):

Here is one way to get umlauts in Windows. This works on Windows 7
Professional. Not tested on other versions.

1. Start cmd (Windows command line interface).

2. Type alt-space, then click Properties, go to the Fonts tab, and pick
something Unicode-aware like Consolas. Do not leave it as a bitmap font.

3. Type chcp at the prompt and enter. It will probably say 437. Now type "chcp
65001" and enter. That will set it to UTF-8.

4. Now you'll be able to run some command like "echo Müller". Copy-paste
Müller from somewhere else, or if you have a German keyboard you can type it
directly. Now if you run Octave in CLI mode from the same cmd window, you
should be able to see and input UTF-8 characters.

The command "chcp" changes the code page -- Windows by default uses code page
437 which is the original IBM PC character set from the 1980s, but it also
treats all of UTF-8 as yet another code page (!!!) numbered 65001.

This hack probably needs much more testing with other languages and scripts,
not just German. But if you use it often enough, you can probably write a
batch file to chcp 65001 before running Octave.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47571>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/