none
The created/painted characters cannot be displayed correctly in the C# file RRS feed

  • Question

  • 1)Prepare an environment where Japanese character are shown correctly.
    2)Start EUDCEDIT.exe from Command Prompt (There is EUDCEDIT.exe in Windows 10)
    3)Paint a character for CODE F040 of EUDC files 
    4)Save the EUDC files.
    5)Link it to all Fonts.
    6)Open IME pad.
    7)Jump to EUDC area of Shift-JIS code and you find EUDC character for 0xF040.
    8)Create a C# console application
    9) In the program.cs file, inserted the painted character, you will find just square displayed. 
    Is it a bug for the C# editor in Visual Studio?
    Wednesday, January 3, 2018 3:17 AM

All replies

  • Please report issues with VS using the Send Feedback feature in VS proper (top right corner).

    Michael Taylor http://www.michaeltaylorp3.net

    Wednesday, January 3, 2018 2:41 PM
    Moderator
  • Hello Lyle Xu,

    >>In the program.cs file, inserted the painted character, you will find just square displayed. Is it a bug for the C# editor in Visual Studio?

    It seems that the VS can't recognize the character although you link it to all fonts. and you could try to open the program.cs file with notepad tools. If you want to input the character I strongly recommend you use unicode value for the character instead of copy the character directly.

    string str = "\uF040";

    If you want to output the value to the console. the code should be like this.

                string str = "\uF040";
    
                Console.OutputEncoding = Encoding.Unicode;
    
                Console.WriteLine(str);

    Best regards,

    Neil Hu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Sunday, January 7, 2018 11:15 AM
    Moderator
  • It's actually a historical issue for Console Unicode support documented here (and a number of other articles on this blog.)

    Michael Kaplan was a MSFT employee who was an expert in internationalization issue.

    Monday, January 8, 2018 2:02 AM
    Answerer
  • Hello Lyle,

    Is there any update or any other assistance I could provide? You could mark the helpful reply as answer if the issue has been solved. And if you have any concerns, please do not hesitate to let us know.

    Thank you for your understanding and cooperation!

    Best regards,

    Neil Hu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Sunday, January 28, 2018 12:25 PM
    Moderator