RE: National characters under Borland C++ 5.02 Windows/DOS
- Posted by rforno at tutopia.com Aug 04, 2002
- 431 views
Thanks, Igor, but the problem is how to use the standard facilities of Borland C++ 5.02 without too much fuss. Please see my answer to Martin Stachon. Regards. ----- Original Message ----- From: Igor Kachan <kinz at peterlink.ru> Subject: Re: National characters under Borland C++ 5.02 Windows/DOS Hello Ricardo, ---------- > Îò: rforno at tutopia.com > Êîìó: EUforum <EUforum at topica.com> > Òåìà: National characters under Borland C++ 5.02 Windows/DOS > Äàòà: 4 àâãóñòà 2002 ã. 9:19 > > Dear Euphorians: > Of course this is an Off-topic question. > I am having problems with Borland C++ 5.02 because, > when you specify a character string in the editor, > using national characters (in Spanish áéíóúüñ etc.), > it uses the Windows standard for them. However, when > you compile and execute such a program by means of > the facilities that come with the compiler > (for example, the "lightning" button), it executes > the program under a DOS windows, and the national > characters show as strange graphs. > Does someone know a way to avoid this problem? > TIA. This problem exists because of MS DOS and MS Windows have different code pages (CPs). If you are working on plain DOS, in the DOS window or on Windows console, these code pages are 8??, so Windows uses *the fonts* for these CPs, OEM encoding, terminal font. Your *strings* are *stable* but depend on editor you use. ed - DOS encoding, NotePad - Windows (ANSI) encoding, there are editors where you can switch fonts - Jfe and CodeGenie, for example. Use Terminal font in these editors and you'll have DOS encoding for strings. Or you can copy/paste strings from the NotePad's txt files into your program under ed. You'll see some strange characters in ed, but the *pure* Windows program will output the right strings. But on consoles - other thing. Compiler do nothing with you strings encoding. Just Windows changes the fonts. There is one exception with ex.exe interpreter. In the *text* modes it uses system DOS fonts, but in *graphics* modes it uses the inner hardly built in fonts. Try please (for more examples about DOS encodings) package: http://www.rapideuphoria.com/nuphor23.zip to get the light (compiled source) PD ex.exe with another built in fonts. That nuphor23.zip is Rob's and my co-work. The interpreters of nuphor23.zip allow any national or special characters (128..255) for identifiers in the Euphoria programs. Or try please my Polyglot package: http://www.rapideuphoria.com/polyglot.zip This program can to work with Chinese, Japanese and Korean now (with many other langs too ;). Regards, Igor Kachan kinz at peterlink.ru