Windows console uses code page 852 or (it is also named OEM 852)
<DEFAULT_ENCODING>
<str>
<![CDATA[WINDOWS-1252]]>
</str>
</DEFAULT_ENCODING>
The only related source file(s) that I found was editorconfigurationdlg.cpp and editor_configuration.xrc.It's a wxWidgets list, if I recall correctly, so changing the conf-file will not work and probably lead to crashes.
Note, backup the the file before trying to edit; note: CB must be closed while editing.
Editing the conf files is NOT recommended as a safe way to do changes.
The list appears to NOT be in the CB source file; so, I am guessing it is Operating System supplied.
I am NOT a CB Developer; this is NOT a safe thing to do (Edit the conf file).
Found in Windows CB default.conf file.Code<DEFAULT_ENCODING>
<str>
<![CDATA[WINDOWS-1252]]>
</str>
</DEFAULT_ENCODING>
Tim S.
I tried iso8859-2 but it's not working correctly... generally, it's nosense to use other code page that OEM 852 because MS Console uses it (and wine implementation too probably). So it would be great upgrade 4 Win coders to use Win console code page :D.
I tried iso8859-2 but it's not working correctly... generally, it's nosense to use other code page that OEM 852 because MS Console uses it (and wine implementation too probably). So it would be great upgrade 4 Win coders to use Win console code page :D.
I gave you enough info; now do some work or shut-up!
Tim S.
But that's nonsense. Why have I to use UTF-8, avoid cin & cout, change too many things ...The nonsense here lays on Microsoft site... If you want code platform independent (as you mentioned earlier) then the easiest way is my approach, and then you have really Unicode support, and not this pseudo implementation from Microsoft... not use cin and cout are the lowest problem you will heave...
I tried iso8859-2 but it's not working correctly... generally, it's nosense to use other code page that OEM 852 because MS Console uses it (and wine implementation too probably). So it would be great upgrade 4 Win coders to use Win console code page :D.
I gave you enough info; now do some work or shut-up!
Tim S.
don't be this rude... jens mentioned that this is a wxWidgets issue and can't be changed that easy...
@oditoter
There are many good reasons to NOT use the win default code page
And there are twice as much reasons to use utf8 (the windows console is a relict from win16 time, and windows should be forced to implement a new console with utf8...) you can read here some statements: http://utf8everywhere.org/But that's nonsense. Why have I to use UTF-8, avoid cin & cout, change too many things ...The nonsense here lays on Microsoft site... If you want code platform independent (as you mentioned earlier) then the easiest way is my approach, and then you have really Unicode support, and not this pseudo implementation from Microsoft... not use cin and cout are the lowest problem you will heave...
BUT if you find some way to set a new codepacge or any other way to successfully use unicode in the windows console, i would really be happy if you can post your solution here!!!!
greetings
@stahta01
Sorry but the only rude person there is(are) ... you. You suggested changing conf files but It was a complete nosense. If the code page had been included in C::B it would be easy to change it there but it isn't (the same problem on Windows...). So I just ignored your opinion (I remind you that you said 'I'm not a C::B dev) waiting for someone who knows more. And jens confirmed what I thought.
@BlueHazzard
Could you help me to make code changing font to Lucida Console in my program (to console...)? I'm quite newbie in programming (you see... still in console) and I guess that it is included in windows.h . I tried on my own using prepared code but I failed.
Maybe it'd be nice workaround by the time I start coding windows apps ;)
Please calm down.@stahta01
Sorry but the only rude person there is(are) ... you. You suggested changing conf files but It was a complete nosense. If the code page had been included in C::B it would be easy to change it there but it isn't (the same problem on Windows...). So I just ignored your opinion (I remind you that you said 'I'm not a C::B dev) waiting for someone who knows more. And jens confirmed what I thought.
@BlueHazzard
Could you help me to make code changing font to Lucida Console in my program (to console...)? I'm quite newbie in programming (you see... still in console) and I guess that it is included in windows.h . I tried on my own using prepared code but I failed.
Maybe it'd be nice workaround by the time I start coding windows apps ;)
Are you all incapable of reading!!!
Lazy idiots; not willing to build a single wxWidgets sample are NOT worth my time!!!
Tim S.
I think I found the source of the list "wxFontEncoding".
I suggest building "wxWidgets/samples/font" is the font listed in the sample?
If not, it is likely an issue on your PC or in wxWidgets.
Edit2: I would guess it is a wxWidgets lack of support issue. But, I can not test it since I do NOT have that font on my PC.
Edit3: I would guess the lack of being listed in wxWidgets's common/fmapbase.cpp file is the likely cause of CB not listing it.
Tim S.
Could you help me to make code changing font to Lucida Console in my program (to console...)? I'm quite newbie in programming (you see... still in console) and I guess that it is included in windows.h . I tried on my own using prepared code but I failed.
Maybe it'd be nice workaround by the time I start coding windows apps ;)
I think I found the source of the list "wxFontEncoding".
I suggest building "wxWidgets/samples/font" is the font listed in the sample?
If not, it is likely an issue on your PC or in wxWidgets.
Edit2: I would guess it is a wxWidgets lack of support issue. But, I can not test it since I do NOT have that font on my PC.
Edit3: I would guess the lack of being listed in wxWidgets's common/fmapbase.cpp file is the likely cause of CB not listing it.
Tim S.
Did no one ever read this post!!
Tim S.
I am finished helping this site for a while; I get insulted for posting the rules to ignorant users!!Yes, I agree with that one statement. Sometimes it's really hard to understand what you mean. We're talking about encoding and you ... about fonts. What?! I totally got lost with your solutions.
It is just NOT worth the hassle trying to help the new posters on this site; they are just too ignorant of the rules of this site.
And they are just too ignorant of programming.
And, they seem unable to read and understand my replies.
I wasted over an hour trying to help the OP and they appears to NOT even have read my posts.
Tim S.