Lugaru's Epsilon
Programmer's
Editor

Context:
Epsilon User's Manual and Reference
   Commands by Topic
      Buffers and Files
         Buffers
         Files
            . . .
            Backup Files
            Line Translation
            DOS/OEM Character Set Support
            File Name Prompts
            File Name Case
         File Variables
            Directory-wide File Variables
            Vi/Vim File Variables
         . . .

Previous   Up    Next
Line Translation  Commands by Topic   File Name Prompts


Epsilon User's Manual and Reference > Commands by Topic > Buffers and Files > Files >

DOS/OEM Character Set Support

Windows programs typically use a different character set than do DOS programs, or programs that run in a Win32 console environment. The DOS character set is known as the DOS/OEM character set, and includes various line drawing characters and miscellaneous characters not in the Windows/ANSI set. The Windows/ANSI character set includes many accented characters not in the DOS/OEM character set. Epsilon for Windows uses the Windows/ANSI character set (with most fonts). Epsilon for Win32 Console uses a DOS/OEM character set by default, but see the console-ansi-font variable.

The oem-to-ansi command converts the current buffer from the DOS/OEM character set to the Windows/ANSI character set. The ansi-to-oem command does the reverse. If any character in the buffer doesn't have a unique translation, these commands warn before translating, and move to the first character without a unique translation.

The find-oem-file command reads a file using the DOS/OEM character set, translating it into the Windows/ANSI character set, and arranges things so when you save the file, the reverse translation automatically occurs.

The commands in this section provide a subset of the functionality available with the Unicode-based commands described in Unicode Features. The oem-to-ansi command is similar to the unicode-convert-from-encoding command. Specify an encoding such as "cp850" or "cp437", using the code page number shown by the "chcp" command at a Windows command prompt. Similarly, the ansi-to-oem command is like the unicode-convert-to-encoding command. The find-oem-file command is like invoking find-file with a numeric prefix argument, so it asks for line translation and encoding options, and specifying the DOS/OEM encoding as above. See Unicode Features for details on setting a default code page and similar options.

Standard bindings:

    oem-to-ansi
   ansi-to-oem
   find-oem-file
 



Previous   Up    Next
Line Translation  Commands by Topic   File Name Prompts


Lugaru Copyright (C) 1984, 2012 Lugaru Software Ltd. All Rights Reserved.