dev-cpp-users Mailing List for Dev-C++

Well, when i said unicode i wanted say ASCII and UNICODE both. And now I
achieved with ASCII to print them in a console program.... with a little
problem: with cout.put(number), after the character appears the number,
and with putchar(number) 0xfffffff after the character. Well, now I need
find if there are another equivalent funcion I can use for do it.
But I hope it is a problem for console programs, thank you.
I must change to learn windows programs.

I achieved it!!!!!!!!
With this strange thing (and complex, I still need pass to windows and
forget the consoles):
cout << static_cast<char>(static_cast<int>(static_cast<char>(160))) <<
endl;
Where 160 is the ASCII number for á.

I'm new to dev-c++.  is there a way to make the editor recognize line breaks
and white space differently.  actually, i'm not sure if that's the right
question, so i'll describe it.  right now i can click my mouse anywhere in
the editor pane and the cursor will go there but i'm used to (and would
prefer) to have the cursor go to the last available space.  in other words
properly follow the white space/ control characters.  it seems like it just
inserts false whitespace in the entire editor.  thanks,
--tim

> I have a problem with this compiler: When I try to write in the output
> a character with accent or an ñ or ¿ or ¡, the (at this moment
> console) program writes other character, a phi for í, beta for á,
> more-or-less for ñ...

I think this problem will go away if you don't write to the console,
but to a window. Probably the console uses another codepage (for ASCII
characters > 127) as dev-c++ (or any other windows editor, it seems).
I don't know how you can use these characers in a console, but probably
you will have to translate them to some old DOS codepage. Maybe you
can find info at microsoft. (http://msdn.microsoft.com)

... 
> So in Dev-C++ 5, it would be nice to make a compiler with support for
> international characters in an easy way, avoiding the need of
> questioning how to do it (support for unicode). (Or make it work fine).

I never used unicode myself, but I'm almost sure that .c/.cpp source
files are always ASCII, and not unicode - so writing unicode directly
inside the source code can't work. You have to write your unicode
strings with an editor supporting unicode (i'm not sure if it could
be integrated into dev-c++), and then you can display them in your
program, e.g. by using the Win32 API.

--
Elias Pschernig

> Whenever I attempt to put stuff in the .rc file of a project, I receive
> parse errors like the one on line 4 of this code:
> #include "resource.h"
>
> IDD_ABOUT DIALOG DISCARDABLE  0, 0, 239, 66
> STYLE DS_MODALFRAME | WS_POPUP | WS_CAPTION | WS_SYSMENU

You should put #include <windows.h> as the first line of your .rc file,
else you can't use defined values like WS_POPUP..

--
Elias Pschernig

I have a problem with this compiler: When I try to write in the output a
character with accent or an ñ or ¿ or ¡, the (at this moment console)
program writes other character, a phi for í, beta for á, more-or-less
for ñ...
I found a page in www.cplusplus.org with the unicode for characters, and
I tried them with the cout.put() function, and it didn't work. I found
the official page of unicode http://unicode.org, and neither, now  it
writes something like 0xffffffffffffffff. And I haven't find anymore
about it. What can I do?  I CANNOT FORGIVE ME (and nobody) WRITE A BAD
LANGUAGE IF IT IS MINE COUNTRY LANGUAGE. IF I AM SPANISH I MUST SPEAK
AND WRITE PERFECT SPANISH. (i forgive to those who are not spanish or
spanish speaker countries, of course)

In regard to the Chris Hague message about .rc files, I have the same
problem, and I sorry because I don't know solve it, I say for know you
that that problem is not only for one person. I have the same with the
bitmap item. And with the font item it doesn't load the fonts.

So in Dev-C++ 5, it would be nice to make a compiler with support for
international characters in an easy way, avoiding the need of
questioning how to do it (support for unicode). (Or make it work fine).
And solve those problems. That can seem *not-to-this-list-questions* but
that *can-discover-some-fails-of-this-program*.
*or-foolishness-of-who-sends-it*