Jump to content

4.8.0.13Korean display exception


SmileFlower
 Share

Recommended Posts

SmileFlower
12 minutes ago, Luke said:

Hi there, what do you mean exactly? Can you please show an example? Thanks.

image.png.4f9d4dc9ec89719c5d567a83ce1096df.png

 

4.8.0.13 Korean subtitles cannot be displayed

Edited by SmileFlower
Link to comment
Share on other sites

3 minutes ago, SmileFlower said:

 

GoNotoCurrent.ttf  Korean can be displayed, but the style is wrong

 

What exactly do you mean by style is wrong?

Link to comment
Share on other sites

SmileFlower

I reorganize and describe the problem

 

This is 4.7.8.0. The Korean display on the web client is normal

1.thumb.png.68b4df71faf5ce6c73b15be105e3758f.png

 

This is 4.8.0.13 webpage client Korean display exception

2.thumb.png.d813e8a9df1727c310b8903ea16d1f70.png

 

 

This is Android client 3.2.79 Korean display is normal

3.png.4bb6b219fd1d4131136db99d8b20f42b.png

 

 

This is Android client 3.2.82 Korean display exception

4.png.3248c81377be1a81dfa36e7cf3a301e2.png

 

 

Sample subtitle file:

subtitle.ass

Link to comment
Share on other sites

SmileFlower
1 hour ago, Luke said:

Do you have other subtitles where it renders the text correctly?

The samples I sent did not add any special effects, so did the plain text, including SRT

Link to comment
Share on other sites

18 hours ago, SmileFlower said:

The samples I sent did not add any special effects, so did the plain text, including SRT

Do you have other subtitles where it renders the text correctly?

Link to comment
Share on other sites

SmileFlower
44 minutes ago, Luke said:

Do you have other subtitles where it renders the text correctly?

As long as it is Korean, the display is not normal. You can try the sample subtitles I sent

Link to comment
Share on other sites

Happy2Play

@Lukethis has to do with the change from subfont.woff2 in 4.7 to GoNotoCurrent.woff2 in 4.8.  At least in web client.

As copying subfont to 4.8 and editing the plugin.js corrects the subs issue.

image.png.8dda882532628da06eb9672acc1b9463.png

subfont.woff2 in 4.7

image.png.919591db794daa3c3c8372214b8b73b6.png

GoNotoCurrent.woff2 in 4.8

image.png.2a9c574a1d99133f2ff667da4f20fe74.png

Link to comment
Share on other sites

Yea but we can't go back to the previous version of the font because it has other issues with other languages, so we have to figure out a plan going forward.

Link to comment
Share on other sites

SmileFlower
2 hours ago, Luke said:

Yea but we can't go back to the previous version of the font because it has other issues with other languages, so we have to figure out a plan going forward.

The problem may be solved by replacing the Korean character set of the old font with the new one. It is necessary to modify woff2 and ttf

Link to comment
Share on other sites

  • 4 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...