User forums > Nightly builds

The 12.11 RC2 (23 November 2012 build 8598) is out.

<< < (7/24) > >>

kipade:

--- Quote from: MortenMacFly on November 24, 2012, 03:41:11 pm ---
--- Quote from: kipade on November 24, 2012, 01:33:19 pm ---Its was the first try of CodeBlocks under MS Windows with mingw, but, I found it could not load a UTF-8 encoded text file(including *.c and *.cpp source file)

--- End quote ---
Works for me. Can you send a sample file which does not work? And: Is it really UTF-8?

--- End quote ---
Yes, its really UTF-8 encoded, Im sure. So, I have to reinstall old version svn8401, it works for me. Because Im Chinese, I usually use Chinese label in my source files, like wxMessageBox(wxT("消息")); if the file encoded in ANSI, gcc will refuse to compile, so I have to convert it into UTF-8 encoded, however, CB can's display it, so that I can't use it to debugging.
Btw, I also have the same problem under linux.

ollydbg:

--- Quote from: kipade on November 26, 2012, 05:37:01 am --- if the file encoded in ANSI, gcc will refuse to compile, so I have to convert it into UTF-8 encoded....

--- End quote ---
I this case, you can either compile this ansi file with gcc option like
--- Code: ----finput-charset=GBK
--- End code ---
, or convert the file to UTF8 format. So, there are two ways.

carra:
I have installed RC2, and it seems to work pretty fine in general. Points I have noticed are:

(1) The Editor Settings and Environment Settings dialogs seem to appear faster now. Which is a welcome improvement! When you are trying configurations you have to open them many times.

(2) I also have problems with UTF-8 encoded sources. I have attached a header that I actually created and edited with previous versions of C::B, by manually selecting the encoding mode as UTF-8.

I have verified through a hex editor that this file does not have BOM, however it displayed (and compiled) correctly in earlier C::B versions. Current version shows garbage for the non-ansii strings it contains.

[attachment deleted by admin]

MortenMacFly:

--- Quote from: carra on November 26, 2012, 10:09:30 am ---(2) I also have problems with UTF-8 encoded sources. I have attached a header that I actually created and edited with previous versions of C::B, by manually selecting the encoding mode as UTF-8.

--- End quote ---
It has already been fixed - see post somewhere else in the forums.

Randajad:
Have another problem with UTF-8.
Why i need to enable Edit->File encoding->Save BOM by my hands? MSVC and ICC makes invalid result on strings if there is no BOM. I think it's neccessary to add UTF-8(with BOM) to Editor->Other Settings->Encoding.

Also sometimes(can't understand when) CB can't hightlight first line when using UTF-8 with bom.

Navigation

[0] Message Index

[#] Next page

[*] Previous page