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

夹注包: 修改文档字体名称为 Harano Aji Mincho #710

Closed
wants to merge 1 commit into from

Conversation

chianjin
Copy link

l3build 错误,构建文档时提示缺少 HaranoAjiMincho 字体,经查验 HaranoAjiMincho-*.otf 系列字体名称为 Harano Aji Mincho

@muzimuzhi
Copy link
Contributor

构建文档时提示缺少 HaranoAjiMincho 字体,经查验 HaranoAjiMincho-*.otf 系列字体名称为 Harano Aji Mincho

我在本地 macOS 和 Overleaf 的 GNU/Linux 镜像里都能复现,不过不清楚发布 https://github.com/CTeX-org/ctex-kit/releases/tag/jiazhu-beta 时为什么文档能编译出来。@qinglee

@qinglee
Copy link
Member

qinglee commented Apr 20, 2024

应该是之前 haranoaji 包发布时包含有 fontspec 配置文件 HaranoAjiMincho.fontspec

\defaultfontfeatures[HaranoAjiMincho]
  {
    Extension = .otf,
    UprightFont = *-Regular,
    BoldFont = *-Bold,
    FontFace = {l}{\shapedefault}{ *-Light },
    FontFace = {eb}{\shapedefault}{ *-Bold }
  }

使用 HaranoAjiMincho 作为字体名称是没有问题的。这些配置文件在 2023 年初 被删掉了,继续使用 HaranoAjiMincho 这个名称就找不到字体了。

@muzimuzhi
Copy link
Contributor

这些配置文件在 2023 年初 被删掉了,继续使用 HaranoAjiMincho 这个名称就找不到字体了。

这两个文件的源文件依然在 trueroad/HaranoAjiFonts-generator 仓库里,像是打包时出了问题。我报给了 HaranoAjiFontstrueroad/HaranoAjiFonts#11

@muzimuzhi
Copy link
Contributor

muzimuzhi commented Apr 24, 2024

Harano Aji 维护者确认了这是打包时的问题,已在 haranoaji v20231009-2 修复(重新包含了 HaranoAjiMincho.fontspecHaranoAjiGothic.fontspec)。

The fixed package has been uploaded to CTAN.
https://www.ctan.org/ctan-ann/id/mailman.8222.1713852961.3764.ctan-ann@ctan.org

The fontspec files are now back in TeX Live.
https://tug.org/svn/texlive?revision=71051&view=revision

trueroad/HaranoAjiFonts#11 (comment)

@muzimuzhi muzimuzhi closed this Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants