Skip to content

Add reference pages for 15 operators named only on the level pages #11

Closed

Description

@HassanAkbar

These 15 operators are named on docs/levels/level-2.adoc or docs/levels/level-3.adoc, but have no reference page under docs/commands/:

currentglobal, currentpagedevice, filter, makepattern, setblackgeneration, setcolor, setcolorspace, setglobal, sethalftone, setpacking, setpagedevice, setpattern, setsmoothness, setundercolorremoval, shfill

setglobal and currentglobal also have no category to go in, because the Guide has no VM category.

Suggested fix: add a reference page for each, with its category and LanguageLevel, and a VM category for setglobal and currentglobal.

Context: claricle/postscript builds its operator vocabulary from the Guide's command pages (claricle/postscript#4). Until these pages exist, the gem supplies their categories and levels in data/operator_overrides.yml, and each entry's reason links back here. #10 covers the three operators whose level the Level 3 page gets wrong.

Activity

  1. added 2 commits that reference this issue on Oct 22, 2026
  2. HassanAkbar commented on Oct 23, 2026

    @HassanAkbar
    MemberAuthor

    All of this is now on main (#15):

    • Added reference pages under docs/commands/references/ for the 15 operators: currentglobal, currentpagedevice, filter, makepattern, setblackgeneration, setcolor, setcolorspace, setglobal, sethalftone, setpacking, setpagedevice, setpattern, setsmoothness, setundercolorremoval and shfill. Each page gives its PostScript LanguageLevel.
    • Each operator is now listed in its category index: Color, Device Output, File I/O, Graphics State, Painting, and Arrays and Strings.
    • Added a Virtual Memory category (docs/commands/vm/) for setglobal and currentglobal, and linked it from the command overview.

    The three operators the Level 3 page listed at the wrong level were fixed separately in #13 (#10).

    Now that the pages exist, claricle/postscript can read these operators' categories and levels from the Guide and drop their entries from data/operator_overrides.yml. That clean-up belongs in that repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions