On 2023-12-15 13:59:56 +0000, Adam Sampson wrote: > I'm pretty sure that was an xpopple (xpdf upstream) fix -- the fault was > caused by me adding render tables to the default resources for UTF-8 > support. In December 2021, I changed -font to affect the "font" resource > rather than the "fontList" resource, which should make the behaviour > match the documentation again. I also added a section to xpdf(1) about > configuring the UI fonts using render tables or regular X fonts, so I > think this bug is fixed now (unless anybody has any further suggestions > for improvement).
I had noticed the section "USER INTERFACE FONTS" and I was wondering whether this was new. The documenation seems fine to me. Thanks. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
