QRnZine/c2.svg
2025-02-25 20:46:59 -06:00

24 lines
1.4 KiB
XML

<svg xmlns="http://www.w3.org/2000/svg" width="550" height="425" viewBox="0 0 550 425">
<rect width="550" height="425" fill="#FFFFFF" stroke="#AAAAAA" />
<text x="105" y="400">Page 1</text>
<text x="380" y="400">Page 2</text>
<foreignObject x="25" y="25" width="225" height="375">
<div xmlns="http://www.w3.org/1999/xhtml">
<b>Preface/Disclaimer</b>
<p>This zine and QRnZine itself are pretty technical in nature and assume that the user is fairly technically advanced going in, with at least basic familiarity with command-line tools and editing of programming, scripting, and markup languages.</p>
<p>The intent of this zine is mostly to explore how a few interesting tools work together to make this document possible, but skips over a lot in the process to fit the medium.</p>
</div>
</foreignObject>
<foreignObject x="300" y="25" width="225" height="375">
<div xmlns="http://www.w3.org/1999/xhtml">
<b>Introduction</b>
<p><i>Link rot is very real and photocopiers don't come with an easy edit button.</i></p>
<p>That's basically the problem QRnZine is intended to fix.</p>
<p>If you could put the source code of a zine within the zine itself, other people could hopefully more easily replicate, modify, and create zines built using that one as a template.</p>
<p>But how do you fit the source code for a zine inside itself?</p>
</div>
</foreignObject>
</svg>