SVG text-handling is weak at best. If you can use a PDF instead (which should be possible in almost all workflows, with the notable exception of vector graphics inline within a webpage), you’d be much better off.
Thanks Ben!
In our workflow, we do indeed need SVG’s. PDF is not suited for our purposes.
So far, we refrained from using justified text blocks, and we noticed that right aligned blocks would yield issues, which we erroneously thought were linked to font issues. Now we understand it is linked to the limitations of SVG.
We can confirm however that the export of music systems in SVG format works flawlessly :). (And right-aligned text in such music systems suffers from slight position shifts, but we can live with that.)
I’ve had to deal with this before. If you must have SVG but you want to guarantee that it displays properly, you need to export it from Dorico as a PDF, then convert it to SVG and convert to curves. This step is very important as it strips the font info and basically makes it just vector drawings. This is essential if it will be viewed on a computer that doesn’t have the correct font.
This method has worked well for me. An online option like Cloud Convert makes short work of batches.
1 Like
Hello Dan,
Thanks for the tip. It would involve an extra step in the production process, as we currently already convert directly the SVG into curves. The problem is that SVGs don’t have a property to justify or right align a text block, so we would have to test how PDF gets converted int an SVG that is properly aligned. I imagine that this conversion process can work if each word of the text block gets its proper coordinates.
I’ll see if we can test that extra step. I’ll let you know. Thanks again!
I think we will not go through the hassle of the extra production step. Our workaround: we don’t use justified text blocks… It is a matter of choice, and the extra effort is not worth it, for us.