New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Japanese kanji are not Japanese #1909
Comments
Hi |
I think in previous Desktop released version it still worked. Previous or 2 before 3.69.2. |
It looks like the Windows desktop client renders the characters using the "Microsoft JhengHei UI", whereas Chrome, for example, used SimSun on my test machine. This explains why the problem is Windows specific. I don't know if this font is doing it the right way for some other context, for example, maybe that would be the correct thing to display for traditional Chinese text? See the Unicode Han Unification. |
Is this automatic process or can you specify which font to use? Windows have by default installed MS Gothic font for Japanese. Or would be easier to implement font selection in Desktop client? The same way as Outlook or Thunderbird have font selection option. |
related: electron/electron#18829 |
adds an "override default font" option to the desktop settings viewer which doesn't show up when there are no overrides configured for the current platform (currently, contains SimHei's latin and chinese name on windows, which is installed by default). Uses a fixed list of fonts because getting a list of installed fonts cross-platform requires a native module like font-manager or parsing of platform-dependent command output (which may be huge) This is not applied automatically because it replaces the default font of the application and we can't rely on locale to detect which font would be correct for the user. changing the font list in main-styles.js directly would also work, but that's not very extensible should this problem occur with other language/locale/platform combinations. It would also require to get the user's choice from the main thread somehow.
adds an "override default font" option to the desktop settings viewer which doesn't show up when there are no overrides configured for the current platform (currently, contains SimHei's latin and chinese name on windows, which is installed by default). Uses a fixed list of fonts because getting a list of installed fonts cross-platform requires a native module like font-manager or parsing of platform-dependent command output (which may be huge) This is not applied automatically because it replaces the default font of the application and we can't rely on locale to detect which font would be correct for the user. changing the font list in main-styles.js directly would also work, but that's not very extensible should this problem occur with other language/locale/platform combinations. It would also require to get the user's choice from the main thread somehow.
adds an "override default font" option to the desktop settings viewer which doesn't show up when there are no overrides configured for the current platform (currently, contains SimHei's latin and chinese name on windows, which is installed by default). Uses a fixed list of fonts because getting a list of installed fonts cross-platform requires a native module like font-manager or parsing of platform-dependent command output (which may be huge) This is not applied automatically because it replaces the default font of the application and we can't rely on locale to detect which font would be correct for the user. changing the font list in main-styles.js directly would also work, but that's not very extensible should this problem occur with other language/locale/platform combinations. It would also require to get the user's choice from the main thread somehow.
adds a function getFonts() to main-styles.js that returns the font-family string for the body style. will add additional fonts depending on the platform and used language. AppearanceSettingsViewer will now also cause a regeneration of the style tags and a change of language on the native side when the language is changed by the user.
adds a function getFonts() to main-styles.js that returns the font-family string for the body style. will add additional fonts depending on the platform and used language. AppearanceSettingsViewer will now also cause a regeneration of the style tags and a change of language on the native side when the language is changed by the user.
adds a function getFonts() to main-styles.js that returns the font-family string for the body style. will add additional fonts depending on the platform and used language. AppearanceSettingsViewer will now also cause a regeneration of the style tags and a change of language on the native side when the language is changed by the user.
adds a function getFonts() to main-styles.js that returns the font-family string for the body style. will add additional fonts depending on the platform and used language. AppearanceSettingsViewer will now also cause a regeneration of the style tags and a change of language on the native side when the language is changed by the user.
adds a function getFonts() to main-styles.js that returns the font-family string for the body style. will add additional fonts depending on the platform and used language. AppearanceSettingsViewer will now also cause a regeneration of the style tags and a change of language on the native side when the language is changed by the user.
I will request features on forum or via support.
Describe the bug
When writing in Japanese, kanji are changed. Also comma after kanji is placed in weird position. In previous versions this was working. In mobile and web application this is shown correctly.
To Reproduce
Steps to reproduce the behaviour:
Expected behavior
If you save draft and open with web application, it will be displayed correctly.
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: