IBM Plex Sans JP AJ1-6 extension quality issues [v3.0 cont]

未关闭
#666 3 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
冷清
领域
design

调研方向

检查 issue 中的字形示例和 Unicode/CID 引用,将受影响的 IBM Plex Sans JP 扩展字形与原始 JP 设计和 AJ1-6 要求进行比较。issue 描述了多处不一致,并指出该列表并不完整;完成这项工作需要修正已报告的字形构造,并完成更广泛的质量审查。

由索引模型根据 Issue 内容生成。

描述

Incorrect 人 top copied from the low-quality SC for 瘹 (U+7639, CID+22032), 壡 (U+58E1, CID+21370) and 朇 (U+6707, CID+21731).
Image

Misaligned top for 礠 (U+7920, CID+22101) in EL weight
Image

Misaligned component for 珝 (U+733D, CID+21986) in EL and H weight
Image

incorrect component according to AJ1-6 for 寏 (U+5BCF, CID+21445):
Image


Additional inconsistencies have been introduced too:

Inconsistent 瓜 where middle vertical stroke of 窳瓞 does not touch the top, and 蓏寙 is different with 窳:
Image

臣 on top should not have leg:
Image

山 on left should not have right leg:
Image
(Funnily, this is probably done with smart component and adding back the right leg. This should not have happened at all when the original JP just doesn't require it.)
Image

Same with 爿 with no protrusion:
Image

Same with 丂 with no protrusion:
Image
Image

Same with 女 with no protrusion:
Image
Image

The above list is not exhaustive.

Given the worse quality and consistency of the new Adobe-Japan1-6 extension (with the previous few issues), I urge IBM Plex team to re-verify thoroughly the works done by the team/company/individuals that expands IBM Plex Sans JP as they have not shown any professionalism when dealing with the original JP design, discarding any original design intent, does not follow any consistent design requirements, does not do any quality assurance checks, and introduced unnecessary complexity by re-using the lower quality glyphs from SC version.

主要语言
CSS
星标
11.8k
派生
626
平均合并
1 天 9 小时
30 天内合并 PR
2

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

IBM/plex 的其他 Issue

查看 IBM/plex 的全部 Issue

相似的 Issue

更多 Design Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。