1738230 - Full width bracket (U+FF08 and U+FF09) glyph is wrong when vertical writing and using SourceHanSerif.ttc

Status: RESOLVED INVALID

(Core :: Layout, defect)

Description

[butameron]

Attachment: Screen shots

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.54 Safari/537.36

Steps to reproduce:

1. Install SourceHanSerif.ttc to Windows 10
   SourceHanSerif.ttc
   https://github.com/adobe-fonts/source-han-serif/releases/tag/1.001R

2. Open the following html with Firefox

<!DOCTYPE html>
<html>
<head>
    <meta charset="utf-8" />
    <style>
        html {
            font-family: "源ノ明朝", "Source Han Serif";
        }
        body {
            -ms-writing-mode: tb-rl;
            writing-mode: vertical-rl;
        }
    </style>
</head>
<body>
    <!--Test Case 1: NG (Full width alphabet + Full width bracket)-->
    <div>
        Ｆ（Ｆ）
    </div>
    <!--Test Case 2: OK (Full width hiragana + Full width bracket)-->
    <div>
        あ（あ）
    </div>
    <!--Test Case 3: NG (Half width Alphabet + Full width bracket) -->
    <div>
        A（A）
    </div>
</body>
</html>

Tested on Windows 10 Pro 64bit Japanese
Version 21H1 (OS build 19043.1288)

Actual results:

Test Case 1. Full width alphabet + Full width bracket
Glyph for horizontal writing (upright glyph) is rendered. -> NG

Test Case 2. Full width hiragana + Full width bracket
Glyph for vertical writing (rotated glyph) is rendered. -> OK

Test Case 3. Full width hiragana + Full width bracket
Glyph for horizontal writing (upright glyph) is rendered. -> NG

Expected results:

Test Case 1. Full width alphabet + Full width bracket
Glyph for vertical writing (rotated glyph) is rendered.

Test Case 2. Full width hiragana + Full width bracket
Glyph for vertical writing (rotated glyph) is rendered.

Test Case 3. Full width hiragana + Full width bracket
Glyph for vertical writing (rotated glyph) is rendered.

Comment 1

[BugBot [:suhaib / :marco]]

The Bugbug bot thinks this bug should belong to the 'Core::Layout' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[butameron]

Test Case 3. Full width hiragana + Full width bracket
"Test Case 3. Half width alphabet + Full width bracket" is right.

Comment 3

[Jonathan Kew [:jfkthame]]

I think this may be a bug in the OpenType features present in the old 1.001 version of the font. If you try resources from the version 2.000 release, such as the SourceHanSerif-VF.ttf font from here, does it work as expected?

Comment 4

[butameron]

Attachment: test.zip

Thank you.
Changing font-familiy to "Source Han Serif VF" works fine.

Unfortunately, "Source Han Serif VF" causes another problem.
When print via built-in PDF printer "PDF に保存" (in English, "Print To PDF"?) , it seems that the printer couldn't embed font.
PDF file saved by Firefox built-in PDF printer doesn't show any "Source Han Serif VF" character in Adobe Acrobat.

Should I file new issue?

Comment 5

[butameron]

I tried another type of font.
Static Super OTC of Source Han Serif 2.000R works fine for displaying and printing.
https://github.com/adobe-fonts/source-han-serif/releases/download/2.000R/SourceHanSerif.ttc.zip

Comment 6

[Jonathan Kew [:jfkthame]]

(In reply to butameron from comment #4)

Created attachment 9248294 [details]
test.zip

Thank you.
Changing font-familiy to "Source Han Serif VF" works fine.

Unfortunately, "Source Han Serif VF" causes another problem.
When print via built-in PDF printer "PDF に保存" (in English, "Print To PDF"?) , it seems that the printer couldn't embed font.
PDF file saved by Firefox built-in PDF printer doesn't show any "Source Han Serif VF" character in Adobe Acrobat.

Should I file new issue?

Yes, that sounds worth investigating, but it's a separate issue so filing a new report would be best -- otherwise it gets really confusing to keep track of things. Probably filing in the Printing::Output component would be a good start.

Closing this bug, as the vertical-mode glyph problem here was a font issue rather than Firefox bug.