[HanoiLUG] vietnamese language and Unicode

[Jean Christophe André]

Phan Thái Trung a écrit :
> But I told about "common Win developing IDE", mean Integrated Dev
> Environment such as common  text editor, compilers.... they usually do
> not allow Win programmer work well with Unicode.
Ok. I didn't know modern Windows IDE editors behaved so bad... Or may be
are you talking about obsoleted-but-still-largely-used softwares like
Foxpro? ;-)

> If you meet traditional Win programmer, you will find that their
> products have difficulty to support Unicode unless they use .NET
> compilers or other 3rd party tools. The best way for now still use
> "TCVN3-like" for apps even in a fully supported unicode OS like WinXP.
Understood. But since we are on a Linux mailing-list, I won't hesitate
to answer this: just stop being constrained by your OS and start using a
*real* developpement environment! And a free one by the way... With all
the source codes available to learn even more and even faster! ;-)

The easiest solution would be to develop using a portable language, but
even if you are still specificaly developping for Windows plateforms,
there is some cross-compilers available with most distributions (look
for the "mingw32" suite, directly available with Ubuntu). I'm talking
about compilers, not IDE. In Linux IDE can be very independant of the
programming language, so they can be used with many of them.

But, even having to work with Windows only, they should have learn to
separate processing from presentation. So the processing code, entered
through a bad behaving IDE environment, doesn't need Unicode input at
all. And the presentation can be entered in separate files through any
good (Unicode compatible) editor. Off course it means they need to learn
to work in a very clean way. But isn't that what we aim to get? Getting
good programmers doing clean programming? ;-)

> Win API funtions that support Unicode are ending by W (wide) and
> functions for non-unicode string are ending by A (ANSI, not ASCII).
> E.g GetWindowTextW() vs. GetWindowTextA(). That's why I called "ANSI"
> like MS way.
So we were both right, except this is one more proof (if one was needed)
that the Microsoft way is really misguiding... It leds students learn
without understanding or even worse with misunderstanding of the real
way things work or, here, the right way to call things...

Yes, I hate Microsoft products... ;-) Not because they are not usefull,
since  I did use them and I agree they are in some way, but because they
are simply misguiding the (almost) whole World population and it's very
hard to get people back in understanding the reality (how things really
work) after that...

-- 
Jean Christophe "プログフ" ANDRÉ — http://asie-pacifique.auf.org/
Responsable technique régional
Agence universitaire de la Francophonie (AuF) — Bureau Asie-Pacifique (BAP)
Adresse postale : AUF, 21 Lê Thánh Tông, T.T. Hoàn Kiếm, Hà Nội, Việt Nam
Tél. : +84 4 9331108   Fax : +84 4 8247383   Mobile : +84 91 3248747
⎧ Note personnelle : merci d'éviter de m'envoyer des fichiers PowerPoint  ⎫
⎩ ou Word, voir http://www.gnu.org/philosophy/no-word-attachments.fr.html ⎭