Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

CodeBlock Unicode conversion

(1/4) > >>

cyberkoa:
Hi all,

   I have come across some thread that requesting Unicode version of codeblock.

   Mandrav and Rick are busy with the development of CodeBlock , and Mandrav have said before that there are too many code need to be modified.

  I really would like to see the future codeblock running in unicode , and I believe some of you have the same idea.

I am not sure how to convert all the source code to unicode-compatible but I read from a thread , the basic thing we need to do is use wxT() to convert all the literal string.

I believe everybody can helps in this but we need a standard way of modification so that in the future Mandrav and Rick can easily get our code to use in the newer version.


First of all , we need
 1)The support of the developers of CodeBlock on this proposal.
 2)Write all future code as unicode compatible as possible.

Secondly, we need standard in some aspect.
 1)The standard of the wxWidget compilation , version and option (I use 2.6.1 , same option to compile , except UNICODE=1)
 2)The standard way of marking modified code, this is a must , if not how the developer can know which code we have modified.
    (I suggest to use //UNICODE S  for start block and //UNICODE E for end block)

 

And I hope that Madrav or Rick can help to create a shortcut in CodeBlock , so that we can change it easily .

 For example ,

     wxMessageBox("Testing");

   We highlight "Testing" , press a shortcut key , it will change to wxT("Testing") .

In fact I tried to hack in the code (in autocomplete.cpp) to do this shortcut myself but fail   :oops:

I shall try to start this when I have time in company, at home , I do wxSmith instead.

rickg22:
i believe there are shorter macros for this. Instead of wxT(), use _T(). Additionally, the wxT is only to be used for display purposes. On all other cases, we should use _().

I'm not sure if search-and-replace with regexp's would do it. But we'd have to be careful with escaped quotes. :-/

David Perfors:
I think you can't trust search-and-replace, there are to many ways to make a string that have to be viewed.But if we only have to use _(), I can do some work for you. (after I have tried it first :))

takeshimiya:
_() for translatable text, and _T() for text that must not be translated.

rickg22:
Are you sure about that? I thought it was the opposite :( Do you have the specific url that says so? (so we can finally settle this question)

Navigation

[0] Message Index

[#] Next page