Re: wcout, wprintf() only print English
On Feb 24, 12:46 pm, Rolf Magnus <ramag...@t-online.de> wrote:
James Kanze wrote:
On Feb 23, 11:33 am, Rolf Magnus <ramag...@t-online.de> wrote:
Ioannis Vranos wrote:
Ioannis Vranos wrote:
Has anyone actually managed to print non-English text by
using wcout or wprintf and the rest of standard, wide
[john@localhost src]$ cat main.cc
using namespace std;
Are you sure that you stored your source file in the same
encoding the compiler expects as source character set?
Are you sure the compiler even allows anything but US ASCII as
I don't know, but if it doesn't, the file was not stored in
the encoding that the compiler expected ;-)
I guess my real point is that you've got to read the compiler
documentation, to find out what it supports. Supposing you can
The OP could use the \u notation to specify his wide characters.
In theory. Can you really imagine maintaining code in which
strings like his are all written using UCN's?
It is, of course, the only halfway portable approach. But IMHO,
it means that he'll need some sort of pre-processor which
converts his characters to UCN's. (It shouldn't be that hard to
write---something like ten or twenty lines of C++. But of
course, in order to write it, you have to know the encoding
Before going any further, we have to know 1) how the Greek
characters are encoded. (Probably UTF-8, since that what my
editor is configured for, and I'm seeing them correctly.)
Content-Type: text/plain; charset=ISO-8859-7; format=flowed
But the encoding used in the posting need not be the same as
the encoding in the original source file.
And the encoding used in the posting need not be the encoding
which I get when I copy/paste it in my environment:-). I'd
completely forgotten about that aspect. Especially, as I'm
using Google to read news, and have configured my browser to
tell the server that UTF-8 is the preferred encoding. I
wouldn't be surprised if Google were translating it (since it
sends many postings in the same HTML page, and so has to ensure
that they are all in the same encoding), but even if it weren't,
the fonts I'm using here are UTF-8, so the browser will convert
to UTF-8 to display, and probably for copy/paste as well.
And which compiler he's using, which options, and what the
compiler documentation says about input file encodings.
Most likely, he'll have to ask in a group for his compiler
what it accepts, and how to make it accept what he's got.
Yes. No matter how you look at it, the problem is NOT trivial.
James Kanze (GABI Software) email:email@example.com
Conseils en informatique orient=C3=A9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=C3=A9mard, 78210 St.-Cyr-l'=C3=89cole, France, +33 (0)1 30 23 00 3=