Few russian characters not displayed on C#.net winform on Windows 2008

Question

4.00/5 (1 vote)

See more:

Hi,

My front-end is written in C#.net (winform app) and it has Datagridview and Textboxes to display Russian strings.

On Windows 2003,everything was working fine.

Recently we migrated front-ends from Windows 2003 to Windows 2008 Server, and i found that some of the Russian characters are not displayed on Front-ends.

In textbox if I right click and select "Show Non-Unicode characters" option, and get those missing chars displayed.

However, i don't want that extra clicks. Chars should be displayed directly without and selection from user.

Regards,
Samir.

Posted 20-May-14 4:23am

Member 10831882

Add a Solution

Comments

Sergey Alexandrovich Kryukov 20-May-14 10:43am

I cannot believe that. All Unicode Russian characters are equal and all are supported by all modern fonts on nearly all modern platforms.
—SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2014-05-20T04:44:00

Solution 1

Please see my comments to the question. The problem does not exist, but you could screw up things in many ways. The recipe is very simple: use only Unicode and UTFs for encoding, never anything else.

—SA

Posted 20-May-14 4:44am

Sergey Alexandrovich Kryukov