Skip to content
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

[Bug]Noto Serif Hentaigana font is not reflected in Microsoft Office. #8

Open
jn-njjp opened this issue Oct 30, 2024 · 0 comments
Open

Comments

@jn-njjp
Copy link

jn-njjp commented Oct 30, 2024

Font in question
googlefonts
variable
NotoSerifHentaigana[wght].ttf

Source: https://github.com/notofonts/hentaigana/releases/tag/NotoSerifHentaigana-v1.000
Date: 2024/10/30

Font version
Verson 1.000

OS name and version
Windows 11 Home 23H2

Application name and version
Microsoft Word/Excel/PowerPoint version 2409

Problem
Even if you select a variant kana font in Microsoft Office, it is not reflected.

  1. Reproduction procedure
    Copy and paste variant kana from Wikipedia, etc. into Word.
    Select the copied and pasted kana and change it to the variant kana font.

  2. Observed result
    Cannot be changed. The kana you tried to change remains in the original font.

  3. Expected results
    The font changes to the variant kana font without any problems.

  4. Additional information
    Noto Sans/Serif Japanese is also installed. This works without any problems.

Character data
𛀁 𛀙 𛀆, etc.

Currently, when there is a text that contains both variant kana and normal kana, if you specify Noto Serif Japanese as the overall font, the variant kana will be garbled. Even if this problem of not being able to specify it in the first place is solved, the problem of it being difficult to use at the same time as Serif Japanese will remain. For ease of use, I would like you to consider completely integrating it into Serif Japanese.
image

@jn-njjp jn-njjp changed the title Noto Serif Hentaigana font is not reflected in Microsoft Office. [Bug]Noto Serif Hentaigana font is not reflected in Microsoft Office. Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant