Updating GitHub Pages

peteroupc · peteroupc · commit b5bb90821758 · 2025-12-12T04:36:07.000-05:00
diff --git a/graphics.html b/graphics.html
@@ -1,10 +1,10 @@
-<!DOCTYPE html><html  xmlns:dc="http://purl.org/dc/terms/" xmlns:og="http://ogp.me/ns#" ><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><title>Graphics and Music Challenges for Classic Computer Applications</title><meta name="citation_pdf_url" content="https://peteroupc.github.io/graphics.pdf"><meta name="citation_url" content="https://peteroupc.github.io/graphics.html"><meta name="citation_title" content="Graphics and Music Challenges for Classic Computer Applications"><meta name="dc.date" content="2025-12-10"><meta name="citation_date" content="2025/12/10"><meta name="citation_publication_date" content="2025/12/10"><meta name="citation_online_date" content="2025/12/10"><meta name="og:title" content="Graphics and Music Challenges for Classic Computer Applications"><meta name="og:type" content="article"><meta name="og:url" content="https://peteroupc.github.io/graphics.html"><meta name="og:site_name" content="peteroupc.github.io"><meta name="dc.format" content="text/html"><meta name="dc.language" content="en"><meta name="title" content="Graphics and Music Challenges for Classic Computer Applications"><meta name="dc.title" content="Graphics and Music Challenges for Classic Computer Applications"><meta name="twitter:title" content="Graphics and Music Challenges for Classic Computer Applications"><meta name="dc.creator" content="Peter Occil"/><meta name="author" content="Peter Occil"/><meta name="citation_author" content="Peter Occil"/><meta name="viewport" content="width=device-width"><link rel=stylesheet type="text/css" href="/style.css">
+<!DOCTYPE html><html  xmlns:dc="http://purl.org/dc/terms/" xmlns:og="http://ogp.me/ns#" ><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><title>Graphics and Music Challenges for Classic Computer Applications</title><meta name="citation_pdf_url" content="https://peteroupc.github.io/graphics.pdf"><meta name="citation_url" content="https://peteroupc.github.io/graphics.html"><meta name="citation_title" content="Graphics and Music Challenges for Classic Computer Applications"><meta name="dc.date" content="2025-12-11"><meta name="citation_date" content="2025/12/11"><meta name="citation_publication_date" content="2025/12/11"><meta name="citation_online_date" content="2025/12/11"><meta name="og:title" content="Graphics and Music Challenges for Classic Computer Applications"><meta name="og:type" content="article"><meta name="og:url" content="https://peteroupc.github.io/graphics.html"><meta name="og:site_name" content="peteroupc.github.io"><meta name="dc.format" content="text/html"><meta name="dc.language" content="en"><meta name="title" content="Graphics and Music Challenges for Classic Computer Applications"><meta name="dc.title" content="Graphics and Music Challenges for Classic Computer Applications"><meta name="twitter:title" content="Graphics and Music Challenges for Classic Computer Applications"><meta name="dc.creator" content="Peter Occil"/><meta name="author" content="Peter Occil"/><meta name="citation_author" content="Peter Occil"/><meta name="viewport" content="width=device-width"><link rel=stylesheet type="text/css" href="/style.css">
             <script type="text/x-mathjax-config"> MathJax.Hub.Config({"HTML-CSS": { availableFonts: ["STIX","TeX"], linebreaks: { automatic:true }, preferredFont: "TeX" },
                     tex2jax: { displayMath: [ ["$$","$$"], ["\\[", "\\]"] ], inlineMath: [ ["$", "$"], ["\\\\(","\\\\)"] ], processEscapes: true } });
             </script><script type="text/javascript" async src="https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.5/MathJax.js?config=TeX-AMS_HTML-full"></script></head><body>  <div class="header">
 <nav><p><a href="#navigation">Menu</a> - <a href="#top">Top</a> - <a href="/">Home</a></nav></div>
 <div class="mainarea" id="top">
-<h1 id="graphics-and-music-challenges-for-classic-computer-applications">Graphics and Music Challenges for Classic Computer Applications</h1><p>This version of the document is dated 2025-12-10.</p>
+<h1 id="graphics-and-music-challenges-for-classic-computer-applications">Graphics and Music Challenges for Classic Computer Applications</h1><p>This version of the document is dated 2025-12-11.</p>
 
 <p>The following are challenges I make to the computer community, relating to:</p>
 
@@ -188,7 +188,7 @@ <h3 id="optional-limits">Optional Limits</h3>
   <li>The game uses no more than 16 million bytes of system memory at a time.</li>
   <li>The game uses no more than 655,360 bytes of system memory (plus 262,144 bytes of additional memory for graphics use only) at a time.<sup id="fnref:10"><a href="#fn:10" class="footnote" rel="footnote" role="doc-noteref">10</a></sup></li>
   <li>The game aims for a frame rate of 30 frames per second.</li>
-  <li>The game’s graphics are rendered in software.  That is, the rendering does not rely on a video card, a graphics accelerator chip, or the operating system’s graphics programming interface (such as GDI, OpenGL, or Direct3D) with the sole exception of sending a finished frame to the screen (such as through GDI’s <code>StretchDIBits</code> or copying to VGA’s frame buffer).</li>
+  <li>The game’s graphics are rendered in software.  That is, the rendering does not rely on a video card, a graphics accelerator chip, or the operating system’s graphics programming interface (such as GDI, OpenGL, or Direct3D) with the sole exception of sending a finished frame to the screen (such as through GDI’s <code>StretchDIBits</code> or copying to VGA’s video memory).</li>
   <li>The game’s graphics rendering employs only 32-bit and smaller integers and fixed-point arithmetic.<sup id="fnref:11"><a href="#fn:11" class="footnote" rel="footnote" role="doc-noteref">11</a></sup></li>
 </ul>
 
diff --git a/graphics.md b/graphics.md
@@ -142,7 +142,7 @@ A game may impose further constraints to this specification (for example, to red
 - The game uses no more than 16 million bytes of system memory at a time.
 - The game uses no more than 655,360 bytes of system memory (plus 262,144 bytes of additional memory for graphics use only) at a time.[^10]
 - The game aims for a frame rate of 30 frames per second.
-- The game's graphics are rendered in software.  That is, the rendering does not rely on a video card, a graphics accelerator chip, or the operating system’s graphics programming interface (such as GDI, OpenGL, or Direct3D) with the sole exception of sending a finished frame to the screen (such as through GDI’s `StretchDIBits` or copying to VGA’s frame buffer).
+- The game's graphics are rendered in software.  That is, the rendering does not rely on a video card, a graphics accelerator chip, or the operating system’s graphics programming interface (such as GDI, OpenGL, or Direct3D) with the sole exception of sending a finished frame to the screen (such as through GDI’s `StretchDIBits` or copying to VGA's video memory).
 - The game's graphics rendering employs only 32-bit and smaller integers and fixed-point arithmetic.[^11]
 
 <a id=Notes_on_Specification></a>
