Developer forums (C::B DEVELOPMENT STRICTLY!) > Contributions to C::B

Code::Blocks' translation

<< < (7/57) > >>

thomas:

--- Quote from: heromyth on February 03, 2006, 02:32:36 am ---After CB uses default.conf as its configure file or is built with UNICODE mode, the internationalize of CB seems more difficult than before.
I don't want to say much more lest so many people be annoyed. :P
I'll try to solve them.
--- End quote ---
Please do say more. What exactly is making it more complicated?

heromyth:

--- Quote from: thomas on February 03, 2006, 10:02:53 am ---
--- Quote from: heromyth on February 03, 2006, 02:32:36 am ---After CB uses default.conf as its configure file or is built with UNICODE mode, the internationalize of CB seems more difficult than before.
I don't want to say much more lest so many people be annoyed. :P
I'll try to solve them.
--- End quote ---
Please do say more. What exactly is making it more complicated?

--- End quote ---

I build CB with unicode mode, but my translation can't works any more like before. Maybe I don't find the right way. So I build CB with ansi mode. Now my translation works. However another problem produced. That's some phrases translated by me have been written into the file default.conf. When I first launch CB and close it, an exception will be raised. It's from sdk\configuremanager.cpp:487 and it says the node and the namespace are "an_dlg". That's because I have translated this phrase "Layout changed!"  in src\main.cpp:917. Then I choice not to translated it and launch CB again (Notice, some Chinese characters have been existed in the file default.conf). A alert window shows these:

--- Code: ---TinyXML error:
Error reading end tag.
--- End code ---

Good news
After I change the defult.conf's code page to utf-8, the second problem seems disappeared and the first one still be there.  Perhaps it is because CB is working with ansi mode, so the default.conf's code page is ansi.  However there produces another problem that all the Chinese characters in default.conf can't be shown correctly.

thomas:
This has nothing to do with the fact that the config is stored in xml, but you have found an actual bug in AnnoyingDialog there. :)

The reason why this fails is that the dialog's caption is used
a) as the caption
b) as the title in the check list box where you can re-enable disabled dialogs
c) as a key in the config file (this works fine in English but is deadly with Chinese chars)

Although the problem is easily identified, a solution is not quite so easy. Well, the solution *is* easy, but it will break the exisiting configuration files for everybody...

Let me think about what to do best.

heromyth:
It's really difficult in handling the non-English characters in XML files. So I have an idea submitting this bug to TinyXML.  :P

takeshimiya:

--- Quote from: heromyth on February 05, 2006, 03:15:10 am ---It's really difficult in handling the non-English characters in XML files. So I have an idea submitting this bug to TinyXML.  :P

--- End quote ---
Why you say that? tinyXML supports Unicode UTF-8 encoded strings.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version