Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | > Both ucs2 and ucs4 use a fixed number of bytes for one character
| > (2
| > | > and 4, respectively, surprise, surprise!). The problem is a
| > | > variable-byte encoding such as utf8.
| > | | Yes I understood that far, sorry for "quiproquo". IMHO, the
| > only code
| > | that should refer to the utf8 encoding is a code that handles writing
| > | or reading a file.
| > Or communicationg with other libs api's.
|
| Which one?
ucs-2 with qt.
so no utf8 here.
utf-8/ucs-2 with pango.
So utf8 is not necessary there also as pango deals perfectly with ucs2
(and 4?)
What aspell can use I have no
idea about. (it can use ucs-2 and ucs-4, but requires them cast to
char*)
Same here...
As for gettext as pointed out by JMarc, this is not like we have to
manipulate the translated string inside the code, are do we?
Abdel.
