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

Font can't be read because of non-Unicode charmap #37

Closed
Denoder opened this issue Dec 12, 2018 · 3 comments
Closed

Font can't be read because of non-Unicode charmap #37

Denoder opened this issue Dec 12, 2018 · 3 comments

Comments

@Denoder
Copy link
Contributor

Denoder commented Dec 12, 2018

there seems to be a small issue regarding the specific font names not being checked.

Lets say for instance i use: EPSON 太丸ゴシック体B this wont work because of .
If i remove it then it'll work, im not sure what other characters are affected but that's the first instance i found.

@Denoder
Copy link
Contributor Author

Denoder commented Jan 24, 2020

Here is an exampel font that isn't being read:
F5AJJHR8.zip

Name: Fj平成極太丸ゴシック体

@TheOneric
Copy link
Member

Merged into #63 since it has more samples.

@TheOneric TheOneric changed the title Font isnt registered because of the name Font can't be read because of non-Unicode charmap Oct 17, 2021
@TheOneric
Copy link
Member

Correction: This has not directly something do to with the name but the font's encoding. It uses “SIJS” as encoding (which affects not only the name, which is read as FjïΩê¨ã…ëæä€ÉSÉVÉbÉNëà but also the charmap making it unusable). All modern fonts use Unicode and that's the only font encoding libass currently supports. See: libass/libass#531
You can recode the font with eg fontforge (remember to also sanitise the name) or use a native Unicode font.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants