Community
Participate
Working Groups
Tested on windows 2003 Arabic locale, build 200404131323 1) Unzip the attached CA.zip file into a temp directory 2) Import the source files into a managed C++ project 3) In the main.cpp, remove the comment //NL, and invoke the content assist using the ctrl space keys. The content assist is not invoked, the class name should be NLÚÑÈí
Created attachment 9773 [details] Test project Unzip into a temp directory then import it to the owrkspace
Redirected to the correct parties.
Hello Heba, What compiler do you use to compile this code ? Also could you please attache NLclass.h? It is not part of the attached project. Thanks Hoda
Created attachment 10253 [details] NLclass.h headet file
Hello Hoda, We are using MinGW compiler (Minimalist GUI Windows)
Heba, What version of the compiler are you using? We are using a gnu compiler version 3.2 and it does not compile unicode. Do you have a newer version? Also, your include file does not have the definition of a class with an Arabic name, the one you use in your main function: "NLÚÑÈí" int main(int argc, char **argv) { NLÚÑÈí *n = new NLclass(); NL // n-> // int i = fun // unique } So I need to know where is that defined. Thanks
> Also, your include file does not have the definition of a class with an Arabic > name, the one you use in your main function: > "NLÚÑÈí" Eavesdropping Whether raw Multibyte characters like this is accepted, is left to the implementation of the compiler(reject or accept). GCC does not accept it. So, I'm kind of curious when I see those PR against the debugger. Do you guys have a Compiler/Debugger that can accept this ? or is it just testing for the sake of testing i.e. to be able to say that the CDT is NLS clean ?
Reducing priority until a compiler is identified for UCNs. Also changing title a bit.
This works fine with CDT 4.0.
Returning old defects to pool so I can have an accurate list of what I'm working on.
This bug was assigned and targeted at a now released milestone (or Future or Next that isn't being used by CDT). As that milestone has now passed, the milestone field has been cleared. If this bug has been fixed, please set the milestone to the version it was fixed in and mark the bug as resolved.
