You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#2521 which reported this issue alongside another issue relating to docx not adding the fontTable.xml to the document.rels.xml
It seems that only the latter issue was fixed, and this original issue with spaces in the filename remains.
I believe it should be a simple fix, if you look at how MS word embeds custom fonts, it just names each font in the fonts/ dir as font1.odttf etc.
Workaround
I am having a look into this issue, as it seems that custom fonts with spaces do not work at all - using the workaround mentioned in this other issue replacing spaces with - does not seem to work.
The file is no longer corrupted, but the font families do not match up with font table properly in this intance
The text was updated successfully, but these errors were encountered:
There was a similar issue from the past
#2521 which reported this issue alongside another issue relating to
docx
not adding the fontTable.xml to the document.rels.xmlIt seems that only the latter issue was fixed, and this original issue with spaces in the filename remains.
I believe it should be a simple fix, if you look at how MS word embeds custom fonts, it just names each font in the fonts/ dir as font1.odttf etc.
Workaround
I am having a look into this issue, as it seems that custom fonts with spaces do not work at all - using the workaround mentioned in this other issue replacing spaces with
-
does not seem to work.The file is no longer corrupted, but the font families do not match up with font table properly in this intance
The text was updated successfully, but these errors were encountered: