Please check if the attachment opens in Inkscape 1.3 or 1.4 version. In version 1.2.2, the file that opens well does not work in the updated version or takes more than 20 minutes. I want to know if it's my computer problem or an updated version of the bug. I am currently using Windows 10.
I think the reason it works fine in Inkscape 1.3 alpha, is because there has been an important upgrade, where unknown fonts are converted to paths.
This obviously means that the text is no longer searchable. The import dialog can also show what fonts are missing (so you could download and install them). When you have the font installed, obviously the text will be searchable again. Note that once the text is imported with "convert to path" ... it is no longer text.
It means it takes a long time to convert a missing font into a path, right? I got it. Thank you.
It's hard to download and install all fonts, so I'll just have to keep using the 1.2 version.
Thank you very much.
I'm on a different computer now - here I have Inkscape 1.2
The text gets imported, but it's clearly a different font (on my computer). So apparently it uses the default SANS font for this case (which happens to support UTF-8 and so also this character set). So maybe it works fine in Inkscape 1.2 because the subsitute font is close enough for you not to notice the difference.
Working ok here...
Inkscape 1.3-alpha (2a5ddc9d23, 2023-03-29)Β Β OS version: Windows 10 22H2
Hi,
I think the reason it works fine in Inkscape 1.3 alpha, is because there has been an important upgrade, where unknown fonts are converted to paths.
This obviously means that the text is no longer searchable. The import dialog can also show what fonts are missing (so you could download and install them). When you have the font installed, obviously the text will be searchable again. Note that once the text is imported with "convert to path" ... it is no longer text.
V1.2.x may only offer font substitution.
v 1.3 provides moreΒ options for missing fonts that conversion to paths. "Substitute" works fine here.
I'm on a different computer now - here I have Inkscape 1.2
The text gets imported, but it's clearly a different font (on my computer). So apparently it uses the default SANS font for this case (which happens to support UTF-8 and so also this character set). So maybe it works fine in Inkscape 1.2 because the subsitute font is close enough for you not to notice the difference.
Β