Hello,
As shown in the example, for text 3, I have to use some online translator to convert the unicode to Chinese each time.
It brings a lot of troubles when writting some string operation codes. In MS version C#/VB.Net, it does not have this problem.
Regards,
Xiaoguang
Logged as bugs://E25593.
Agreed, at least optional, it should show those as the final Unicode characters (where display-able), not as escapoed character literals
bugs://E25593 was closed as fixed.
Fixed, with a new option in Preferences (on by default): โShow Non-ASCII Characters in Debug Evaluationsโ
fantasic news, thanks!!
Hello,
Looks like it only works in Water IDE?
Code as below:
namespace OxygeneDotnet;
interface
uses
System.Linq;
type
Program = class
public
class method Main(args: array of String): Int32;
private
end;
implementation
class method Program.Main(args: array of String): Int32;
begin
var text:String:=โๆๆฅ่ช็ซๆโ; // Which means I came from Mars
text:=text+".";
end;
end.
By the way, Visual Studio version is 2022 17.1.0 Preview 2.0 community
I believe the option is not exposed in Visual Studio yet, no. iโll log.
bugs://E25593 was reopened.
Yes, I guess so, canโt find this option in VS.
BTW, water is such a good IDE. Now I almost only use VS to:
iโm so happy to hear that! much appreciated 
.
bugs://E25593 was closed as fixed.
Hi, installed latest build 2707, looks like the problem is fixed for .net for both water/VS.
However, for Java, still has the problem for the 2 IDEs:
Could you have a look? thanks.
So Java Unicode is broken both in the Water console and VS evals? Is the eval bad in Water, too?
Logged as bugs://E25629.
Sorry, in water, the locals and watches are working for unicode, but the outputs are not (as shown in figure 2 bottom line3:)
In VS,the locals and watches are not working for unicode
thanx for clarifying.
Hi mh,
With latest stable build 2709, I confirmed that the watch are now working for unicode for both Water and Visual studio.
But the output still not showing correctly (as shown in the bottom, line 3).
Could you take a look? Thanks.
Thanx. the issue is still marked โopenโ, so i assume thatโs as expected and the second fix is still in the works, as these were two unrelated problems really.
