> I've noticed that utf-8.ly confused the font names.
I've created a merge request.
https://gitlab.com/lilypond/lilypond/-/merge_requests/595
It solves the confusion of Japanese font names in utf-8.ly
but does not solve the `--dgs-load-fonts` warning.
> Note: NotoSansJP-Regular and NotoSansCJKjp-Regular are similar
> but different fonts.
I've noticed that utf-8.ly confused the font names.
It requires the font `Noto Serif JP`.
https://gitlab.com/lilypond/lilypond/-/blob/d6b62def753b268fc5adfbe8443aa477d38395ef/input/regression/utf-8.ly#L30
And
>> ```
>> Layout output to `./1a/lily-d0aeef0b.eps'...
>> fatal error: Font NotoSansCJKjp-Regular cannot be loaded via Ghostscript
>> because it is an OpenType/CFF Collection (OTC) font.
>> ```
> /usr/share/fonts/opentype/noto/NotoSansCJK-Regular.ttc: Noto S
> On Jan 2, 2021, at 14:32, Werner LEMBERG wrote:
>
>> Does this warning indicate something amiss in my build environment?
>>
>> ```
>> Layout output to `./1a/lily-d0aeef0b.eps'...
>> fatal error: Font NotoSansCJKjp-Regular cannot be loaded via Ghos
> Does this warning indicate something amiss in my build environment?
>
> ```
> Layout output to `./1a/lily-d0aeef0b.eps'...
> fatal error: Font NotoSansCJKjp-Regular cannot be loaded via Ghostscript
> because it is an OpenType/CFF Collection (OTC) font.
> ```
What fon
Does this warning indicate something amiss in my build environment?
```
Layout output to `./1a/lily-d0aeef0b.eps'...
fatal error: Font NotoSansCJKjp-Regular cannot be loaded via Ghostscript
because it is an OpenType/CFF Collection (OTC) font.
```
That was from input/regression/utf-8.ly dur
