search

notofonts / noto-cjk

Noto CJK fonts
http://www.google.com/get/noto/help/cjk
3.02k stars 217 forks source link

Noto Sans 关 & 直 not supported in Figma; Noto Sans SC full-width punctuations issue #285

Closed YananP closed 2 months ago

YananP commented 2 months ago

Hi there! I noticed some font issues when producing PDFs in Figma, and wonder if anyone can offer some advice, or if these are known issues.

Application name and version

Figma Desktop App version 124.3.3

Issue

Noto Sans SC has full-width quotation marks. These occupy excessive space. Noto Sans SC: The "……" punctuation is at the vertical centre. Noto Sans: Some of the characters are displaying incorrectly in Figma. (直 and 关)

To check, I'm using the following sentence:

他们说：“……一直是关键任务。”

Screenshots

image

× Quotation marks are full-width, which is not Simplified Chinese (mainland China) publishing standard. × Ellipsis at the vertical centre.

===========

image

√ Quotation marks are half-width. × Some characters are not supported, displaying Japanese Kanji. (直 and 关)

NightFurySL2001 commented 2 months ago

Noto Sans SC:

× Quotation marks are full-width, which is not Simplified Chinese (mainland China) publishing standard. × Ellipsis at the vertical centre.

Both are correct for Simplified Chinese (mainland China) publishing standard GB/T 15834-2011 《标点符号用法》. image image

Noto Sans:

This font does not contain CJK characters, it is purely only for Latin/Cyrillic/Greek usage. Meaning Chinese characters will fallback to other fonts, probably Noto Sans JP in this case.

YananP commented 2 months ago

Thank you for your reply @NightFurySL2001! It's interesting because even though 5.1.3 states quotation marks should take up a character's space, right under in 5.1.6 & 4.11.2, the quotation marks are using half-width.

NightFurySL2001 commented 2 months ago

The whole document is typesetted with tight spacing (标点挤压), which could be explained with 5.1.11: image However in reality it's just a problem of the typesetting software used to typeset the doucment, and the editor did not manage the punctuations carefully. See https://www.w3.org/TR/clreq/#table_of_bracket_indication_punctuation_marks for a better description.