Re: Header fonts

[David Kastrup]

David Kastrup <address@hidden> writes:

> Timothy Lanfear <address@hidden> writes:
>
>> Fonts for the header fields are not set correctly for the second and
>> subsequent books in a file.
>>
>> Pre-built version 2.19.45, 64-bit Linux.
>>
>> \version "2.19.45"
>>
>> \header { title = "Title" composer = "Composer" }
>>
>> \book { \score { a'1 } }
>> \book { \score { a'1 } }
>
> Interesting.
>
> address@hidden:/tmp$ ls -l gaga*.pdf
> -rw-rw-r-- 1 dak dak 15033 Jul 10 11:31 gaga-1.pdf
> -rw-rw-r-- 1 dak dak 41971 Jul 10 11:31 gaga.pdf
>
> address@hidden:/tmp$ pdffonts gaga.pdf
> name type encoding emb sub uni object ID
> ------------------------------------ -----------------
> ---------------- --- --- --- ---------
> LQFAMB+Emmentaler-20 Type 1C Custom yes yes no 12 0
> IDXJFX+TeXGyreSchola-Bold Type 1C WinAnsi yes yes no 8 0
> ENLKFF+TeXGyreSchola-Regular Type 1C Custom yes yes no 10 0
>
> address@hidden:/tmp$ pdffonts gaga-1.pdf
> name type encoding emb sub uni object ID
> ------------------------------------ -----------------
> ---------------- --- --- --- ---------
> LQFAMB+Emmentaler-20 Type 1C Custom yes yes no 12 0
> RSRUFC+TeXGyreSchola-Bold Type 1C WinAnsi yes yes no 8 0
> YMRISQ+TeXGyreSchola-Regular Type 1C Custom yes yes no 10 0
>
>
> So it's the same fonts that claim to be embedded but the second PDF file
> still has only 1/4 of the size.  And, well, indeed the titles look less
> than convincing, obviously using some emergency substitute.
>
> This does not happen with a LilyPond executable claiming to be 2.19.44
> (so it is from some compilation between 2.19.43 and 2.19.44) so it is a
> fairly recent problem.  Should not be exercising any of the new \header
> code from me I think, so it's more likely to be a newly introduced bug
> in font handling.
>
> Will bisect.

Well,

eda66de049d33031a3230dfbf5735399bf2c1d60 is the first bad commit
commit eda66de049d33031a3230dfbf5735399bf2c1d60
Author: Masamichi Hosoda <address@hidden>
Date:   Tue Jun 28 18:44:49 2016 +0900

    Issue 4909/2: Add checking conflicts between CFF flavored fonts
    
    This commit adds checking conflicts between fonts
    which have same name in 'CFF' table
    but different name in 'name' table.


But then this was sort-of apparent from the discussion elsewhere.  Too
bad it went mostly under the radar before 2.19.45 got released.

-- 
David Kastrup