Le mercredi 19 avril 2023 à 06:02 +, Werner LEMBERG a écrit :
> No, we can't.
>
> For FreeType, a bounding box ('bbox') of a glyph is set up by the
> minima and maxima of all its contours (omitting single-point
> contours). Computing this is very slow. However, much faster to
> compute is t
>> For LilyPond, the term 'bbox' means something completely different:
>> It is an artificial box suited for LilyPond's needs but *completely
>> decoupled* from the actual glyph dimensions. For a glyph's width,
>> breapth, height, and depth, the OpenType SFNT tables only deliver
>> 'width'.
>>
>>
Hi,
With [!1957](https://gitlab.com/lilypond/lilypond/-/merge_requests/1957) that
will soon become ready, I think it's about time to discuss how we want the “big
picture” user experience and font developer experience to be with respect to
alternative music fonts.
For those who haven't followed
Hi Jean,
> For those who haven't followed the (long) story, this MR basically lets
> LilyPond search for music fonts in the same way as it searches for text
> fonts. It thus makes it possible to make music fonts found with
> ly:font-config-add-font or ly:font-config-add-directory, in contrast t
Le vendredi 21 avril 2023 à 07:03 -0400, Kieren MacMillan a écrit :
> How modular and adaptable will that be? In a robust stylesheet system, there
> would be “inheritance”, “cascading”, etc., rather than the “include and
> overwrite” that happens with [ad-hoc] stylesheets now.
"Inheritance" is
On 21/04/2023 12:03, Kieren MacMillan wrote:
If, next to the .otf font file, a file called stylesheet.ily (or another
bikeshed color) is found, it is read and defines the style parameters. Because
we want to be able to apply it both globally and locally to one
score/bookpart/book, we take it i
> Le 21 avr. 2023 à 14:48, Wols Lists a écrit :
> Just to add to bikeshed colours, please DON'T call it "stylesheet". Call it
> the same name as the font, or something like that.
> If I've got a bunch of custom fonts I use, I just want to dump them in a
> directory and forget about them. If
> Now to the second approach, which I prefer. [...]
Me too. All your suggestions are sound, thanks.
Werner
> Le 21 avr. 2023 à 15:18, Jean Abou Samra a écrit :
>
> The idea is that rather than putting all the .otf file in one directory, you
> make one subdirectory per font. Cf. the bit about recursive searching.
By the way, this is what we’re heading toward with SMuFL anyway. It doesn’t
specify
Here is the current countdown report.
The next countdown will begin on April 24th.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!1953 Remove unused subfont info from LILC font table - Jean Abou Samra
https
10 matches
Mail list logo
