Notepad++ can't display Chinese Characters after updating to Windows 10 18363.592 - character-encoding

I just updated my windows 10 from 1909 18363.535 to 1909 18363.592. Notepad++ used to work properly and was able to display Chinese Characters, but after this update
NONE of the Chinese character can be displayed. Initially, I thought it was a Notepad++ problem, as it happened on my other laptop, so I copied the same file to my 2nd laptop which had the 18363.535 version, same version of Notepad++, the file was able to display just fine.
After the update, neither can display Chinese characters. I have even tried to change the file format, from UTF8 to ASCII and checked some character encoding. None worked.
All Chinese are now squares. You can even input the new ones.
My locale was set correctly to Chinese on both computers using windows 10 X64 English (UK) version.
Anyone had the same/similar problems????

Did a long seach, as it turns out, it's a font problem.
Windows 10's lastest update somehow messed up the font.

Related

Spring4D TObjectDataSet Arabic charactes in win 10

I am using Sprinfg4D TObjectDataSet in a project, all is perfect in windows 7, but wheen i move the application to windows 10 , the fields with arabic characters seem not woking correctly, in SqlSevrer DB all is perfect except the UI, specialy the arabic characters showed like ???????, even in DBGrid, even in DevExpress Controls.
SQLServer

NSIS Installer does not show Russian text

I am trying to create an installer that support Russian language. I spent many times, but still did not fix the problem.
I have Windows 10 English version with installed Russian language pack. Russian language is set to default.
Here are my steps:
Install NSIS 3.01. (The same was with 2.46).
Build Examples\languages.nsi from NSIS. I use Windows XP as build PC.
When I run languages.exe on Window 10 and select Russian language I see the following:
The text is not in Russian.
Well it is probably in Russian, but in wrong font. Otherwise all text consist of question character (?).
With "Unicode true", the text is in Russian. But I would not like to use it and to understand the issue.
Regards,
Valery.
Unless you are still supporting Windows 95/98/ME there is no reason to not build a Unicode installer.
You must change the Language for non-Unicode programs to make non-Unicode version display the correct characters.

WiX localization garbled words under installer properties tab

I'm trying to do localization in WiX installer. How can I fix the garbled words shown below in the installer properties? The language that I defined is Japanese.
Windows Installer doesn't officially support codepage 65001 for UTF-8 -- mostly because of UI problems like this. Try using codepage 932 for ja-JP strings. Also, make sure you're setting the Package/#SummaryCodepage attribute (the .wxl file's code page sets Product/#Codepage).

Firemonkey Unicode support for XP

Am developing a Delphi firemonkey desktop application with XE5.
I use Unicode characters to localize the application (Asian language call Sinhala).
Everything is perfect with windows 7 (We haven't tested it with Vista). But when we test it with windows XP, it display every character as a box (except in title bar).
What is the problem? Is delphi firemonkey support unicode in XP?
Is there any way to get it display correctly on XP?
(This happens only with firemonkey, everything is OK with VCL. Since am going to make it support for MAC, I have to use firemonkey.)
AFAIK FireMonkey does not implement the so-called Font fall-back mechanism. It does not use the Uniscribe API.
I suspect the font you are using (e.g. Tahoma) does not contain the needed characters in XP - whereas the TTF file included with Seven/Vista does contain them. So FireMonkey is not able to display the text as expected in XP.
Change the font to one having all needed glyphs. You may have "Arial Unicode MS" available, even on XP, if you have MSOffice installed.
By default, the VCL renderer uses the ExtTextOut GDI API which does implement font fall-back, so it automagically searches the installed fonts for the missing glyphs.
To properly use/display Unicode the OS has to support unicode strings and you have to have fonts installed that can display the Unicode characters. Since their are 65000+ characters not all font manufacturers include every Unicode character.
I think the FireMonkey app uses a font that does not contain Sinhala characters. Play with the font used by the app.
If you need a Sinhala font, the wonderful Alan Wood’s Unicode Resources has a section Large, multi-script Unicode fonts for Windows computers. The South Asian font page names several fonts you can try.
Alternatively, Googing "sinhala unicode font" will also give you plenty of suggestions.
I have checked all these suggestions - but there is no useful turnout of my problem. I have found out the following facts.
Changing the font to Arial MS Unicode or replacing Tahoma with a TTF file from Windows 7 doesn’t work.
Changing the font to “Iskole Pota”, a font which support Sinhala Unicode symbols , solved the problem for TEdit component.
All the components which are descendents of TTextControl don’t work with “Iskole Potha” solution.
I have further noticed that changing the font to something like “Wingdings” for TTextControl descendants don’t show appropriate symbols either. They still show English.

Delphi can't recognize Russian characters

I have an English version of the Windows XP operating system installed on my computer. If I try to use the Russian input language, for example, to give a form a caption that's written in Russian, the only thing I see is those unintelligible symbols that you often see when there is a problem with proper character encoding. Is there a way to make Delphi recognize Russian characters?
Any suggestions will be highly appreciated.
You can change default code-page used for programs that do not provide locale info (Control Panel > Regional setting > Advanced) to your locale (Russian).
As for SQL that is a separate question probably solved by SQL DB settings.
P.S. I would suggest you to move to Unicode version of Delphi (XE) and SQL too.

Resources