Hi all, I think Kazuki says:
It is true that **most of** the collection fonts available in the world have a subfont whose postscript name is exactly same as its fontname, however, it is NOT true that **all of** the collection fonts do. And he is right: some of the examples are Apple's new CJK fonts and what Yusuke has sent to us. And the patch Kazuki has sent works fine, I think. ----- Hironobu Yamashita 2015/10/09 13:04、Yusuke Terada <[email protected]> のメッセージ: > I've made a font for testing on Kazuki's advice using AFDKO. > > You can download it from here: > https://dl.dropboxusercontent.com/u/5807100/SourceHanSans-Medium-Reduced.ttc > > If you compile the attached luaotfload_test.tex with plain-LuaTeX 0.81.0, you > will get this error: > <./SourceHanSans-Medium-Reduced.ttc(SourceHanSans-Medium:-1)Invalid TTC index > number > > After applying the patch Kazuki submitted yesterday to fontloader, this > source can be compiled correctly. > > Sincerely, > > Yusuke Terada > > <luaotfload_test.tex> > > >> 2015/10/09 11:20、Kazuki Maeda <[email protected]> のメール： >> >> SourceHanSans-Medium.ttc has the following metadata: >> >> ... >> ["fontname"]="SourceHanSans-Medium", >> ... >> >> and four subfonts: >> >> (0): >> ["postscriptname"]="SourceHanSans-Medium", >> (1): >> ["postscriptname"]="SourceHanSansK-Medium", >> (2): >> ["postscriptname"]="SourceHanSansSC-Medium", >> (3): >> ["postscriptname"]="SourceHanSansTC-Medium", >> >> In this case, ("postscriptname" of the subfont 0) == ("fontname" of >> SourceHanSans-Medium.ttc). >> Therefore, "Invalid TTC index number" error does not occur. >> If you delete subfont 0 from the ttc, you may get the error. >> >> >> Best regards >> Kazuki Maeda >
