User forums > Using Code::Blocks

UTF-8 handling by wxSmith

<< < (2/2)

BlueHazzard:
installing a nightly isn't that difficult/space consuming... try it and you are sure...
NOTE: you don't install a nightly, you simply download it, unzip it and run it. You even can copy it over the release installation. BUT you need also the right dlls from the nightly forum post.

Modifying some project files by hand is no good idea. And also i don't think that this feature was implemented before the added option in the dialog, so yes i think that a nightly is behaving differently...

greetings

paul_c_weiss:
Thank you,

While the issue is real, I now think that I am coping with another problem, since minor modifications on my wxSmith file
cause execution errrors which cannot be corrected. What I mean is that changing a dimension (using the GUI)
induces an execution error, and then correcting back the dimension to its former value does not suppress
the error, after project re-building....

This is a totally different issue which I must now understand.
I shall later come back to the UTF-8 issue

Thanks for your help!

ivan braga:
I know the topic is old, but the problem has not yet been resolved.

Unfortunately

--- Quote from: BlueHazzard on April 10, 2016, 11:40:19 pm ---maybe this can help:
"Settings->Editor->wxSmith Settings->Other Settings->Non I18N Strings"

--- End quote ---
does not work.



But editing directly as suggested

--- Quote from: paul_c_weiss on April 13, 2016, 10:53:02 am ---<wxsmith version="1">
            <gui name="wxWidgets" src="SudokuApp.cpp" main="SudokuFrame" init_handlers="necessary" language="CPP" />
            <resources>
               <wxFrame wxs="wxsmith/Sudokuframe.wxs" src="SudokuMain.cpp" hdr="SudokuMain.h" fwddecl="0" i18n="1" name="SudokuFrame" language="CPP" />
            </resources>
         </wxsmith>

Obviously by replacing i18n="1"by i18n="0"

--- End quote ---

it works perfectly.

Thank you, your tip helped me, it was already with your head hot.

Miguel Gimenez:
Use of i18N in wxSmith is strange:
  - The value in Settings -> Editor -> wxSmith -> Use i18N for strings looks like a global enable for translation.
  - Each wxs file has its own setting (chosen when creating the resource in the Advanced options tab) and is not modifiable without editing the CBP file.

Both settings are ANDed in wxscodinglang.cpp:185, if the result is true then the string is surrounded with _(), if not with the value selected in Settings -> Non i18N strings.

This behaviour is unexpected and should be clarified, probably Use i18N for strings should be changed to Enable i18N globally or similar wording.

Navigation

[0] Message Index

[*] Previous page