Sorry about the boring sentences found here: http://www.xmlmind.com/xmleditor/faq.html#custom_pdf_fonts
We have re-tested this feature using latest Java 11 on macOS Mojave and the suggested workaround works great (after restarting XXE, as recommended in the "Preferences" dialog)...except that the "Times New Roman" font family lacks the glyphs for some "exotic" languages (e.g. "ru", "pl" OK; "hi" NOT OK).
After choosing another font family (e.g. "Arial Unicode MS") and mapping it to "serif", the problem was definitely solved.
On 12/03/2018 12:17 AM, Leif Halvard Silli wrote:
I will keep me eyes open to eventually uncover the bug. http://www.xmlmind.com/xmleditor/faq.html#custom_pdf_fonts As for the FAQ, and with my best intentions, when I read the FAQ today, I come to the conclusion that the problem is that it is not written the way I expect: After the very practical question «Is there a workaround for this problem?», a very direct "Yes" and at least a general 'howto' would have been in place. Only after such a basic howto would I eventually expect to see background information explaining why the workaround was necessary in the first place. (And possibly some caveats info as well.) Instead the reply begins with the 'why' in the form of 5 sentences that covers something which the frequently asked question did not mention as an issue: An explaination for WHY the user has experienced this problem (basically: «this is not XMLmind’s fault») followed by a high-level explanation of how to solve the problem. Only in the last two sentences (6 and 7), practical help with regard to «a workaround for this problem» is offered: * This can be done from within XMLmind XML Editor. More information in XMLmind XML Editor - Online Help, Apache FOP options and RenderX XEP options. Suggestion: Make those last two sentences the first two sentences of the reply, and the FAQ is already much better. Why? Because: To me, the current five first sentences are slightly annoying. Why must I read so much "stuff" *and* as well understand why/how/if it relates to my problem, before I am offered the solution? Why not instead focus on the good news? The good message is that XMLmind does offer a workaround for this problem. Hiding the good news behind info that some find boring and others are well (or at least enough well) aware of, is not ideal IMO.
-- XMLmind XML Editor Support List xmleditor-support@xmlmind.com http://www.xmlmind.com/mailman/listinfo/xmleditor-support
