ascherer / web Goto Github PK

Include webmacx.tex and makeall, write a README file and add a license.

• CWEB
• CTIE
• TIE

See Xcwebmac.tex, which uses code from knuth.drv.

There is already a branch from 2022!

On MacOS 10.15.7 with Adobe Acrobat Reader 2021.001.20135 we get an error popup with any PDF file created with the \ifpdftex code in pwebmac.tex and if we don't kill this dialog and close the offending PDF view then the whole system freezes dead and reboots due to the crash.

Also, the online PDF validator reports many errors like "The operator has an invalid number of operands" and "The value of the key Last is 2457 0 R but must be 2091 0 R".

According to @kberry, 'we' are free to modify dvicopy, patgen, pktogf, and pktype, because they are not maintained by DEK. bibtex will not be changed by OP anytime soon.

\[ has an extra } issued by pdftex somewhere in \make....

The "new" webmac.tex produces 536 pages instead of 535 with the original webmac.tex. Section §585 is broken differently.

Both pdftex and xetex produce weird "outlines" for mf.web and tex.web.

Investigate macro \[.

Extend Appendix F:

• Add with pwebmac.tex
• New section about Hypertext like in cwebman

While we're at it, it's maybe a good idea to read it (again).

pdfwebtocfront.tex starts the PDF output for pltotf.web on page '302' with Property list description of font metric data (in small caps) from starred section 5, instead of with Introduction from starred section 1. There seems to be a page shift, because all headlines start one page early.

Amend TeX Live's weave.ch accordingly and apply #21.

Because of getopt, it might rather be option -p.

Also \catecontentspage.

Maybe that's not a good idea, because it requires pwebmac.tex.

These macros are totally irrelevant for Pascal/WEB.

First, we want to reproduce the "original" form of the tables-of-contents pages for the 19 WEB programs with plain old DVI-producing TeX. ✔️

Next, we use various PDF-producing variants of the TeX engine. ✔️

Last, with pdfwebtocfront.tex added, {pdf,xe}TeX picks up the incorrect \topmarks or \rheader text for most of the WEB sources.

weave weave; pdftex weave produces weave.pdf that gives tons of warnings à la

{Path|Text} object uses {Gray|RGB} based color space.
No PDF/A Output Intent specified

on https://freepdfonline.com/verifypdfa/

TeX Stackexchange knows an answer for pdfTeX: https://tex.stackexchange.com/questions/61217/latex-color-and-icc-color-profile

Downloading ICC profile sRGB2014.icc from http://www.color.org/srgbprofiles.xalter#v2 and adding the relevant PDF code in \ifpdftex purges all of these color warnings.

All that's left are these 'Preflight Results':

Document Results
XRef cannot be an object stream (not a PDF 1.4 compatible feature)
Metadata key missing in root catalog
MarkInfo dictionary is not present
Structure Tree Root missing.

Page 1 Results
Link Annotation's F key is missing
Unicode info not available for font -- tons of these on every page

Work has started in branch https://github.com/ascherer/web/tree/pdf-icc-color-profiles

pwebmac should use cwebacromac and permit processing with LuaTeX.

CWEB's cwebmac.tex supports

• Plain TeX with/out \let\pdf+ to create clickable links in PDF output, using xdvipdfmx manually
• pdfTeX to create clickable links in PDF output
• XeTeX with/out \let\pdf+ to create clickable links in PDF output, using xdvipdfmx in the background

Goal of this issue is to amend webmac.tex with the separate PDF functionality from pdfwebmac.tex and xewebmac.tex.