[NTG-context] Re: SPR: was Re: Re: language in tagging and export

16 Jul 2025


      On 7/16/2025 1:14 AM, Max Chernoff via ntg-context wrote:
...
Hi Jim,
On Tue, 2025-07-15 at 10:06 -0300, Jim wrote:
...
Might I ask you
(a) To confirm that your PDF reader does, indeed, do SPR?
     (I.e., not just everything else on your system.)
     and
Ah, good point, I should have checked first. Using the following test
file:
\loadtypescriptfile[plex]
\setupbodyfont[plex-thin, sans]
     \setupinterlinespace[1sp]
\define[1]\makeline{%
         \setupbodyfont[#1pt]%
         \dorecurse{
             \numexpression(\textwidth / \widthofstring{l}) - 1\relax
         }{l\hfill}%
         \unskip%
         \par%
     }
\define\makelines{%
         \processcommalist[2, 4, 6, 8, 10, 11, 12, 16, 24, 36, 72]\makeline%
     }
\startTEXpage[width=6in]
         \makelines
\startframedtext[
             offset=0pt,
             width=broad,
             background=color,
             backgroundcolor=black,
             color=white,
         ]
             \makelines
         \stopframedtext
     \stopTEXpage
Chromium and Firefox (pdf.js) use subpixel rendering, while Evince,
Okular, MuPDF, and xpdf just use greyscale antialiasing. I usually use
Firefox to view PDFs, and everything else on my system uses subpixel
rendering, so I just assumed that the rest of the PDF viewers did as
well.
all side effects of these pattents involved ... pathetic large company 
policies ... esp given how trhey benefit from open source (and we're not 
even talking stuff that can't be invented multiple times at the same 
place independently)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------