[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Can we refactor output-svg.scm to avoid regexp?
From: |
Étienne Beaulé |
Subject: |
Re: Can we refactor output-svg.scm to avoid regexp? |
Date: |
Wed, 28 Oct 2020 22:38:53 -0400 |
Svg-woff is not only broken with that old bug, but also that SVG fonts are
deprecated. The hope is that the work on SMUFL done this summer could be used
in the SVG backend, and with that, embedding musical symbols directly could be
avoided to reduce regex use.
Étienne
> Le 28 oct. 2020 à 22:27, K.L. <k.l.lambda@gmail.com> a écrit :
>
> Hello guys.
>
> I ran a profiling for SVG backend engraving, I saw the most time cost
> (95%+) is taken by regexp execution.
>
> It seems the usage of regexps in output-svg.scm is to extract vector font
> content fragments from font svg assets. Can we refactor this work by an XML
> parser, maybe in C++?
>
> I saw there is another alternate option, svg-woff. But I encountered the
> scm error:
>
>> output-svg.scm:448:16: Unbound variable: paper
>>
>
> It seems an unresolved old bug for some years after googling it.
>
> This may be the biggest performance bottleneck of SVG backend at present,
> once fixed, we will get huge improvement.
>
> Any ideas?
>
> [image: image.png]
> [image: image.png]
> <image.png><image.png>