Am I right understanding you that we should put shx -> ttf font-name translation table into dxfloader.py? Or maybe even into ft2engine?
If such translation table is ok for dxfloader.py, I could try do it, but if it's deeper - sorry, I can't afford myself to dive in.
Thanks,
Kirill
P.S.
Just for the record: as already said, I have no style['1000'] entry in my DXF, and more, even when attribute 3 references geniso.shx, which is for sure absent on my system, in target SVG I get russian text more or less correctly rendered (as it turned out with fallback uniconvertor font BitstreamVeraSans-Roman).
That's why there is maybe a third option: just use shx font-name as-is, and issue an user-visible warning, that such-and-such dxf font was used without converting to TrueType.
Of course, it's a hack, but maybe if proper solution will be somehow delayed, it's better to have text with default font than not to have any text at all.
Max, thanks for your reply.
Am I right understanding you that we should put shx -> ttf font-name translation table into dxfloader.py? Or maybe even into ft2engine?
If such translation table is ok for dxfloader.py, I could try do it, but if it's deeper - sorry, I can't afford myself to dive in.
Thanks,
Kirill
P.S.
Just for the record: as already said, I have no style['1000'] entry in my DXF, and more, even when attribute 3 references geniso.shx, which is for sure absent on my system, in target SVG I get russian text more or less correctly rendered (as it turned out with fallback uniconvertor font BitstreamVeraSa ns-Roman) .
That's why there is maybe a third option: just use shx font-name as-is, and issue an user-visible warning, that such-and-such dxf font was used without converting to TrueType.
Of course, it's a hack, but maybe if proper solution will be somehow delayed, it's better to have text with default font than not to have any text at all.