When converting DWG to PDF, the%% 130,%% 131,%% 132,%% 133,%% 162,%% 163 set under tssdeng.shx cannot be recognized
tssdeng.7z (7.4 KB)
@78783718,
Hi.
Could you please try to load image with load options, e.g.:
using (CadImage cadImage = (CadImage)Image.Load(fileName, new LoadOptions { SpecifiedEncoding = CodePages.SimpChinese }))
{
...
}
If this is not helpful, please, attach the initial DWG file, we will investigate the reason.
@78783718,
we have created CADNET-9591 to investigate this issue better and fix it. It could be helpful for us if you can send additionally the picture with the expected result (that’s just to avoid any confusion as I see some other default version of tssdeng font exists, probably, with other symbols).
The issues you have found earlier (filed as CADNET-9591) have been fixed in this Aspose.CAD for .NET 24.2 update. This message was posted using Bugs notification tool by oleksii.gorokhovatskyi
demo.7z (925.6 KB)
Now there is another error, for multi line text. There is no problem with single line text.
Unhandled exception. System.AggregateException: One or more errors occurred. (Image export failed. Error during PDF export: The given key ‘0’ was not present in the dictionary.)
—> Aspose.CAD.CadExceptions.ImageSaveException: Image export failed. Error during PDF export: The given key ‘0’ was not present in the dictionary.
—> System.Exception: Error during PDF export: The given key ‘0’ was not present in the dictionary.
—> System.Collections.Generic.KeyNotFoundException: The given key ‘0’ was not present in the dictionary.
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
The issues you have found earlier (filed as CADNET-9672) have been fixed in this Aspose.CAD for .NET 24.7 update. This message was posted using Bugs notification tool by oleksii.gorokhovatskyi
Now a new problem has arisen。Remove. 7z
problem.7z.003.7z (5 MB)
problem.7z.004.7z (5 MB)
problem.7z.005.7z (983.2 KB)
problem.7z.001.7z (5 MB)
problem.7z.002.7z (5 MB)
@78783718,
Hi,
the latest issue CADNET-9863 has been fixed in the latest Aspose.CAD for .NET 24.9 release.