#214 Output pane charset under windows

Feature_Request
closed-fixed
Neil Hodgson
SciTE (619)
5
2005-08-30
2004-07-22
Anonymous
No

Russian (for example) windows uses two different
charsets for input/output in console programs (cp866)
and windowed programs (windows-1251). As result cp866
encoded output of console tools displayed in output
pane as windows-1251 encoded.

Is there are any idea about how to solve this problem?

Discussion

  • Logged In: YES
    user_id=1088911

    In windows consoles uses OEM charset and windows
    applications uses ANSI charset,
    so this patch (SciTE v 1.60) should solve this problem:

    diff U3 scite\win32\SciTEWin.cxx
    scite\win32\SciTEWin.cxx.oemoutput
    --- scite\win32\SciTEWin.cxx Mon Apr 12 10:33:06 2004
    +++ scite\win32\SciTEWin.cxx.oemoutput Thu Jul 22 11:18:30 2004
    @@ -816,6 +816,8 @@
    MakeOutputVisible();
    seenOutput = true;
    }
    + //Convert OEM output to ANSI
    + OemToCharBuff(buffer, buffer, bytesRead);
    // Display the data
    OutputAppendStringSynchronised(buffer, bytesRead);
    }

     
  • Neil Hodgson
    Neil Hodgson
    2004-07-22

    Logged In: YES
    user_id=12579

    The output pane is not a console and may not, depending on
    the tool used, be printing in the OEM CP. I often use tools
    that generate UTF-8 output and this patch would break that use.

     
  • Neil Hodgson
    Neil Hodgson
    2004-07-22

    • assigned_to: nobody --> nyamatongwe
     
  • Logged In: YES
    user_id=1088911

    2 nyamatongwe
    It's true, but I usually use tools that generates OEM
    encoded output, so this patch for me is enough. But, in
    general, I think it should be possible to define output pane
    encoding at command level (command.encoding.0.*...=.. so we
    can use command.replace.selection.0.* with OEM output) and
    at global level (errorlist.encoding=..) as default.

     
  • Neil Hodgson
    Neil Hodgson
    2004-07-27

    Logged In: YES
    user_id=12579

    For consistency, the global settings should be called
    output.code.page / output.character.set. New command
    settings should use the command.mode mechanism rather than
    add more command.* options. I am unlikely to work on any of
    these features.

     
  • Neil Hodgson
    Neil Hodgson
    2004-07-27

    • status: open --> open-wont-fix
     
  • Neil Hodgson
    Neil Hodgson
    2005-08-30

    • status: open-wont-fix --> closed-fixed
     
  • Neil Hodgson
    Neil Hodgson
    2005-08-30

    Logged In: YES
    user_id=12579

    Added output.code.page property.