Hi Hyunmook,
Thanks for your patience. Our product team has investigated the issue and would like to update you that problems with graphical
subsystem(PDFNEWNET-40678) has been solved with use of ConvertTransparencyAction parameter as following, but problems with font subsystem(PDFNEWNET-40688) still remain and these
problems are very serious.
Document pdfDocument = new Document(myDir+ “a.pdf”);
pdfDocument.Convert(myDir + “log.xml”, PdfFormat.PDF_A_1B,
ConvertErrorAction.Delete, ConvertTransparencyAction.Mask);
pdfDocument.Save(myDir + "a_pdfa.pdf");
The first problem is that input document has very specific font - “HYSMyeongJo-Medium”. This font is not embedded in source PDF document. PDF/A standard requires that this font must be embedded into document, but we can’t embed it cause this font is absent on our machines. It’s a clear question - what to embed? If this font is presented on host computers then the input document will be converted into PDF/A without problems.
But what to do if problem font is absent? This font is very specific and it is a difficult task to find a font which can substitute font “HYSMyeongJo-Medium” correctly. Adobe Acrobat substitutes this font with the font “AdobeMyungjoStd-Medium” and it is clear from font’s name that it is a private Adobe’s font and we can’t use it for our font substitution. We have implemented a new feature that gives a possibility to set and use custom font substitution for customers, if they have problems with absence of a font on destination machine. To set font substitution they can use code like this:
FontRepository.Substitutions.Add(new SimpleFontSubstitution("HYSMyeongJo-Medium", "MingLiU"));
And here question arises what font to use for substitution is transmitted on customer’s side.
But if you agree to use custom font substitution another problem also have place with substitution of font “HYSMyeongJo-Medium”. This font has a specific encoding - “KSC-EUC-H”. Aspose.Pdf can not support encodings like this properly. And this support will be appeared after fix for task PDFNEWNET-40448. When this fix can be? It’s a difficult question, cause this fix requires very serious remake of almost all encoding functionality which has more than 100K of code. So we can’t guarantee that fix for PDFNEWNET-40448 will be at 11.9 version. After investigation and implementation of some encoding functionality in versions 11.8-11.9 situation with ETA for PDFNEWNET-40448 will be more clear.
We suppose there are no another approaches to solve this problem except:
destination machine has font “HYSMyeongJo-Medium” or
set custom font substitution and use it after fix of PDFNEWNET-40448.
So we have questions here -
Are you agree to substitute fonts at your own rules? If you disagree with it then task has to be closed as known issue, because we can’t use Adobe’s font. And if you agree for fonts substitution then can you wait for this time or not?
Please confirm your understanding. We are sorry for the inconvenience caused.
Best Regards,