Testing x64_dbg UNICODE support...

[mrexodia]

Hello everyone,

Recently there have been some questions regarding UNICODE support in x64_dbg. If you're a Chinese/Russian/Vietnamese/Japanese/Whatever user, please try this test version on your computer and report any bugs on http://issues.x64dbg.com or in this topic.

Everything inside x64_dbg should have UNICODE support. Comments/variables/scripts etc are all supported (hopefully).

Notice that your script files should be encoded UTF-8 without BOM.

Notice that this is not an official release. This is a branch called 'utf8_support', if it turns out to be working good, there will be a new release.

Attached the test build.

Greetings,

Mr. eXoDia

dev22g.rar

[xiaotang]

This version supports Chinese, preliminary tests are normal, in the hope that the official the next version of the amendment. But when the search string is still not search, hope to add a new function, press ESC to return to the last.

[Artic]

what you mean with the  search function is not searching? or is it related to the unicode, that the search function is not working?

[mrexodia]

He means that x64dbg will only detect extended ASCII strings, no chinese characters etc. The reason for this is mainly that chinese characters have a variable width even though I specify 'fixed width' in the font settings.

Greetings

[Artic]

ohh so i guess this is next then. UNICODE support looks really timeintensive to implement?

[Aguila]

ohh so i guess this is next then. UNICODE support looks really timeintensive to implement?

not in general, but Mr. eXoDia made a BIG mistake at the beginning: not supporting unicode out of the box right from the beginning

[Artic]

not in general, but Mr. eXoDia made a BIG mistake at the beginning: not supporting unicode out of the box right from the beginning

ok this makes sense. but im so in live with x64dbg. works now better like olly.

[mrexodia]

ohh so i guess this is next then. UNICODE support looks really timeintensive to implement?

Nope, it was actually done in a few hours of work

not in general, but Mr. eXoDia made a BIG mistake at the beginning: not supporting unicode out of the box right from the beginning

Maybe true, although making everything wchar_t doesn't solve anything, it would require conversions to UTF-8 when you save it to disk anyway

Currently everything appears to be working (except searching for Chinese characters, but that's just because I don't want to support that right now). The plugin interface is still the same, except that paths could be UTF-8 instead of ASCII.

Greetings

[wonderzdh]

thank you