http://cc.practices.tools/wiki/api.php?action=feedcontributions&feedformat=atom&user=SimoonCreative Crowds wiki - User contributions [en]2026-04-09T16:15:43ZUser contributionsMediaWiki 1.45.1http://cc.practices.tools/wiki/index.php?title=Fonts&diff=5543Fonts2026-03-21T12:08:36Z<p>Simoon: /* Hosted on CC */</p>
<hr />
<div>==Hosted elsewhere==<br />
<br />
* https://usemodify.com An aggregator made by Raphäel Bastide<br />
* https://www.design-research.be/by-womxn/ Badass Libre fonts by womxn<br />
* https://velvetyne.fr/ French Libre fonts type foundry<br />
* http://osp.kitchen/foundry/ The foundry of Brussel's Open Source Publishing<br />
* http://www.peter-wiegel.de/ Weird and wonderful letters (mostly script and display) made by font-dabbler Peter Wiegel, for his personal foundry "Cat Fonts"<br />
* https://justseeds.org/project/justseeds-open-type-project/ "The Justseeds Open Type Project creates open-access fonts for activists, organizers, and movement designers"<br />
* https://typotheque.genderfluid.space/ The typotheque of Franco-Belgian collective Bye Bye Binary<br />
<br />
==Hosted on CC==<br />
<br />
https://cc.practices.tools/fonts/<br />
<br />
Typefaces and fonts that are installed on CC (often) come with pre-prepared stylesheets. To use these fonts, first import the relevant stylesheet:<br />
<br />
<code>@import url('https://path.to.the.stylesheet/stylesheet.css');</code><br />
<br />
Here is an always under construction list of the fonts installed on CC:<br />
<br />
{| class="wikitable sortable"<br />
! foundry !! typeface !! designer !! type !! families & styles || formats || licence || stylesheet<br />
|-<br />
| || All Con || Simon Browne || monospace, sans-serif || Regular, Bold, Extended, Big Dots, Monospace || .ttf || || https://cc.practices.tools/fonts/simoon/AC/stylesheet.css<br />
|-<br />
| [https://authentic.website/ Authentic] || [https://authentic.website/sans Authentic Sans] || Christina Janus, Desmond Wong || sans-serif || 60, 90, 130, 150 (Regular & Condensed) || .otf, .woff, .woff2 || [http://www.wtfpl.net/ WTFPL] || https://cc.practices.tools/fonts/Authentic_Sans/stylesheet.css<br />
|-<br />
| [https://typotheque.genderfluid.space Bye Bye Binary] || [https://typotheque.genderfluid.space/amiamie.html Amiamie] || Mirat Masson || sans-serif || Light, Regular, Bold, Italic || .otf, .ttf, .woff, .woff2 || [https://openfontlicense.org/open-font-license-official-text/ OFL 1.1] || https://cc.practices.tools/fonts/BBB/Amiamie-Typeface-main/stylesheet.css<br />
|-<br />
| [https://typotheque.genderfluid.space Bye Bye Binary] || [https://typotheque.genderfluid.space/baskervvol.html Baskervvol] || Bye Bye Binary || serif || Base, Fondue || .otf, .ttf, .woff, .woff2 || [https://openfontlicense.org/open-font-license-official-text/ OFL 1.1] || https://cc.practices.tools/fonts/BBB/baskervvol/stylesheet.css<br />
|-<br />
| [https://typotheque.genderfluid.space Bye Bye Binary] || [https://typotheque.genderfluid.space/poppins.html BBB-Poppins-TN] || Eugénie Bidaut & Camille°Circlude || sans-serif || Regular, Italic, Bold, Bold Italic || .otf, .ttf, .woff, .woff2 || [https://openfontlicense.org/open-font-license-official-text/ OFL 1.1] || https://cc.practices.tools/fonts/BBB/bbb-poppins-tn/stylesheet.css<br />
|-<br />
| [https://typotheque.genderfluid.space Bye Bye Binary] || [https://typotheque.genderfluid.space/poppins.html Crozette] || Thais Cuny || decorative || Regular || .otf, .ttf, .woff, .woff2 || [https://openfontlicense.org/open-font-license-official-text/ OFL 1.1] || https://cc.practices.tools/fonts/BBB/crozette/stylesheet.css<br />
|-<br />
| [https://typotheque.genderfluid.space Bye Bye Binary] || [https://typotheque.genderfluid.space/ductus-mono.html Ductus Mono] || Amélie Dumont || sans-serif, monospace || Regular, Calligraphic, Geometric || .otf, .ttf, .woff, .woff2 || [https://openfontlicense.org/open-font-license-official-text/ OFL 1.1] || https://cc.practices.tools/fonts/BBB/ductus-mono/stylesheet.css<br />
|-<br />
| || Computer Modern || Donald Knuth || sans, sans-serif, script, monospace || Bright, Bright_Semibold, Classical Serif Italic, Concrete, Sans, Sans Demi-Condensed, Serif, Serif Slanted, Typewriter Light, Typewriter Variable, Upright Italic || .eot, .woff, .ttf, .svg || [https://openfontlicense.org/open-font-license-official-text/ OFL 1.1] || https://cc.practices.tools/fonts/Computer_Modern/stylesheet.css<br />
|-<br />
| [https://www.collletttivo.it Collletttivo] || [https://www.collletttivo.it/typefaces/absans Absans] || Valerio Monopoli || sans-serif || Regular || .otf, .woff, .woff2 || [https://openfontlicense.org/open-font-license-official-text/ OFL 1.1] || https://cc.practices.tools/fonts/collletttivo/CLT-Absans/stylesheet.css<br />
|-<br />
| [https://www.collletttivo.it Collletttivo] || [https://www.collletttivo.it/typefaces/necto-mono Necto Mono] || Marco Condello || monospace || Regular || .otf, .woff, .woff2 || [https://openfontlicense.org/open-font-license-official-text/ OFL 1.1] || https://cc.practices.tools/fonts/collletttivo/CLT-Necto_Mono/stylesheet.css<br />
|-<br />
| [https://www.collletttivo.it Collletttivo] || [https://www.collletttivo.it/typefaces/ortica Ortica] || Ben Bovani || serif || Light, Regular, Bold, Angular || .otf, .woff, .woff2 || [https://openfontlicense.org/open-font-license-official-text/ OFL 1.1] || https://cc.practices.tools/fonts/collletttivo/CLT-Ortica/stylesheet.css<br />
|-<br />
| || [https://healtheweb.site/ Heal the Web] || Rainbow Unicorn & Jakub Kanior || sans-serif || A, B || .otf || [https://www.mozilla.org/en-US/MPL/2.0/FAQ/ MPL-2.0] || https://cc.practices.tools/fonts/HealTheWeb/stylesheet.css<br />
|-<br />
| || [https://usemodify.com/fonts/lucette/ Lucette] || Yann Linguinou || serif || Regular, Italic || .otf, .ttf, .woff, .woff2 || [https://openfontlicense.org/open-font-license-official-text/ OFL 1.1] || https://cc.practices.tools/fonts/Lucette/font/stylesheet.css<br />
|-<br />
| [http://osp.kitchen/foundry/ OSP] || [http://osp.kitchen/foundry/crickx/ Crickx] || OSP || script, display || PubliFlourChrystelise, PubliFluorDroiteOuverte, PubliFluorDroiteOuverte, PubliFluorDroiteRush, PubliFluorNormale, PubliFluorNormaleOuverte, PubliFluorNormaleRush || .otf, .woff || [https://constantvzw.org/wefts/cc4r.en.html CC4R] || https://cc.practices.tools/fonts/OSP/Crickx/stylesheet.css<br />
|-<br />
| || [https://www.redaction.us/ Redaction] || Jeremy Mickel || serif || 10, 35, 50, 70, 90, 100 (Regular, Italic, Bold) || .otf, .ttf, .woff, .woff2 || [https://openfontlicense.org/open-font-license-official-text/ OFL 1.1] || https://cc.practices.tools/fonts/Redaction/stylesheet.css<br />
|-<br />
| [https://velvetyne.fr/ Velvetyne] || [https://velvetyne.fr/fonts/degheest/ Degheest Family] || Ange Degheest, Camille Depalle, Eugénie Bidaut, Luna Delabre, Mandy Elbé, May Jolivet, Oriane Charvieux, Benjamin Gomez, Justine Herbel || pixel, monospace, sans-serif, serif || director regular, director light, director bold, director variable, abordage regular, basalte fond, basalte multicolor, basalte volume, equateur regular, ft88 bold, ft88 expanded, ft88 gothique, ft88 italic, ft88 regular, ft88 school, ft88 serif, latitude regular, louise regular || .otf, .ttf, .woff, .woff2 || [https://openfontlicense.org/open-font-license-official-text/ OFL 1.1] || https://cc.practices.tools/fonts/velvetyne/degheest-types/stylesheet.css<br />
|-<br />
| [https://velvetyne.fr/ Velvetyne] || [https://gitlab.com/velvetyne/Happy-Times-at-the-IKOB Happy Times at the IKOB] || Lucas Le Bihan || serif || regular, bold, italic || .otf, .ttf, .woff, .woff2 || [https://openfontlicense.org/open-font-license-official-text/ OFL 1.1] || https://cc.practices.tools/fonts/velvetyne/happy-times-at-the-IKOB/stylesheet.css<br />
|-<br />
| [https://velvetyne.fr/ Velvetyne] || Montchauve || Frank Adebiaye || modular titling fantasy || medium || .otf || [https://openfontlicense.org/open-font-license-official-text/ OFL 1.1] || https://cc.practices.tools/fonts/velvetyne/montchauve/stylesheet.css<br />
|-<br />
| [https://velvetyne.fr/ Velvetyne] || [https://github.com/CollectifWech/Savate Savate] || Collectif Wech || sans-serif || regular, italic || .eot, .svg, .ttf, .woff, .woff2 || [https://openfontlicense.org/open-font-license-official-text/ OFL 1.1] || https://cc.practices.tools/fonts/velvetyne/savate/stylesheet.css<br />
|-<br />
|}</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Main_Page&diff=5536Main Page2026-02-27T10:25:52Z<p>Simoon: </p>
<hr />
<div>__NOTOC__<br />
<div style="float:right;margin-left:1em;"><eplite id="cc-conditions" show-chat="false" /></div><br />
<br />
[[File:Creative-crowds-cc.png|200px]]<br />
<br />
Welcome to CC, a shared server currently maintained by Simon, Manetta and Doriane from Rotterdam/Brussels. <br />
<br />
With CC we explore how community gathers around specific experimental publishing tools, how hosted tools can be prototyped for activist collectivities, and how we can question and participate in a discourse around practices and tools.<br />
<br />
CC is currently hosting the following things:<br />
<br />
* [https://cc.practices.tools/octomode/ octomode] is running<br />
* [[Wiki-to-print|wiki-to-print]] is configured for use<br />
* [https://cc.practices.tools/etherdot/ etherdot] is stitching<br />
* [https://cc.practices.tools/pad/ pads]<br />
* [https://cc.practices.tools/fonts/ fonts]<br />
* [https://cc.practices.tools/traces/ traces]<br />
* [[Cobbled-paths|cobbled paths]] (not yet)<br />
* this wiki<br />
<br />
If you want, you can sign the '''collective calendar''' (on the right) as a way to collect server presences together. Under the calendar you can find the '''CC-collective conditions for use''' we formulated, which is something we consider to be in flux.<br />
<br />
You can write us at: [mailto:cc@practices.tools cc@practices.tools]<br />
<br />
<div style="columns:2;column-gap:5mm;column-fill:auto;"><br />
<br />
==A recent change==<br />
<br />
[[File:So-you-decided-to-make-a-zine-in-octomode.pdf|200px|thumb|left|Zine made by Simon during the Des*gn Week in Linz, November 2025]]<br />
<br style="clear:both;"><br />
<br />
<h1 style="display:block;border:0;background:linear-gradient(yellow,white);padding:0.5em;margin:1em 0 0.5em;border-radius:25px 0 0 0;">CC currently hosts...</h1><br />
<br />
==This wiki==<br />
<br />
We use this wiki as a working environment to produce publications with, organise the collective CC server maintenance work, and document things we do.<br />
<br />
==octomode==<br />
<br />
→ '''URL''': https://cc.practices.tools/octomode/<br><br />
→ '''more info''': [[Octomode|octomode]] <br><br />
→ '''git repo''': https://git.vvvvvvaria.org/CC/octomode<br />
<br />
Octomode is a collective editing space for PDF making, using Etherpad, Paged.js and Flask.<br />
<br />
The version installed on CC is open for use but it is password protected, reach out to us to ask for it, we share the password in an open ended network of trusted-peers and trusted-peers-of-peers.<br />
<br />
[[File:Rwx-octo5.svg|200px]]<br />
[[File:Read-write-execute-octo-mode.png|200px]]<br />
[[File:Octo-hands.png|200px]]<br />
<br />
==wiki-to-print==<br />
<br />
→ '''URL''': https://cc.practices.tools/wiki/Pdf:Unfolding<br><br />
→ '''more info''': [[wiki-to-print]] <br><br />
→ '''git repo''': https://git.vvvvvvaria.org/CC/wiki-to-print<br />
<br />
Wiki-to-print is a collective publishing environment that hooks into wiki practices and cultures. It uses MediaWiki software, CCS Print rules and Paged.js, to render a preview of the PDF in the browser.<br />
<br />
The version installed on CC is internally used. But if you're curious to try it, let us know.<br />
<br />
[[File:Wiki-to-print.gv.svg|200px]]<br />
<br />
==pads==<br />
<br />
→ '''URL''': https://cc.practices.tools/pads/<br />
<br />
Pads on CC are open for use for things related to CC in some way.<br />
<br />
==fonts==<br />
<br />
→ '''URL''': https://cc.practices.tools/fonts/<br><br />
→ '''more info''': [[Fonts]]<br />
<br />
We are hosting a very adhocly selected list of fonts to use them in web-to-print projects.<br />
<br />
==traces==<br />
<br />
→ '''URL''': https://cc.practices.tools/traces/<br />
<br />
Here we collect traces of our practices crossing with CC.<br />
<br />
</div></div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Main_Page&diff=5535Main Page2026-02-27T10:18:37Z<p>Simoon: </p>
<hr />
<div>__NOTOC__<br />
<div style="float:right;margin-left:1em;"><eplite id="cc-conditions" show-chat="false" /></div><br />
<br />
[[File:Creative-crowds-cc.png|200px]]<br />
<br />
Welcome to CC, a shared server currently maintained by Simon, Manetta and Doriane from Rotterdam/Brussels. <br />
<br />
With CC we explore how community gathers around specific experimental publishing tools, how hosted tools can be prototyped for activist collectivities, and how we can question and participate in a discourse around practices and tools.<br />
<br />
CC is currently hosting the following things:<br />
<br />
* [https://cc.practices.tools/octomode/ octomode] is running<br />
* [[Wiki-to-print|wiki-to-print]] is configured for use<br />
* [https://cc.practices.tools/etherdot/ etherdot] is graphing<br />
* [https://cc.practices.tools/pad/ pads]<br />
* [https://cc.practices.tools/fonts/ fonts]<br />
* [https://cc.practices.tools/traces/ traces]<br />
* [[Cobbled-paths|cobbled paths]] (not yet)<br />
* this wiki<br />
<br />
If you want, you can sign the '''collective calendar''' (on the right) as a way to collect server presences together. Under the calendar you can find the '''CC-collective conditions for use''' we formulated, which is something we consider to be in flux.<br />
<br />
You can write us at: [mailto:cc@practices.tools cc@practices.tools]<br />
<br />
<div style="columns:2;column-gap:5mm;column-fill:auto;"><br />
<br />
==A recent change==<br />
<br />
[[File:So-you-decided-to-make-a-zine-in-octomode.pdf|200px|thumb|left|Zine made by Simon during the Des*gn Week in Linz, November 2025]]<br />
<br style="clear:both;"><br />
<br />
<h1 style="display:block;border:0;background:linear-gradient(yellow,white);padding:0.5em;margin:1em 0 0.5em;border-radius:25px 0 0 0;">CC currently hosts...</h1><br />
<br />
==This wiki==<br />
<br />
We use this wiki as a working environment to produce publications with, organise the collective CC server maintenance work, and document things we do.<br />
<br />
==octomode==<br />
<br />
→ '''URL''': https://cc.practices.tools/octomode/<br><br />
→ '''more info''': [[Octomode|octomode]] <br><br />
→ '''git repo''': https://git.vvvvvvaria.org/CC/octomode<br />
<br />
Octomode is a collective editing space for PDF making, using Etherpad, Paged.js and Flask.<br />
<br />
The version installed on CC is open for use but it is password protected, reach out to us to ask for it, we share the password in an open ended network of trusted-peers and trusted-peers-of-peers.<br />
<br />
[[File:Rwx-octo5.svg|200px]]<br />
[[File:Read-write-execute-octo-mode.png|200px]]<br />
[[File:Octo-hands.png|200px]]<br />
<br />
==wiki-to-print==<br />
<br />
→ '''URL''': https://cc.practices.tools/wiki/Pdf:Unfolding<br><br />
→ '''more info''': [[wiki-to-print]] <br><br />
→ '''git repo''': https://git.vvvvvvaria.org/CC/wiki-to-print<br />
<br />
Wiki-to-print is a collective publishing environment that hooks into wiki practices and cultures. It uses MediaWiki software, CCS Print rules and Paged.js, to render a preview of the PDF in the browser.<br />
<br />
The version installed on CC is internally used. But if you're curious to try it, let us know.<br />
<br />
[[File:Wiki-to-print.gv.svg|200px]]<br />
<br />
==pads==<br />
<br />
→ '''URL''': https://cc.practices.tools/pads/<br />
<br />
Pads on CC are open for use for things related to CC in some way.<br />
<br />
==fonts==<br />
<br />
→ '''URL''': https://cc.practices.tools/fonts/<br><br />
→ '''more info''': [[Fonts]]<br />
<br />
We are hosting a very adhocly selected list of fonts to use them in web-to-print projects.<br />
<br />
==traces==<br />
<br />
→ '''URL''': https://cc.practices.tools/traces/<br />
<br />
Here we collect traces of our practices crossing with CC.<br />
<br />
</div></div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Upgrading_pagedjs&diff=5532Upgrading pagedjs2026-02-22T16:57:30Z<p>Simoon: /* Method */</p>
<hr />
<div>Up until today (February 21st, 2026), the version of pagedjs that Octomode depends on is 0.1.43.<br />
<br />
From today, we will upgrade to the latest stable version, 0.4.3.<br />
<br />
Octomode depends on two files that should be changed with the upgrade.<br />
<br />
* /opt/octomode/static/paged.polyfill.js (v0.1.43)<br />
* /opt/octomode/static/pagedjs.css (v0.2.0)<br />
<br />
These should be upgraded to <br />
<br />
* /opt/octomode/static/paged.polyfill.js (v0.4.3)<br />
* /opt/octomode/static/interface.css (v0.4)<br />
<br />
The file <code>paged.polyfill.js</code> can be overwritten, but as the CSS has a different filename, we should also update any templates with the old filename that are still being used by Octomode:<br />
<br />
* /opt/octomode/static/templates/pagedjs.html<br />
<br />
== Method ==<br />
<br />
1. go inside <code>/opt/octomode/static/</code> and download the files (make backups first)<br />
<br />
$ curl https://unpkg.com/pagedjs@0.4.3/dist/paged.polyfill.js > paged.polyfill.js<br />
$ curl https://gitlab.coko.foundation/pagedjs/interface-polyfill/-/raw/master/interface.css?ref_type=heads > interface.css<br />
<br />
2. change ownership to the www-data user<br />
<br />
$ chown www-data:www-data paged.polyfill.js<br />
$ chown www-data:www-data interface.css<br />
<br />
3. go inside <code>/opt/octomode/static/templates</code> and edit the template <code>pagedjs.html</code><br />
<br />
$ sudo nano pagedjs.html<br />
<br />
4. Replace the text "pagedjs.css" with "interface.css". Changing it from:<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='pagedjs.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
to<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='interface.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
TODO: upgrade pagedjs for wiki-to-print, which is a separate installation of pagedjs.<br />
<br />
[[Category:Sysadmin]]</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=CC_to_do_list&diff=5531CC to do list2026-02-21T14:37:24Z<p>Simoon: </p>
<hr />
<div>==A list of things to do==<br />
<br />
* <s>change email address associated with OVH (currently it's info@varia.zone)</s><br />
** check if OVH offers backups, or makes one full disk copy with vorta/borg (manetta)<br />
* <s>make servus account (manetta)</s> -- paid first invoice (apr+may+jun = €90) on 13/06 (mb)<br />
* <s>check our money status at Varia (simon)</s><br />
* send email to CC users that we know with a hello and backup reminder<br />
* <s>pay Manetta 566.69</s> (simon)<br />
* <s>checking Stimu application digital culture (simon)</s><br />
* <s>invoice varia for content/form (manetta)</s><br />
* <s>move octomode git to CC group on varia git (manetta)</s><br />
<br />
==Server things==<br />
<br />
* check backup situation again<br />
* check if certbot cronjob works<br />
* check if ssh root login works<br />
* think about the etherpad database: do we want to delete history of pads to keep the size of the database under 1GB? (currently 942MB, Jan 2026) or think of a way in which pads can be deleted?<br />
<br />
==Things to pick up, a collected list during our residency in Linz==<br />
<br />
* [[Finances]]<br />
** updating the wiki page on what we have spent (lol this is just about Servpub https://cc.practices.tools/wiki/Docum%E2%82%ACntation)<br />
* continue research question articulation of CC<br />
** feedback session?<br />
** how to invite crowd(s)<br />
** who do we invite directly?<br />
* things we want to install on the server<br />
* r/w/x/o ctomode writing<br />
** could be joined with "so, you decided..."<br />
* how public/open should the CC wiki be?<br />
* octomode work<br />
** welcome page<br />
** documentation<br />
** editing of octomode wiki page<br />
* CC git where?<br />
* publish interview with Femke and Pierre<br />
* <s>edit etherpad default text !!!</s> (done 3 Dec, manetta)<br />
* so, you decided... zine: how to extend the last few pages for more context, making it open-ended (for another time)<br />
* document Des*gn Week workshop + zine that we made<br />
<br />
==For later==<br />
<br />
* <s>send email to Varia about transfer of git repo</s> (not needed in the end i think, danny knows)<br />
* move box with many Content/Form copies from XPUB to elsewhere<br />
* move the wiki to another location in the server<br />
<br />
[[Category:Sysadmin]]</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Upgrading_pagedjs&diff=5530Upgrading pagedjs2026-02-21T14:34:57Z<p>Simoon: </p>
<hr />
<div>Up until today (February 21st, 2026), the version of pagedjs that Octomode depends on is 0.1.43.<br />
<br />
From today, we will upgrade to the latest stable version, 0.4.3.<br />
<br />
Octomode depends on two files that should be changed with the upgrade.<br />
<br />
* /opt/octomode/static/paged.polyfill.js (v0.1.43)<br />
* /opt/octomode/static/pagedjs.css (v0.2.0)<br />
<br />
These should be upgraded to <br />
<br />
* /opt/octomode/static/paged.polyfill.js (v0.4.3)<br />
* /opt/octomode/static/interface.css (v0.4)<br />
<br />
The file <code>paged.polyfill.js</code> can be overwritten, but as the CSS has a different filename, we should also update any templates with the old filename that are still being used by Octomode:<br />
<br />
* /opt/octomode/static/templates/pagedjs.html<br />
<br />
== Method ==<br />
<br />
1. go inside <code>/opt/octomode/static/</code> and download the files (make backups first)<br />
<br />
$ curl https://unpkg.com/pagedjs@0.4.3/dist/paged.polyfill.js > paged.polyfill.js<br />
$ curl https://gitlab.coko.foundation/pagedjs/interface-polyfill/-/raw/master/interface.css?ref_type=heads > interface.css<br />
<br />
2. change ownership to the www-data user<br />
<br />
$ chown www-data:www-data paged.polyfill.js<br />
$ chown www-data:www-data interface.css<br />
<br />
3. go inside <code>/opt/octomode/static/templates</code><br />
<br />
$ sudo nano pagedjs.html<br />
<br />
4. Replace the text "pagedjs.css" with "interface.css". Changing it from:<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='pagedjs.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
to<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='interface.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
TODO: upgrade pagedjs for wiki-to-print, which is a separate installation of pagedjs.<br />
<br />
[[Category:Sysadmin]]</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Upgrading_pagedjs&diff=5529Upgrading pagedjs2026-02-21T14:34:14Z<p>Simoon: /* Method */</p>
<hr />
<div>Up until today (February 21st, 2026), the version of pagedjs that Octomode depends on is 0.1.43.<br />
<br />
From today, we will upgrade the version to the latest stable version, 0.4.3.<br />
<br />
Octomode depends on two files that should be changed with the upgrade.<br />
<br />
* /opt/octomode/static/paged.polyfill.js (v0.1.43)<br />
* /opt/octomode/static/pagedjs.css (v0.2.0)<br />
<br />
These should be upgraded to <br />
<br />
* /opt/octomode/static/paged.polyfill.js (v0.4.3)<br />
* /opt/octomode/static/interface.css (v0.4)<br />
<br />
The file <code>paged.polyfill.js</code> can be overwritten, but as the CSS has a different filename, we should also update any templates with the old filename that are still being used by Octomode:<br />
<br />
* /opt/octomode/static/templates/pagedjs.html<br />
<br />
== Method ==<br />
<br />
1. go inside <code>/opt/octomode/static/</code> and download the files (make backups first)<br />
<br />
$ curl https://unpkg.com/pagedjs@0.4.3/dist/paged.polyfill.js > paged.polyfill.js<br />
$ curl https://gitlab.coko.foundation/pagedjs/interface-polyfill/-/raw/master/interface.css?ref_type=heads > interface.css<br />
<br />
2. change ownership to the www-data user<br />
<br />
$ chown www-data:www-data paged.polyfill.js<br />
$ chown www-data:www-data interface.css<br />
<br />
3. go inside <code>/opt/octomode/static/templates</code><br />
<br />
$ sudo nano pagedjs.html<br />
<br />
4. Replace the text "pagedjs.css" with "interface.css". Changing it from:<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='pagedjs.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
to<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='interface.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
TODO: upgrade pagedjs for wiki-to-print, which is a separate installation of pagedjs.<br />
<br />
[[Category:Sysadmin]]</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Upgrading_pagedjs&diff=5528Upgrading pagedjs2026-02-21T14:33:31Z<p>Simoon: </p>
<hr />
<div>Up until today (February 21st, 2026), the version of pagedjs that Octomode depends on is 0.1.43.<br />
<br />
From today, we will upgrade the version to the latest stable version, 0.4.3.<br />
<br />
Octomode depends on two files that should be changed with the upgrade.<br />
<br />
* /opt/octomode/static/paged.polyfill.js (v0.1.43)<br />
* /opt/octomode/static/pagedjs.css (v0.2.0)<br />
<br />
These should be upgraded to <br />
<br />
* /opt/octomode/static/paged.polyfill.js (v0.4.3)<br />
* /opt/octomode/static/interface.css (v0.4)<br />
<br />
The file <code>paged.polyfill.js</code> can be overwritten, but as the CSS has a different filename, we should also update any templates with the old filename that are still being used by Octomode:<br />
<br />
* /opt/octomode/static/templates/pagedjs.html<br />
<br />
== Method ==<br />
<br />
1. go inside <code>/opt/octomode/static/</code><br />
<br />
$ curl https://unpkg.com/pagedjs@0.4.3/dist/paged.polyfill.js > paged.polyfill.js<br />
$ curl https://gitlab.coko.foundation/pagedjs/interface-polyfill/-/raw/master/interface.css?ref_type=heads > interface.css<br />
<br />
2. change ownership to the www-data user<br />
<br />
$ chown www-data:www-data paged.polyfill.js<br />
$ chown www-data:www-data interface.css<br />
<br />
3. go inside <code>/opt/octomode/static/templates</code><br />
<br />
$ sudo nano pagedjs.html<br />
<br />
4. Replace the text "pagedjs.css" with "interface.css". Changing it from:<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='pagedjs.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
to<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='interface.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
TODO: upgrade pagedjs for wiki-to-print, which is a separate installation of pagedjs.<br />
<br />
[[Category:Sysadmin]]</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Upgrading_pagedjs&diff=5527Upgrading pagedjs2026-02-21T14:32:31Z<p>Simoon: /* Method */</p>
<hr />
<div>Up until today (February 21st, 2026), the version of pagedjs that Octomode depends on is 0.1.43.<br />
<br />
From today, we will upgrade the version to the latest stable version, 0.4.3.<br />
<br />
Octomode depends on two files that should be changed with the upgrade.<br />
<br />
* /opt/octomode/static/paged.polyfill.js (v0.1.43)<br />
* /opt/octomode/static/pagedjs.css (v0.2.0)<br />
<br />
These should be upgraded to <br />
<br />
* /opt/octomode/static/paged.polyfill.js (v0.4.3)<br />
* /opt/octomode/static/interface.css (v0.4)<br />
<br />
The file <code>paged.polyfill.js</code> can be overwritten, but as the CSS has a different filename, we should also update any templates that are being used by Octomode:<br />
<br />
* /opt/octomode/static/templates/pagedjs.html<br />
<br />
== Method ==<br />
<br />
1. go inside <code>/opt/octomode/static/</code><br />
<br />
$ curl https://unpkg.com/pagedjs@0.4.3/dist/paged.polyfill.js > paged.polyfill.js<br />
$ curl https://gitlab.coko.foundation/pagedjs/interface-polyfill/-/raw/master/interface.css?ref_type=heads > interface.css<br />
<br />
2. change ownership to the www-data user<br />
<br />
$ chown www-data:www-data paged.polyfill.js<br />
$ chown www-data:www-data interface.css<br />
<br />
3. go inside <code>/opt/octomode/static/templates</code><br />
<br />
$ sudo nano pagedjs.html<br />
<br />
4. Replace the text "pagedjs.css" with "interface.css". Changing it from:<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='pagedjs.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
to<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='interface.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
TODO: upgrade pagedjs for wiki-to-print, which is a separate installation of pagedjs.<br />
<br />
[[Category:Sysadmin]]</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Upgrading_pagedjs&diff=5526Upgrading pagedjs2026-02-21T14:31:50Z<p>Simoon: </p>
<hr />
<div>Up until today (February 21st, 2026), the version of pagedjs that Octomode depends on is 0.1.43.<br />
<br />
From today, we will upgrade the version to the latest stable version, 0.4.3.<br />
<br />
Octomode depends on two files that should be changed with the upgrade.<br />
<br />
* /opt/octomode/static/paged.polyfill.js (v0.1.43)<br />
* /opt/octomode/static/pagedjs.css (v0.2.0)<br />
<br />
These should be upgraded to <br />
<br />
* /opt/octomode/static/paged.polyfill.js (v0.4.3)<br />
* /opt/octomode/static/interface.css (v0.4)<br />
<br />
The file <code>paged.polyfill.js</code> can be overwritten, but as the CSS has a different filename, we should also update any templates that are being used by Octomode:<br />
<br />
* /opt/octomode/static/templates/pagedjs.html<br />
<br />
== Method ==<br />
<br />
1. go inside <code>/opt/octomode/static/</code><br />
<br />
<syntaxhighlight lang="bash"><br />
$ curl https://unpkg.com/pagedjs@0.4.3/dist/paged.polyfill.js > paged.polyfill.js<br />
$ curl https://gitlab.coko.foundation/pagedjs/interface-polyfill/-/raw/master/interface.css?ref_type=heads > interface.css<br />
</syntaxhighlight><br />
<br />
2. change ownership to the www-data user<br />
<br />
$ chown www-data:www-data paged.polyfill.js<br />
$ chown www-data:www-data interface.css<br />
<br />
3. go inside <code>/opt/octomode/static/templates</code><br />
<br />
<syntaxhighlight lang="bash"><br />
$ sudo nano pagedjs.html<br />
</syntaxhighlight><br />
<br />
Replace the text "pagedjs.css" with "interface.css". Changing it from:<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='pagedjs.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
to<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='interface.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
TODO: upgrade pagedjs for wiki-to-print, which is a separate installation of pagedjs.<br />
<br />
[[Category:Sysadmin]]</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Upgrading_pagedjs&diff=5525Upgrading pagedjs2026-02-21T14:26:32Z<p>Simoon: </p>
<hr />
<div>Up until today (February 21st, 2026), the version of pagedjs that Octomode depends on is 0.1.43.<br />
<br />
From today, we will upgrade the version to the latest stable version, 0.4.3.<br />
<br />
Octomode depends on two files that should be changed with the upgrade.<br />
<br />
* /opt/octomode/static/paged.polyfill.js (v0.1.43)<br />
* /opt/octomode/static/pagedjs.css (v0.2.0)<br />
<br />
These should be upgraded to <br />
<br />
* /opt/octomode/static/paged.polyfill.js (v0.4.3)<br />
* /opt/octomode/static/interface.css (v0.4)<br />
<br />
The file <code>paged.polyfill.js</code> can be overwritten, but as the CSS has a different filename, we should also update any templates that are being used by Octomode:<br />
<br />
* /opt/octomode/static/templates/pagedjs.html<br />
<br />
== Method ==<br />
<br />
1. go inside <code>/opt/octomode/static/</code><br />
<br />
<syntaxhighlight lang="bash"><br />
$ curl https://unpkg.com/pagedjs@0.4.3/dist/paged.polyfill.js > paged.polyfill.js<br />
$ curl https://gitlab.coko.foundation/pagedjs/interface-polyfill/-/raw/master/interface.css?ref_type=heads > interface.css<br />
</syntaxhighlight><br />
<br />
2. change ownership to the www-data user<br />
<br />
$ chown www-data:www-data paged.polyfill.js<br />
$ chown www-data:www-data interface.css<br />
<br />
3. go inside <code>/opt/octomode/static/templates</code><br />
<br />
<syntaxhighlight lang="bash"><br />
$ sudo nano pagedjs.html<br />
</syntaxhighlight><br />
<br />
Replace the text "pagedjs.css" with "interface.css". Changing it from:<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='pagedjs.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
to<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='interface.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
TODO: upgrade pagedjs for wiki-to-print, which is a separate installation of pagedjs.</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Upgrading_pagedjs&diff=5524Upgrading pagedjs2026-02-21T14:14:49Z<p>Simoon: </p>
<hr />
<div>Up until today (February 21st, 2026), the version of pagedjs that Octomode depends on is 0.1.43.<br />
<br />
From today, we will upgrade the version to the latest stable version, 0.4.3.<br />
<br />
Octomode depends on two files that should be changed with the upgrade.<br />
<br />
* /opt/octomode/static/paged.polyfill.js (v0.1.43)<br />
* /opt/octomode/static/pagedjs.css (v0.2.0)<br />
<br />
These should be upgraded to <br />
<br />
* /opt/octomode/static/paged.polyfill.js (v0.4.3)<br />
* /opt/octomode/static/interface.css (v0.4)<br />
<br />
The file <code>paged.polyfill.js</code> can be overwritten, but as the CSS has a different filename, we should also update any templates that are being used by Octomode:<br />
<br />
* /opt/octomode/static/templates/pagedjs.html<br />
<br />
== Method ==<br />
<br />
install curl<br />
switch the the www-data user, which owns the files<br />
<br />
inside <code>/opt/octomode/static/</code><br />
<br />
<syntaxhighlight lang="bash"><br />
$ curl https://app.unpkg.com/pagedjs@0.4.3/files/dist/paged.polyfill.js > paged.polyfill.js<br />
$ curl https://gitlab.coko.foundation/pagedjs/interface-polyfill/-/raw/master/interface.css?ref_type=heads > interface.css<br />
</syntaxhighlight><br />
<br />
inside <code>/opt/octomode/static/templates</code><br />
<br />
<syntaxhighlight lang="bash"><br />
$ sudo nano pagedjs.html<br />
</syntaxhighlight><br />
<br />
Replace the text "pagedjs.css" with "interface.css". Changing it from:<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='pagedjs.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
to<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='interface.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
TODO: upgrade pagedjs for wiki-to-print, which is a separate installation of pagedjs.</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Upgrading_pagedjs&diff=5523Upgrading pagedjs2026-02-21T14:10:21Z<p>Simoon: </p>
<hr />
<div>Up until today (February 21st, 2026), the version of pagedjs that Octomode depends on is 0.1.43.<br />
<br />
From today, we will upgrade the version to the latest stable version, 0.4.3.<br />
<br />
Octomode depends on two files that should be changed with the upgrade.<br />
<br />
* /opt/octomode/static/paged.polyfill.js (v0.1.43)<br />
* /opt/octomode/static/pagedjs.css (v0.2.0)<br />
<br />
These should be upgraded to <br />
<br />
* /opt/octomode/static/paged.polyfill.js (v0.4.3)<br />
* /opt/octomode/static/interface.css (v0.4)<br />
<br />
The file <code>paged.polyfill.js</code> can be overwritten, but as the CSS has a different filename, we should also update any templates that are being used by Octomode:<br />
<br />
* /opt/octomode/static/templates/pagedjs.html<br />
<br />
== Method ==<br />
<br />
inside <code>/opt/octomode/static/</code><br />
<br />
<syntaxhighlight lang="bash"><br />
$ curl https://app.unpkg.com/pagedjs@0.4.3/files/dist/paged.polyfill.js > paged.polyfill.js<br />
$ curl https://gitlab.coko.foundation/pagedjs/interface-polyfill/-/raw/master/interface.css?ref_type=heads > interface.css<br />
</syntaxhighlight><br />
<br />
inside <code>/opt/octomode/static/templates</code><br />
<br />
<syntaxhighlight lang="bash"><br />
$ sudo nano pagedjs.html<br />
</syntaxhighlight><br />
<br />
Replace the text "pagedjs.css" with "interface.css". Changing it from:<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='pagedjs.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
to<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='interface.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
TODO: upgrade pagedjs for wiki-to-print, which is a separate installation of pagedjs.</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Upgrading_pagedjs&diff=5522Upgrading pagedjs2026-02-21T14:10:01Z<p>Simoon: /* Method */</p>
<hr />
<div>Up until today (February 21st, 2026), the version of pagedjs that Octomode depends on is 0.1.43.<br />
<br />
From today, we will upgrade the version to the latest stable version, 0.4.3.<br />
<br />
Octomode depends on two files that should be changed with the upgrade.<br />
<br />
* /opt/octomode/static/pagedjs.polyfill.js (v0.1.43)<br />
* /opt/octomode/static/pagedjs.css (v0.2.0)<br />
<br />
These should be upgraded to <br />
<br />
* /opt/octomode/static/pagedjs.polyfill.js (v0.4.3)<br />
* /opt/octomode/static/interface.css (v0.4)<br />
<br />
The file <code>pagedjs.polyfill.js</code> can be overwritten, but as the CSS has a different filename, we should also update any templates that are being used by Octomode:<br />
<br />
* /opt/octomode/static/templates/pagedjs.html<br />
<br />
== Method ==<br />
<br />
inside <code>/opt/octomode/static/</code><br />
<br />
<syntaxhighlight lang="bash"><br />
$ curl https://app.unpkg.com/pagedjs@0.4.3/files/dist/paged.polyfill.js > paged.polyfill.js<br />
$ curl https://gitlab.coko.foundation/pagedjs/interface-polyfill/-/raw/master/interface.css?ref_type=heads > interface.css<br />
</syntaxhighlight><br />
<br />
inside <code>/opt/octomode/static/templates</code><br />
<br />
<syntaxhighlight lang="bash"><br />
$ sudo nano pagedjs.html<br />
</syntaxhighlight><br />
<br />
Replace the text "pagedjs.css" with "interface.css". Changing it from:<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='pagedjs.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
to<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='interface.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
TODO: upgrade pagedjs for wiki-to-print, which is a separate installation of pagedjs.</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Upgrading_pagedjs&diff=5521Upgrading pagedjs2026-02-21T14:06:35Z<p>Simoon: /* Method */</p>
<hr />
<div>Up until today (February 21st, 2026), the version of pagedjs that Octomode depends on is 0.1.43.<br />
<br />
From today, we will upgrade the version to the latest stable version, 0.4.3.<br />
<br />
Octomode depends on two files that should be changed with the upgrade.<br />
<br />
* /opt/octomode/static/pagedjs.polyfill.js (v0.1.43)<br />
* /opt/octomode/static/pagedjs.css (v0.2.0)<br />
<br />
These should be upgraded to <br />
<br />
* /opt/octomode/static/pagedjs.polyfill.js (v0.4.3)<br />
* /opt/octomode/static/interface.css (v0.4)<br />
<br />
The file <code>pagedjs.polyfill.js</code> can be overwritten, but as the CSS has a different filename, we should also update any templates that are being used by Octomode:<br />
<br />
* /opt/octomode/static/templates/pagedjs.html<br />
<br />
== Method ==<br />
<br />
inside <code>/opt/octomode/static/</code><br />
<br />
<syntaxhighlight lang="bash"><br />
$ curl https://app.unpkg.com/pagedjs@0.4.3/files/dist/paged.polyfill.js > pagedjs.polyfill.js<br />
$ curl https://gitlab.coko.foundation/pagedjs/interface-polyfill/-/raw/master/interface.css?ref_type=heads > interface.css<br />
</syntaxhighlight><br />
<br />
inside <code>/opt/octomode/static/templates</code><br />
<br />
<syntaxhighlight lang="bash"><br />
$ sudo nano pagedjs.html<br />
</syntaxhighlight><br />
<br />
Replace the text "pagedjs.css" with "interface.css". Changing it from:<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='pagedjs.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
to<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='interface.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
TODO: upgrade pagedjs for wiki-to-print, which is a separate installation of pagedjs.</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Upgrading_pagedjs&diff=5520Upgrading pagedjs2026-02-21T14:06:14Z<p>Simoon: /* Method */</p>
<hr />
<div>Up until today (February 21st, 2026), the version of pagedjs that Octomode depends on is 0.1.43.<br />
<br />
From today, we will upgrade the version to the latest stable version, 0.4.3.<br />
<br />
Octomode depends on two files that should be changed with the upgrade.<br />
<br />
* /opt/octomode/static/pagedjs.polyfill.js (v0.1.43)<br />
* /opt/octomode/static/pagedjs.css (v0.2.0)<br />
<br />
These should be upgraded to <br />
<br />
* /opt/octomode/static/pagedjs.polyfill.js (v0.4.3)<br />
* /opt/octomode/static/interface.css (v0.4)<br />
<br />
The file <code>pagedjs.polyfill.js</code> can be overwritten, but as the CSS has a different filename, we should also update any templates that are being used by Octomode:<br />
<br />
* /opt/octomode/static/templates/pagedjs.html<br />
<br />
== Method ==<br />
<br />
inside <code>/opt/octomode/static/</code><br />
<br />
<syntaxhighlight lang="bash" line><br />
$ curl https://app.unpkg.com/pagedjs@0.4.3/files/dist/paged.polyfill.js > pagedjs.polyfill.js<br />
$ curl https://gitlab.coko.foundation/pagedjs/interface-polyfill/-/raw/master/interface.css?ref_type=heads > interface.css<br />
</syntaxhighlight><br />
<br />
inside <code>/opt/octomode/static/templates</code><br />
<br />
<syntaxhighlight lang="python" line><br />
$ sudo nano pagedjs.html<br />
</syntaxhighlight><br />
<br />
Replace the text "pagedjs.css" with "interface.css". Changing it from:<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='pagedjs.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
to<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='interface.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
TODO: upgrade pagedjs for wiki-to-print, which is a separate installation of pagedjs.</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Upgrading_pagedjs&diff=5519Upgrading pagedjs2026-02-21T14:05:27Z<p>Simoon: </p>
<hr />
<div>Up until today (February 21st, 2026), the version of pagedjs that Octomode depends on is 0.1.43.<br />
<br />
From today, we will upgrade the version to the latest stable version, 0.4.3.<br />
<br />
Octomode depends on two files that should be changed with the upgrade.<br />
<br />
* /opt/octomode/static/pagedjs.polyfill.js (v0.1.43)<br />
* /opt/octomode/static/pagedjs.css (v0.2.0)<br />
<br />
These should be upgraded to <br />
<br />
* /opt/octomode/static/pagedjs.polyfill.js (v0.4.3)<br />
* /opt/octomode/static/interface.css (v0.4)<br />
<br />
The file <code>pagedjs.polyfill.js</code> can be overwritten, but as the CSS has a different filename, we should also update any templates that are being used by Octomode:<br />
<br />
* /opt/octomode/static/templates/pagedjs.html<br />
<br />
== Method ==<br />
<br />
inside <code>/opt/octomode/static/</code><br />
<br />
$ curl https://app.unpkg.com/pagedjs@0.4.3/files/dist/paged.polyfill.js > pagedjs.polyfill.js<br />
$ curl https://gitlab.coko.foundation/pagedjs/interface-polyfill/-/raw/master/interface.css?ref_type=heads > interface.css<br />
<br />
inside <code>/opt/octomode/static/templates</code><br />
<br />
$ sudo nano pagedjs.html<br />
<br />
Replace the text "pagedjs.css" with "interface.css". Changing it from:<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='pagedjs.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
to<br />
<br />
<syntaxhighlight lang="html" line><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='interface.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</syntaxhighlight><br />
<br />
TODO: upgrade pagedjs for wiki-to-print, which is a separate installation of pagedjs.</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Upgrading_pagedjs&diff=5518Upgrading pagedjs2026-02-21T14:04:10Z<p>Simoon: /* Method */</p>
<hr />
<div>Up until today (February 21st, 2026), the version of pagedjs that Octomode depends on is 0.1.43.<br />
<br />
From today, we will upgrade the version to the latest stable version, 0.4.3.<br />
<br />
Octomode depends on two files that should be changed with the upgrade.<br />
<br />
* /opt/octomode/static/pagedjs.polyfill.js (v0.1.43)<br />
* /opt/octomode/static/pagedjs.css (v0.2.0)<br />
<br />
These should be upgraded to <br />
<br />
* /opt/octomode/static/pagedjs.polyfill.js (v0.4.3)<br />
* /opt/octomode/static/interface.css (v0.4)<br />
<br />
The file <code>pagedjs.polyfill.js</code> can be overwritten, but as the CSS has a different filename, we should also update any templates that are being used by Octomode:<br />
<br />
* /opt/octomode/static/templates/pagedjs.html<br />
<br />
== Method ==<br />
<br />
inside <code>/opt/octomode/static/</code><br />
<br />
$ curl https://app.unpkg.com/pagedjs@0.4.3/files/dist/paged.polyfill.js > pagedjs.polyfill.js<br />
$ curl https://gitlab.coko.foundation/pagedjs/interface-polyfill/-/raw/master/interface.css?ref_type=heads > interface.css<br />
<br />
inside <code>/opt/octomode/static/templates</code><br />
<br />
$ sudo nano pagedjs.html<br />
<br />
Replace the text "pagedjs.css" with "interface.css". Changing it from:<br />
<br />
<code><br />
<nowiki><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='pagedjs.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</nowiki><br />
</code><br />
<br />
to<br />
<br />
<code><br />
<nowiki><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='interface.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</nowiki><br />
</code><br />
<br />
TODO: upgrade pagedjs for wiki-to-print, which is a separate installation of pagedjs.</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Upgrading_pagedjs&diff=5517Upgrading pagedjs2026-02-21T14:03:25Z<p>Simoon: Created page with "Up until today (February 21st, 2026), the version of pagedjs that Octomode depends on is 0.1.43. From today, we will upgrade the version to the latest stable version, 0.4.3. Octomode depends on two files that should be changed with the upgrade. * /opt/octomode/static/pagedjs.polyfill.js (v0.1.43) * /opt/octomode/static/pagedjs.css (v0.2.0) These should be upgraded to * /opt/octomode/static/pagedjs.polyfill.js (v0.4.3) * /opt/octomode/static/interface.css (v0.4) Th..."</p>
<hr />
<div>Up until today (February 21st, 2026), the version of pagedjs that Octomode depends on is 0.1.43.<br />
<br />
From today, we will upgrade the version to the latest stable version, 0.4.3.<br />
<br />
Octomode depends on two files that should be changed with the upgrade.<br />
<br />
* /opt/octomode/static/pagedjs.polyfill.js (v0.1.43)<br />
* /opt/octomode/static/pagedjs.css (v0.2.0)<br />
<br />
These should be upgraded to <br />
<br />
* /opt/octomode/static/pagedjs.polyfill.js (v0.4.3)<br />
* /opt/octomode/static/interface.css (v0.4)<br />
<br />
The file <code>pagedjs.polyfill.js</code> can be overwritten, but as the CSS has a different filename, we should also update any templates that are being used by Octomode:<br />
<br />
* /opt/octomode/static/templates/pagedjs.html<br />
<br />
== Method ==<br />
<br />
inside <code>/opt/octomode/static/</code><br />
<br />
$ curl https://app.unpkg.com/pagedjs@0.4.3/files/dist/paged.polyfill.js > pagedjs.polyfill.js<br />
$ curl https://gitlab.coko.foundation/pagedjs/interface-polyfill/-/raw/master/interface.css?ref_type=heads > interface.css<br />
<br />
inside <code>/opt/octomode/static/templates</code><br />
<br />
$ sudo nano pagedjs.html<br />
<br />
Replace the text "pagedjs.css" with "interface.css". Changing it from:<br />
<br />
<code><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='pagedjs.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</code><br />
<br />
to<br />
<br />
<code><br />
<!DOCTYPE html><br />
<html lang="{{ lang }}"><br />
<head><br />
<meta charset="utf-8"><br />
<meta name="viewport" content="width=device-width, initial-scale=1.0"><br />
<script src="{{ url_for('static', filename='paged.polyfill.js') }}" type="text/javascript"></script><br />
<link href="{{ url_for('static', filename='interface.css') }}" rel="stylesheet" type="text/css" media="screen"><br />
<!-- [LOCAL HACK] mb: added /octomode/ below to make the stylesheet link work again. --><br />
<link href="/octomode/{{ name }}/stylesheet.css" rel="stylesheet" type="text/css" media="print"><br />
<title>{{ title }}</title><br />
</head><br />
<body><br />
{{ pad_content }}<br />
</body><br />
</html><br />
</code><br />
<br />
TODO: upgrade pagedjs for wiki-to-print, which is a separate installation of pagedjs.</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Error_log&diff=5516Error log2026-02-13T10:53:05Z<p>Simoon: /* Left-justifying a last line in a full justified paragraph */</p>
<hr />
<div>This page documents (some of) the quirks of using free/libre open-source software to make graphic design ''in Octomode''.<br />
<br />
These are all Paged.js related atm.<br />
<br />
== Left-justifying a last line in a full justified paragraph ==<br />
<br />
=== the problem ===<br />
At OSP we (Simon & Clara) are designing a novel in Octomode. The text is full justified throughout, with text indentations before each paragraph, and a mix of line breaks and paragraph breaks. But the last sentence of the paragraph is also full justified, because there is a <nowiki><br></nowiki> that makes the paragraph break. You could drive a truck through those word spaces.<br />
<br />
[[File:you-could-drive-a-truck-through-those-wordspaces.png|thumb|400px|Last line is also full justified :sadface:]]<br />
<br />
=== the solution ===<br />
Lazy method: add a whole heap of non-breaking spaces into the content<nowiki>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</nowiki><br />
<br />
[[File:non-breaking-spaces-hack.png|thumb|400px|packing a bunch of non-breaking spaces]]<br />
<br />
=== the result ===<br />
Voila! The last line is now left-justified. There must be a more elegant way to do this, but we go to print in 2 days (!)<br />
<br />
[[File:last-line-full-justified.png|thumb|400px|hackity hack works!]]<br />
<br />
== An unexpected column jump ==<br />
[[File:firefox-image-cutoff.png|thumb|Images cut off in PDF exported from Firefox]]<br />
[[File:column-jump-issue.png|thumb|The automagical column jump]]<br />
<br />
=== The situation ===<br />
The intention was to make a multi-page report, which has a cover page and text flowing across two columns, beginning on page 2. The document was made using the Firefox browser over the course of a week or so. Everything looked great, until the PDF was exported, which showed images breaking across columns. Strange, as this was not how it appeared in the PDF as it was rendered in the browser.<br />
<br />
So, the switch was made to Chrome, which was recommended as a more stable browser to work with. But in Chrome, there was an entirely different issue. On page 2, the text did not flow across two columns. Instead, it jumped from the left-hand column on page 2, to page 3.<br />
<br />
=== Inspecting... ===<br />
In the CSS, the property and values <code>columns: 2 auto;</code> were previously applied to a class called <code>.columns</code>. In the pad, this class had also been added on page 2, like so: <br />
<br />
<section class="columns"><br />
<br />
When inspecting the elements, it appeared that the <code><section></code> tag had been closed at the end of the first column automagically. So, the text did not flow to the second column, as the browser thought this was the end of the section?<br />
<br />
=== Resolution ===<br />
After much searching online, gnashing of teeth and hand-wringing, the issue was solved by adding <code><section class="columns"></code> to the cover (page 1), then a bunch of break tags: <pre><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/></pre><br />
<br />
This pushed the text down to page 2, where it flowed across both columns, as originally intended.<br />
<br />
<br />
== Disappearing sentences ==<br />
<br />
Since OSP has been working on [http://diversions.constantvzw.org/ DiVersions] in 2020, which is made with Paged.js, stories of disappearing sentences on page breaks have been circulating in the web-to-print networks-of-networks. It also emerged in the context of making [https://volumetricregimes.xyz/index.php?title=Main_Page Volumetric Regimes]. <br />
<br />
Below is a log of messages and exchanges on the Mattermost instance of Coko around this issue. <br />
<br />
<blockquote>'''m---b''': Hey all, hope you are well! A couple of months ago i have been hanging around here (or actually in the other chat instance before the move to this one) to learn about paged.js as i was working on a 300+ pages book. It has been my first bigger project made with paged.js and it has been an amazing learning curve! The making of the book has been on hold for a while and i’m picking it up again these days, but unfortunately a mysterious problem suddenly appeared again: sentences are “eaten” and thus disappearing at the bottom of pages. I had bumped into this in the very beginning of the project too, and @julien was so nice to talk me through possible things that could have caused it. We talked about documenting this in some way, as i have heard stories of designers around me who also bumped into this and said how much anxiety it gives them to not understand when or why sentences disappear. Specially when they work with deadlines, this can easily create all-nighters to make sure that a PDF can be send to print on time. We did not find the time to talk and document it at the end of 2021, but since i’m bumping into this problem again now, and it feels interesting and relevant to document this, i was wondering if @julien or someone else would be up for a short conversation somewhere next week to chat about it?<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': About the missing sentence in the 342 pages book (Volumetric Regimes): <br />
<br />
* i checked the zoom, the browser is at 100% <br />
* all my sizes are in px, including the baseline and top and bottom margins of the page, to avoid the rounding issue <br />
* when i turn Hyphenology off, the issue disappears<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': I tried again to tweak the page margins, but without success. If i make them smaller, the missing line reappears, but … the next one is missing.<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': I feel quite desperate now… don’t know what to do anymore, the “hack” of this afternoon (working with the CTRL+S saved copy) messes up the text flow, … which leaves me out of options to try other things or find other hack-ish ways to send this file to print :slightly_frowning_face:<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': It turns out that without Hyphenology everything is oke, but we need Hyphenology for the hyphenation of the book… Did you encounter this missing sentences bug before by any chance, in combination with Hyphenology? Is there anything i can do?<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': Meanwhile…. i am back at my 342 pages book project, we are sending it to print, but unfortunately the missing sentences bug reappeared……<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': Hey Julien, hope you are well! I wanted to let you know that the missing sentences problem strangely enough suddenly disappeared again. The PDF renders oke now, and i’m crossing fingers for it to stay like this!<br />
</blockquote><br />
<br />
<blockquote><br />
'''m---b''': Hello all! I'm writing with a question around the mystery of sentences disappearing on page breaks... It appeared again, while making a 1st of May anarchist newspaper in Varia. I'm not working on it myself, but it made me curious to check in here and ask what the current status is around these haunting moments? <br />
<br />
'''julien''': hey there. i think we had some interesting experiments with @harshna, it seems that when you have some element with a subpixel height, the rounding/conversion seems to break things. Do you have anything set using em? to explain quickly: on screen, chrome will consider that 8.8px is equal to 8px (6pt). but when it puts the same content on the paper, it consider that 8.8px = 6.6pt. The amount of content it can add on screen is a bit different than what you have on paper. But since paged,js already made the break between pages. the content moves a little bit. <br />
<br />
I have an idea to test later with @harshna so we could come with a more usable solution (i hope)<br />
<br />
'''m---b''': Thanks so much for the reply, will forward this to the others at Varia who were making the newspaper! And would you recommend to work in pixels or in points? I think I asked you this before... but i can't find my notes back :confused:...<br />
<br />
'''julien''': pixel. because the screen is used to draw the pages first. (we’re exploring options to change a bit how pagedjs do the conversion but it’s not really that simple)<br />
</blockquote><br />
<br />
<blockquote><br />
'''decentral1se''': Hmmmm, yeh, it doesn't seem to be working. I'm only working with px now across the entire stylesheet<br />
<br />
'''decentral1se''': things are getting dissapeared on the page breaks between columns (image 1: pdf view image 2: print preview) <br />
<br />
[[File:Missing-sentences-decentral1se-1.png|300px]] [[File:Missing-sentences-decentral1se-2.png|300px]]<br />
<br />
'''decentral1se''': there is also a report about 2 column layout doing strange things so i might try 3 column layout :thinking_face: <br />
<br />
'''harshna''': I agree its still breaking in some places. Its not only about 2 column layout, we tried with single column layout and it has missing lines too. We are working on a fix for that now.<br />
<br />
'''decentral1se''': aha ok, cool! thanks for the efforts :star2: <br />
<br />
'''decentral1se''': happy to test stuff if that helps<br />
<br />
'''harshna''': it would be great if you could report abnormalities/ any patterns that you find<br />
<br />
'''decentral1se''': thank you<br />
</blockquote><br />
<br />
<blockquote><br />
'''julien''': @decentral1se do you have any footnotes?<br />
<br />
we may have found a way to hack our way out of those weird rounding issues.<br />
<br />
by adding and then removing some emtpy space.<br />
<br />
(a hack,really}<br />
<br />
'''decentral1se''': no footnotes, some text in @page:first { @top-left { content: "..."; ... and page numbers tho. Everythings in https://octomode.vvvvvvaria.org/anarcho-krant-mvp-issue-1/stylesheet/ (DM me for username/password).<br />
<br />
'''decentral1se''': curious about the hack :nerd_face: <br />
<br />
'''julien''': ok so, the idea is to leverage the footnote space by giving it some empty space, and run a hook to remove that space just before printing.<br />
<br />
really, a hack<br />
<br />
<pre><br />
class fixMissingLine extends Paged.Handler {<br />
constructor(chunker, polisher, caller) {<br />
super(chunker, polisher, caller);<br />
this.moveToParentFig = [];<br />
}<br />
afterRendered(pages) {<br />
document.querySelectorAll('.pagedjs_sheet').forEach(sheet => sheet.style.setProperty('--pagedjs-footnotes-height', '0px'))<br />
}<br />
}<br />
Paged.registerHandlers(fixMissingLine);<br />
<br />
and add to your css:<br />
.pagedjs_sheet {<br />
--pagedjs-footnotes-height: 12px<br />
}<br />
</pre><br />
<br />
i hope the children never learn we did such a trick.<br />
<br />
'''decentral1se''': it's hacks all the way down :smile_cat: <br />
<br />
i will see about integrating this into octomode to test<br />
<br />
have you had some luck testing this already? <br />
<br />
oh hmm if i don't already have footnotes, then i can't use this? :thinking_face: <br />
<br />
'''julien''': yep you can <br />
<br />
and yes we tried.<br />
<br />
it’s completely untested and quite dangerous but hey, who wants to live a long and nice and peaceful life right? :sunglasses: <br />
<br />
'''decentral1se''': haha lovely stuff, will try tmoz, thx!<br />
</blockquote><br />
===Links===<br />
<br />
* https://git.vvvvvvaria.org/varia/octomode/issues/25<br />
* https://github.com/pagedjs/pagedjs/issues/130<br />
* https://github.com/pagedjs/pagedjs/issues/87<br />
* https://github.com/pagedjs/pagedjs/issues/87#issuecomment-1476958035<br />
<br />
==Differences in PDF renderings in Mac/Linux==<br />
<br />
https://mattermost.coko.foundation/coko/pl/6jdgxiybridq5bg4scx63tirgh<br />
<br />
[[File:Screenshot-page-77-78-mb.png|thumb|right|screenshot on Linux]] <br />
[[File:Screenshot-page-77-78-simon-sm.png|thumb|right|screenshot on Mac]]<br />
<br />
<blockquote><br />
'''m---b''': Hey all! Hope you are having a lovely summer. @simoon and i're slowly picking up work again in Rotterdam and are wrapping up a remake of the APRJA journal, which is now produced with Paged.js. :wink:<br />
<br />
While going to the list of last changes, we noticed that Paged.js renders the pages differently on a Mac and Linux computer, even though we are on the exact same version of Chrome :grimacing:.<br />
Have you noticed that before? Is there anything we can do?<br />
</blockquote><br />
<br />
<blockquote><br />
'''julien''': hey there!<br />
yeah it’s one of those thing we can’t really do anything about because it’s about mac and linux use their fonts.<br />
<br />
so for example. hypens have been available on mac for much longer than for linux :confused:<br />
<br />
The only workaround is by using pagedjs-cli on a server, which comes with the problem of having a hardest time to make small changes.<br />
</blockquote></div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Error_log&diff=5515Error log2026-02-13T10:29:58Z<p>Simoon: /* Left-justifying a last line in a full justified paragraph */</p>
<hr />
<div>This page documents (some of) the quirks of using free/libre open-source software to make graphic design ''in Octomode''.<br />
<br />
These are all Paged.js related atm.<br />
<br />
== Left-justifying a last line in a full justified paragraph ==<br />
<br />
=== the problem ===<br />
The text is full justified throughout, with text indentations before each paragraph, and a mix of line breaks and paragraph breaks. But the last sentence of the paragraph is also full justified, because there is a <nowiki><br></nowiki> that makes the paragraph break. You could drive a truck through those word spaces.<br />
<br />
[[File:you-could-drive-a-truck-through-those-wordspaces.png|thumb|400px|Last line is also full justified :sadface:]]<br />
<br />
=== the solution ===<br />
Lazy method: add a whole heap of non-breaking spaces into the content<nowiki>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</nowiki><br />
<br />
[[File:non-breaking-spaces-hack.png|thumb|400px|packing a bunch of non-breaking spaces]]<br />
<br />
=== the result ===<br />
Voila! The last line is now left-justified. There must be a more elegant way to do this, but we go to print in 2 days (!)<br />
<br />
[[File:last-line-full-justified.png|thumb|400px|hackity hack works!]]<br />
<br />
== An unexpected column jump ==<br />
[[File:firefox-image-cutoff.png|thumb|Images cut off in PDF exported from Firefox]]<br />
[[File:column-jump-issue.png|thumb|The automagical column jump]]<br />
<br />
=== The situation ===<br />
The intention was to make a multi-page report, which has a cover page and text flowing across two columns, beginning on page 2. The document was made using the Firefox browser over the course of a week or so. Everything looked great, until the PDF was exported, which showed images breaking across columns. Strange, as this was not how it appeared in the PDF as it was rendered in the browser.<br />
<br />
So, the switch was made to Chrome, which was recommended as a more stable browser to work with. But in Chrome, there was an entirely different issue. On page 2, the text did not flow across two columns. Instead, it jumped from the left-hand column on page 2, to page 3.<br />
<br />
=== Inspecting... ===<br />
In the CSS, the property and values <code>columns: 2 auto;</code> were previously applied to a class called <code>.columns</code>. In the pad, this class had also been added on page 2, like so: <br />
<br />
<section class="columns"><br />
<br />
When inspecting the elements, it appeared that the <code><section></code> tag had been closed at the end of the first column automagically. So, the text did not flow to the second column, as the browser thought this was the end of the section?<br />
<br />
=== Resolution ===<br />
After much searching online, gnashing of teeth and hand-wringing, the issue was solved by adding <code><section class="columns"></code> to the cover (page 1), then a bunch of break tags: <pre><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/></pre><br />
<br />
This pushed the text down to page 2, where it flowed across both columns, as originally intended.<br />
<br />
<br />
== Disappearing sentences ==<br />
<br />
Since OSP has been working on [http://diversions.constantvzw.org/ DiVersions] in 2020, which is made with Paged.js, stories of disappearing sentences on page breaks have been circulating in the web-to-print networks-of-networks. It also emerged in the context of making [https://volumetricregimes.xyz/index.php?title=Main_Page Volumetric Regimes]. <br />
<br />
Below is a log of messages and exchanges on the Mattermost instance of Coko around this issue. <br />
<br />
<blockquote>'''m---b''': Hey all, hope you are well! A couple of months ago i have been hanging around here (or actually in the other chat instance before the move to this one) to learn about paged.js as i was working on a 300+ pages book. It has been my first bigger project made with paged.js and it has been an amazing learning curve! The making of the book has been on hold for a while and i’m picking it up again these days, but unfortunately a mysterious problem suddenly appeared again: sentences are “eaten” and thus disappearing at the bottom of pages. I had bumped into this in the very beginning of the project too, and @julien was so nice to talk me through possible things that could have caused it. We talked about documenting this in some way, as i have heard stories of designers around me who also bumped into this and said how much anxiety it gives them to not understand when or why sentences disappear. Specially when they work with deadlines, this can easily create all-nighters to make sure that a PDF can be send to print on time. We did not find the time to talk and document it at the end of 2021, but since i’m bumping into this problem again now, and it feels interesting and relevant to document this, i was wondering if @julien or someone else would be up for a short conversation somewhere next week to chat about it?<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': About the missing sentence in the 342 pages book (Volumetric Regimes): <br />
<br />
* i checked the zoom, the browser is at 100% <br />
* all my sizes are in px, including the baseline and top and bottom margins of the page, to avoid the rounding issue <br />
* when i turn Hyphenology off, the issue disappears<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': I tried again to tweak the page margins, but without success. If i make them smaller, the missing line reappears, but … the next one is missing.<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': I feel quite desperate now… don’t know what to do anymore, the “hack” of this afternoon (working with the CTRL+S saved copy) messes up the text flow, … which leaves me out of options to try other things or find other hack-ish ways to send this file to print :slightly_frowning_face:<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': It turns out that without Hyphenology everything is oke, but we need Hyphenology for the hyphenation of the book… Did you encounter this missing sentences bug before by any chance, in combination with Hyphenology? Is there anything i can do?<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': Meanwhile…. i am back at my 342 pages book project, we are sending it to print, but unfortunately the missing sentences bug reappeared……<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': Hey Julien, hope you are well! I wanted to let you know that the missing sentences problem strangely enough suddenly disappeared again. The PDF renders oke now, and i’m crossing fingers for it to stay like this!<br />
</blockquote><br />
<br />
<blockquote><br />
'''m---b''': Hello all! I'm writing with a question around the mystery of sentences disappearing on page breaks... It appeared again, while making a 1st of May anarchist newspaper in Varia. I'm not working on it myself, but it made me curious to check in here and ask what the current status is around these haunting moments? <br />
<br />
'''julien''': hey there. i think we had some interesting experiments with @harshna, it seems that when you have some element with a subpixel height, the rounding/conversion seems to break things. Do you have anything set using em? to explain quickly: on screen, chrome will consider that 8.8px is equal to 8px (6pt). but when it puts the same content on the paper, it consider that 8.8px = 6.6pt. The amount of content it can add on screen is a bit different than what you have on paper. But since paged,js already made the break between pages. the content moves a little bit. <br />
<br />
I have an idea to test later with @harshna so we could come with a more usable solution (i hope)<br />
<br />
'''m---b''': Thanks so much for the reply, will forward this to the others at Varia who were making the newspaper! And would you recommend to work in pixels or in points? I think I asked you this before... but i can't find my notes back :confused:...<br />
<br />
'''julien''': pixel. because the screen is used to draw the pages first. (we’re exploring options to change a bit how pagedjs do the conversion but it’s not really that simple)<br />
</blockquote><br />
<br />
<blockquote><br />
'''decentral1se''': Hmmmm, yeh, it doesn't seem to be working. I'm only working with px now across the entire stylesheet<br />
<br />
'''decentral1se''': things are getting dissapeared on the page breaks between columns (image 1: pdf view image 2: print preview) <br />
<br />
[[File:Missing-sentences-decentral1se-1.png|300px]] [[File:Missing-sentences-decentral1se-2.png|300px]]<br />
<br />
'''decentral1se''': there is also a report about 2 column layout doing strange things so i might try 3 column layout :thinking_face: <br />
<br />
'''harshna''': I agree its still breaking in some places. Its not only about 2 column layout, we tried with single column layout and it has missing lines too. We are working on a fix for that now.<br />
<br />
'''decentral1se''': aha ok, cool! thanks for the efforts :star2: <br />
<br />
'''decentral1se''': happy to test stuff if that helps<br />
<br />
'''harshna''': it would be great if you could report abnormalities/ any patterns that you find<br />
<br />
'''decentral1se''': thank you<br />
</blockquote><br />
<br />
<blockquote><br />
'''julien''': @decentral1se do you have any footnotes?<br />
<br />
we may have found a way to hack our way out of those weird rounding issues.<br />
<br />
by adding and then removing some emtpy space.<br />
<br />
(a hack,really}<br />
<br />
'''decentral1se''': no footnotes, some text in @page:first { @top-left { content: "..."; ... and page numbers tho. Everythings in https://octomode.vvvvvvaria.org/anarcho-krant-mvp-issue-1/stylesheet/ (DM me for username/password).<br />
<br />
'''decentral1se''': curious about the hack :nerd_face: <br />
<br />
'''julien''': ok so, the idea is to leverage the footnote space by giving it some empty space, and run a hook to remove that space just before printing.<br />
<br />
really, a hack<br />
<br />
<pre><br />
class fixMissingLine extends Paged.Handler {<br />
constructor(chunker, polisher, caller) {<br />
super(chunker, polisher, caller);<br />
this.moveToParentFig = [];<br />
}<br />
afterRendered(pages) {<br />
document.querySelectorAll('.pagedjs_sheet').forEach(sheet => sheet.style.setProperty('--pagedjs-footnotes-height', '0px'))<br />
}<br />
}<br />
Paged.registerHandlers(fixMissingLine);<br />
<br />
and add to your css:<br />
.pagedjs_sheet {<br />
--pagedjs-footnotes-height: 12px<br />
}<br />
</pre><br />
<br />
i hope the children never learn we did such a trick.<br />
<br />
'''decentral1se''': it's hacks all the way down :smile_cat: <br />
<br />
i will see about integrating this into octomode to test<br />
<br />
have you had some luck testing this already? <br />
<br />
oh hmm if i don't already have footnotes, then i can't use this? :thinking_face: <br />
<br />
'''julien''': yep you can <br />
<br />
and yes we tried.<br />
<br />
it’s completely untested and quite dangerous but hey, who wants to live a long and nice and peaceful life right? :sunglasses: <br />
<br />
'''decentral1se''': haha lovely stuff, will try tmoz, thx!<br />
</blockquote><br />
===Links===<br />
<br />
* https://git.vvvvvvaria.org/varia/octomode/issues/25<br />
* https://github.com/pagedjs/pagedjs/issues/130<br />
* https://github.com/pagedjs/pagedjs/issues/87<br />
* https://github.com/pagedjs/pagedjs/issues/87#issuecomment-1476958035<br />
<br />
==Differences in PDF renderings in Mac/Linux==<br />
<br />
https://mattermost.coko.foundation/coko/pl/6jdgxiybridq5bg4scx63tirgh<br />
<br />
[[File:Screenshot-page-77-78-mb.png|thumb|right|screenshot on Linux]] <br />
[[File:Screenshot-page-77-78-simon-sm.png|thumb|right|screenshot on Mac]]<br />
<br />
<blockquote><br />
'''m---b''': Hey all! Hope you are having a lovely summer. @simoon and i're slowly picking up work again in Rotterdam and are wrapping up a remake of the APRJA journal, which is now produced with Paged.js. :wink:<br />
<br />
While going to the list of last changes, we noticed that Paged.js renders the pages differently on a Mac and Linux computer, even though we are on the exact same version of Chrome :grimacing:.<br />
Have you noticed that before? Is there anything we can do?<br />
</blockquote><br />
<br />
<blockquote><br />
'''julien''': hey there!<br />
yeah it’s one of those thing we can’t really do anything about because it’s about mac and linux use their fonts.<br />
<br />
so for example. hypens have been available on mac for much longer than for linux :confused:<br />
<br />
The only workaround is by using pagedjs-cli on a server, which comes with the problem of having a hardest time to make small changes.<br />
</blockquote></div>Simoonhttp://cc.practices.tools/wiki/index.php?title=File:Last-line-full-justified.png&diff=5514File:Last-line-full-justified.png2026-02-13T10:27:28Z<p>Simoon: </p>
<hr />
<div></div>Simoonhttp://cc.practices.tools/wiki/index.php?title=File:Non-breaking-spaces-hack.png&diff=5513File:Non-breaking-spaces-hack.png2026-02-13T10:27:09Z<p>Simoon: </p>
<hr />
<div></div>Simoonhttp://cc.practices.tools/wiki/index.php?title=File:You-could-drive-a-truck-through-those-wordspaces.png&diff=5512File:You-could-drive-a-truck-through-those-wordspaces.png2026-02-13T10:26:42Z<p>Simoon: </p>
<hr />
<div></div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Error_log&diff=5511Error log2026-02-13T10:26:20Z<p>Simoon: /* Left-justifying a last line in a full justified paragraph */</p>
<hr />
<div>This page documents (some of) the quirks of using free/libre open-source software to make graphic design ''in Octomode''.<br />
<br />
These are all Paged.js related atm.<br />
<br />
== Left-justifying a last line in a full justified paragraph ==<br />
<br />
=== the problem ===<br />
The text is full justified throughout, with text indentations before each paragraph, and a mix of line breaks and paragraph breaks. But the last sentence of the paragraph is also full justified, because there is a <nowiki><br></nowiki> that makes the paragraph break. You could drive a truck through those word spaces.<br />
<br />
[[File:you-could-drive-a-truck-through-those-wordspaces.png|thumb|Last line is also full justified :sadface:]]<br />
<br />
=== the solution ===<br />
Lazy method: add a whole heap of non-breaking spaces into the content<nowiki>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</nowiki><br />
<br />
[[File:non-breaking-spaces-hack.png|thumb|packing a bunch of non-breaking spaces]]<br />
<br />
=== the result ===<br />
Voila! The last line is now left-justified. There must be a more elegant way to do this, but we go to print in 2 days (!)<br />
<br />
[[File:last-line-full-justified.png|thumb|hackity hack works!]]<br />
<br />
== An unexpected column jump ==<br />
[[File:firefox-image-cutoff.png|thumb|Images cut off in PDF exported from Firefox]]<br />
[[File:column-jump-issue.png|thumb|The automagical column jump]]<br />
<br />
=== The situation ===<br />
The intention was to make a multi-page report, which has a cover page and text flowing across two columns, beginning on page 2. The document was made using the Firefox browser over the course of a week or so. Everything looked great, until the PDF was exported, which showed images breaking across columns. Strange, as this was not how it appeared in the PDF as it was rendered in the browser.<br />
<br />
So, the switch was made to Chrome, which was recommended as a more stable browser to work with. But in Chrome, there was an entirely different issue. On page 2, the text did not flow across two columns. Instead, it jumped from the left-hand column on page 2, to page 3.<br />
<br />
=== Inspecting... ===<br />
In the CSS, the property and values <code>columns: 2 auto;</code> were previously applied to a class called <code>.columns</code>. In the pad, this class had also been added on page 2, like so: <br />
<br />
<section class="columns"><br />
<br />
When inspecting the elements, it appeared that the <code><section></code> tag had been closed at the end of the first column automagically. So, the text did not flow to the second column, as the browser thought this was the end of the section?<br />
<br />
=== Resolution ===<br />
After much searching online, gnashing of teeth and hand-wringing, the issue was solved by adding <code><section class="columns"></code> to the cover (page 1), then a bunch of break tags: <pre><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/></pre><br />
<br />
This pushed the text down to page 2, where it flowed across both columns, as originally intended.<br />
<br />
<br />
== Disappearing sentences ==<br />
<br />
Since OSP has been working on [http://diversions.constantvzw.org/ DiVersions] in 2020, which is made with Paged.js, stories of disappearing sentences on page breaks have been circulating in the web-to-print networks-of-networks. It also emerged in the context of making [https://volumetricregimes.xyz/index.php?title=Main_Page Volumetric Regimes]. <br />
<br />
Below is a log of messages and exchanges on the Mattermost instance of Coko around this issue. <br />
<br />
<blockquote>'''m---b''': Hey all, hope you are well! A couple of months ago i have been hanging around here (or actually in the other chat instance before the move to this one) to learn about paged.js as i was working on a 300+ pages book. It has been my first bigger project made with paged.js and it has been an amazing learning curve! The making of the book has been on hold for a while and i’m picking it up again these days, but unfortunately a mysterious problem suddenly appeared again: sentences are “eaten” and thus disappearing at the bottom of pages. I had bumped into this in the very beginning of the project too, and @julien was so nice to talk me through possible things that could have caused it. We talked about documenting this in some way, as i have heard stories of designers around me who also bumped into this and said how much anxiety it gives them to not understand when or why sentences disappear. Specially when they work with deadlines, this can easily create all-nighters to make sure that a PDF can be send to print on time. We did not find the time to talk and document it at the end of 2021, but since i’m bumping into this problem again now, and it feels interesting and relevant to document this, i was wondering if @julien or someone else would be up for a short conversation somewhere next week to chat about it?<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': About the missing sentence in the 342 pages book (Volumetric Regimes): <br />
<br />
* i checked the zoom, the browser is at 100% <br />
* all my sizes are in px, including the baseline and top and bottom margins of the page, to avoid the rounding issue <br />
* when i turn Hyphenology off, the issue disappears<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': I tried again to tweak the page margins, but without success. If i make them smaller, the missing line reappears, but … the next one is missing.<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': I feel quite desperate now… don’t know what to do anymore, the “hack” of this afternoon (working with the CTRL+S saved copy) messes up the text flow, … which leaves me out of options to try other things or find other hack-ish ways to send this file to print :slightly_frowning_face:<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': It turns out that without Hyphenology everything is oke, but we need Hyphenology for the hyphenation of the book… Did you encounter this missing sentences bug before by any chance, in combination with Hyphenology? Is there anything i can do?<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': Meanwhile…. i am back at my 342 pages book project, we are sending it to print, but unfortunately the missing sentences bug reappeared……<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': Hey Julien, hope you are well! I wanted to let you know that the missing sentences problem strangely enough suddenly disappeared again. The PDF renders oke now, and i’m crossing fingers for it to stay like this!<br />
</blockquote><br />
<br />
<blockquote><br />
'''m---b''': Hello all! I'm writing with a question around the mystery of sentences disappearing on page breaks... It appeared again, while making a 1st of May anarchist newspaper in Varia. I'm not working on it myself, but it made me curious to check in here and ask what the current status is around these haunting moments? <br />
<br />
'''julien''': hey there. i think we had some interesting experiments with @harshna, it seems that when you have some element with a subpixel height, the rounding/conversion seems to break things. Do you have anything set using em? to explain quickly: on screen, chrome will consider that 8.8px is equal to 8px (6pt). but when it puts the same content on the paper, it consider that 8.8px = 6.6pt. The amount of content it can add on screen is a bit different than what you have on paper. But since paged,js already made the break between pages. the content moves a little bit. <br />
<br />
I have an idea to test later with @harshna so we could come with a more usable solution (i hope)<br />
<br />
'''m---b''': Thanks so much for the reply, will forward this to the others at Varia who were making the newspaper! And would you recommend to work in pixels or in points? I think I asked you this before... but i can't find my notes back :confused:...<br />
<br />
'''julien''': pixel. because the screen is used to draw the pages first. (we’re exploring options to change a bit how pagedjs do the conversion but it’s not really that simple)<br />
</blockquote><br />
<br />
<blockquote><br />
'''decentral1se''': Hmmmm, yeh, it doesn't seem to be working. I'm only working with px now across the entire stylesheet<br />
<br />
'''decentral1se''': things are getting dissapeared on the page breaks between columns (image 1: pdf view image 2: print preview) <br />
<br />
[[File:Missing-sentences-decentral1se-1.png|300px]] [[File:Missing-sentences-decentral1se-2.png|300px]]<br />
<br />
'''decentral1se''': there is also a report about 2 column layout doing strange things so i might try 3 column layout :thinking_face: <br />
<br />
'''harshna''': I agree its still breaking in some places. Its not only about 2 column layout, we tried with single column layout and it has missing lines too. We are working on a fix for that now.<br />
<br />
'''decentral1se''': aha ok, cool! thanks for the efforts :star2: <br />
<br />
'''decentral1se''': happy to test stuff if that helps<br />
<br />
'''harshna''': it would be great if you could report abnormalities/ any patterns that you find<br />
<br />
'''decentral1se''': thank you<br />
</blockquote><br />
<br />
<blockquote><br />
'''julien''': @decentral1se do you have any footnotes?<br />
<br />
we may have found a way to hack our way out of those weird rounding issues.<br />
<br />
by adding and then removing some emtpy space.<br />
<br />
(a hack,really}<br />
<br />
'''decentral1se''': no footnotes, some text in @page:first { @top-left { content: "..."; ... and page numbers tho. Everythings in https://octomode.vvvvvvaria.org/anarcho-krant-mvp-issue-1/stylesheet/ (DM me for username/password).<br />
<br />
'''decentral1se''': curious about the hack :nerd_face: <br />
<br />
'''julien''': ok so, the idea is to leverage the footnote space by giving it some empty space, and run a hook to remove that space just before printing.<br />
<br />
really, a hack<br />
<br />
<pre><br />
class fixMissingLine extends Paged.Handler {<br />
constructor(chunker, polisher, caller) {<br />
super(chunker, polisher, caller);<br />
this.moveToParentFig = [];<br />
}<br />
afterRendered(pages) {<br />
document.querySelectorAll('.pagedjs_sheet').forEach(sheet => sheet.style.setProperty('--pagedjs-footnotes-height', '0px'))<br />
}<br />
}<br />
Paged.registerHandlers(fixMissingLine);<br />
<br />
and add to your css:<br />
.pagedjs_sheet {<br />
--pagedjs-footnotes-height: 12px<br />
}<br />
</pre><br />
<br />
i hope the children never learn we did such a trick.<br />
<br />
'''decentral1se''': it's hacks all the way down :smile_cat: <br />
<br />
i will see about integrating this into octomode to test<br />
<br />
have you had some luck testing this already? <br />
<br />
oh hmm if i don't already have footnotes, then i can't use this? :thinking_face: <br />
<br />
'''julien''': yep you can <br />
<br />
and yes we tried.<br />
<br />
it’s completely untested and quite dangerous but hey, who wants to live a long and nice and peaceful life right? :sunglasses: <br />
<br />
'''decentral1se''': haha lovely stuff, will try tmoz, thx!<br />
</blockquote><br />
===Links===<br />
<br />
* https://git.vvvvvvaria.org/varia/octomode/issues/25<br />
* https://github.com/pagedjs/pagedjs/issues/130<br />
* https://github.com/pagedjs/pagedjs/issues/87<br />
* https://github.com/pagedjs/pagedjs/issues/87#issuecomment-1476958035<br />
<br />
==Differences in PDF renderings in Mac/Linux==<br />
<br />
https://mattermost.coko.foundation/coko/pl/6jdgxiybridq5bg4scx63tirgh<br />
<br />
[[File:Screenshot-page-77-78-mb.png|thumb|right|screenshot on Linux]] <br />
[[File:Screenshot-page-77-78-simon-sm.png|thumb|right|screenshot on Mac]]<br />
<br />
<blockquote><br />
'''m---b''': Hey all! Hope you are having a lovely summer. @simoon and i're slowly picking up work again in Rotterdam and are wrapping up a remake of the APRJA journal, which is now produced with Paged.js. :wink:<br />
<br />
While going to the list of last changes, we noticed that Paged.js renders the pages differently on a Mac and Linux computer, even though we are on the exact same version of Chrome :grimacing:.<br />
Have you noticed that before? Is there anything we can do?<br />
</blockquote><br />
<br />
<blockquote><br />
'''julien''': hey there!<br />
yeah it’s one of those thing we can’t really do anything about because it’s about mac and linux use their fonts.<br />
<br />
so for example. hypens have been available on mac for much longer than for linux :confused:<br />
<br />
The only workaround is by using pagedjs-cli on a server, which comes with the problem of having a hardest time to make small changes.<br />
</blockquote></div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Error_log&diff=5510Error log2026-02-13T10:25:33Z<p>Simoon: /* Left-justifying a last line in a full justified paragraph */</p>
<hr />
<div>This page documents (some of) the quirks of using free/libre open-source software to make graphic design ''in Octomode''.<br />
<br />
These are all Paged.js related atm.<br />
<br />
== Left-justifying a last line in a full justified paragraph ==<br />
<br />
=== the problem ===<br />
The text is full justified throughout, with text indentations before each paragraph, and a mix of line breaks and paragraph breaks. But the last sentence of the paragraph is also full justified, because there is a ```<br>``` that makes the paragraph break. You could drive a truck through those word spaces.<br />
<br />
[[File:you-could-drive-a-truck-through-those-wordspaces.png|thumb|Last line is also full justified :sadface:]]<br />
<br />
=== the solution ===<br />
Lazy method: add a whole heap of non-breaking spaces into the content<code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<code><br />
<br />
[[File:non-breaking-spaces-hack.png|thumb|packing a bunch of non-breaking spaces]]<br />
<br />
=== the result ===<br />
Voila! The last line is now left-justified. There must be a more elegant way to do this, but we go to print in 2 days (!)<br />
<br />
[[File:last-line-full-justified.png|thumb|hackity hack works!]]<br />
<br />
== An unexpected column jump ==<br />
[[File:firefox-image-cutoff.png|thumb|Images cut off in PDF exported from Firefox]]<br />
[[File:column-jump-issue.png|thumb|The automagical column jump]]<br />
<br />
=== The situation ===<br />
The intention was to make a multi-page report, which has a cover page and text flowing across two columns, beginning on page 2. The document was made using the Firefox browser over the course of a week or so. Everything looked great, until the PDF was exported, which showed images breaking across columns. Strange, as this was not how it appeared in the PDF as it was rendered in the browser.<br />
<br />
So, the switch was made to Chrome, which was recommended as a more stable browser to work with. But in Chrome, there was an entirely different issue. On page 2, the text did not flow across two columns. Instead, it jumped from the left-hand column on page 2, to page 3.<br />
<br />
=== Inspecting... ===<br />
In the CSS, the property and values <code>columns: 2 auto;</code> were previously applied to a class called <code>.columns</code>. In the pad, this class had also been added on page 2, like so: <br />
<br />
<section class="columns"><br />
<br />
When inspecting the elements, it appeared that the <code><section></code> tag had been closed at the end of the first column automagically. So, the text did not flow to the second column, as the browser thought this was the end of the section?<br />
<br />
=== Resolution ===<br />
After much searching online, gnashing of teeth and hand-wringing, the issue was solved by adding <code><section class="columns"></code> to the cover (page 1), then a bunch of break tags: <pre><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/></pre><br />
<br />
This pushed the text down to page 2, where it flowed across both columns, as originally intended.<br />
<br />
<br />
== Disappearing sentences ==<br />
<br />
Since OSP has been working on [http://diversions.constantvzw.org/ DiVersions] in 2020, which is made with Paged.js, stories of disappearing sentences on page breaks have been circulating in the web-to-print networks-of-networks. It also emerged in the context of making [https://volumetricregimes.xyz/index.php?title=Main_Page Volumetric Regimes]. <br />
<br />
Below is a log of messages and exchanges on the Mattermost instance of Coko around this issue. <br />
<br />
<blockquote>'''m---b''': Hey all, hope you are well! A couple of months ago i have been hanging around here (or actually in the other chat instance before the move to this one) to learn about paged.js as i was working on a 300+ pages book. It has been my first bigger project made with paged.js and it has been an amazing learning curve! The making of the book has been on hold for a while and i’m picking it up again these days, but unfortunately a mysterious problem suddenly appeared again: sentences are “eaten” and thus disappearing at the bottom of pages. I had bumped into this in the very beginning of the project too, and @julien was so nice to talk me through possible things that could have caused it. We talked about documenting this in some way, as i have heard stories of designers around me who also bumped into this and said how much anxiety it gives them to not understand when or why sentences disappear. Specially when they work with deadlines, this can easily create all-nighters to make sure that a PDF can be send to print on time. We did not find the time to talk and document it at the end of 2021, but since i’m bumping into this problem again now, and it feels interesting and relevant to document this, i was wondering if @julien or someone else would be up for a short conversation somewhere next week to chat about it?<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': About the missing sentence in the 342 pages book (Volumetric Regimes): <br />
<br />
* i checked the zoom, the browser is at 100% <br />
* all my sizes are in px, including the baseline and top and bottom margins of the page, to avoid the rounding issue <br />
* when i turn Hyphenology off, the issue disappears<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': I tried again to tweak the page margins, but without success. If i make them smaller, the missing line reappears, but … the next one is missing.<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': I feel quite desperate now… don’t know what to do anymore, the “hack” of this afternoon (working with the CTRL+S saved copy) messes up the text flow, … which leaves me out of options to try other things or find other hack-ish ways to send this file to print :slightly_frowning_face:<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': It turns out that without Hyphenology everything is oke, but we need Hyphenology for the hyphenation of the book… Did you encounter this missing sentences bug before by any chance, in combination with Hyphenology? Is there anything i can do?<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': Meanwhile…. i am back at my 342 pages book project, we are sending it to print, but unfortunately the missing sentences bug reappeared……<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': Hey Julien, hope you are well! I wanted to let you know that the missing sentences problem strangely enough suddenly disappeared again. The PDF renders oke now, and i’m crossing fingers for it to stay like this!<br />
</blockquote><br />
<br />
<blockquote><br />
'''m---b''': Hello all! I'm writing with a question around the mystery of sentences disappearing on page breaks... It appeared again, while making a 1st of May anarchist newspaper in Varia. I'm not working on it myself, but it made me curious to check in here and ask what the current status is around these haunting moments? <br />
<br />
'''julien''': hey there. i think we had some interesting experiments with @harshna, it seems that when you have some element with a subpixel height, the rounding/conversion seems to break things. Do you have anything set using em? to explain quickly: on screen, chrome will consider that 8.8px is equal to 8px (6pt). but when it puts the same content on the paper, it consider that 8.8px = 6.6pt. The amount of content it can add on screen is a bit different than what you have on paper. But since paged,js already made the break between pages. the content moves a little bit. <br />
<br />
I have an idea to test later with @harshna so we could come with a more usable solution (i hope)<br />
<br />
'''m---b''': Thanks so much for the reply, will forward this to the others at Varia who were making the newspaper! And would you recommend to work in pixels or in points? I think I asked you this before... but i can't find my notes back :confused:...<br />
<br />
'''julien''': pixel. because the screen is used to draw the pages first. (we’re exploring options to change a bit how pagedjs do the conversion but it’s not really that simple)<br />
</blockquote><br />
<br />
<blockquote><br />
'''decentral1se''': Hmmmm, yeh, it doesn't seem to be working. I'm only working with px now across the entire stylesheet<br />
<br />
'''decentral1se''': things are getting dissapeared on the page breaks between columns (image 1: pdf view image 2: print preview) <br />
<br />
[[File:Missing-sentences-decentral1se-1.png|300px]] [[File:Missing-sentences-decentral1se-2.png|300px]]<br />
<br />
'''decentral1se''': there is also a report about 2 column layout doing strange things so i might try 3 column layout :thinking_face: <br />
<br />
'''harshna''': I agree its still breaking in some places. Its not only about 2 column layout, we tried with single column layout and it has missing lines too. We are working on a fix for that now.<br />
<br />
'''decentral1se''': aha ok, cool! thanks for the efforts :star2: <br />
<br />
'''decentral1se''': happy to test stuff if that helps<br />
<br />
'''harshna''': it would be great if you could report abnormalities/ any patterns that you find<br />
<br />
'''decentral1se''': thank you<br />
</blockquote><br />
<br />
<blockquote><br />
'''julien''': @decentral1se do you have any footnotes?<br />
<br />
we may have found a way to hack our way out of those weird rounding issues.<br />
<br />
by adding and then removing some emtpy space.<br />
<br />
(a hack,really}<br />
<br />
'''decentral1se''': no footnotes, some text in @page:first { @top-left { content: "..."; ... and page numbers tho. Everythings in https://octomode.vvvvvvaria.org/anarcho-krant-mvp-issue-1/stylesheet/ (DM me for username/password).<br />
<br />
'''decentral1se''': curious about the hack :nerd_face: <br />
<br />
'''julien''': ok so, the idea is to leverage the footnote space by giving it some empty space, and run a hook to remove that space just before printing.<br />
<br />
really, a hack<br />
<br />
<pre><br />
class fixMissingLine extends Paged.Handler {<br />
constructor(chunker, polisher, caller) {<br />
super(chunker, polisher, caller);<br />
this.moveToParentFig = [];<br />
}<br />
afterRendered(pages) {<br />
document.querySelectorAll('.pagedjs_sheet').forEach(sheet => sheet.style.setProperty('--pagedjs-footnotes-height', '0px'))<br />
}<br />
}<br />
Paged.registerHandlers(fixMissingLine);<br />
<br />
and add to your css:<br />
.pagedjs_sheet {<br />
--pagedjs-footnotes-height: 12px<br />
}<br />
</pre><br />
<br />
i hope the children never learn we did such a trick.<br />
<br />
'''decentral1se''': it's hacks all the way down :smile_cat: <br />
<br />
i will see about integrating this into octomode to test<br />
<br />
have you had some luck testing this already? <br />
<br />
oh hmm if i don't already have footnotes, then i can't use this? :thinking_face: <br />
<br />
'''julien''': yep you can <br />
<br />
and yes we tried.<br />
<br />
it’s completely untested and quite dangerous but hey, who wants to live a long and nice and peaceful life right? :sunglasses: <br />
<br />
'''decentral1se''': haha lovely stuff, will try tmoz, thx!<br />
</blockquote><br />
===Links===<br />
<br />
* https://git.vvvvvvaria.org/varia/octomode/issues/25<br />
* https://github.com/pagedjs/pagedjs/issues/130<br />
* https://github.com/pagedjs/pagedjs/issues/87<br />
* https://github.com/pagedjs/pagedjs/issues/87#issuecomment-1476958035<br />
<br />
==Differences in PDF renderings in Mac/Linux==<br />
<br />
https://mattermost.coko.foundation/coko/pl/6jdgxiybridq5bg4scx63tirgh<br />
<br />
[[File:Screenshot-page-77-78-mb.png|thumb|right|screenshot on Linux]] <br />
[[File:Screenshot-page-77-78-simon-sm.png|thumb|right|screenshot on Mac]]<br />
<br />
<blockquote><br />
'''m---b''': Hey all! Hope you are having a lovely summer. @simoon and i're slowly picking up work again in Rotterdam and are wrapping up a remake of the APRJA journal, which is now produced with Paged.js. :wink:<br />
<br />
While going to the list of last changes, we noticed that Paged.js renders the pages differently on a Mac and Linux computer, even though we are on the exact same version of Chrome :grimacing:.<br />
Have you noticed that before? Is there anything we can do?<br />
</blockquote><br />
<br />
<blockquote><br />
'''julien''': hey there!<br />
yeah it’s one of those thing we can’t really do anything about because it’s about mac and linux use their fonts.<br />
<br />
so for example. hypens have been available on mac for much longer than for linux :confused:<br />
<br />
The only workaround is by using pagedjs-cli on a server, which comes with the problem of having a hardest time to make small changes.<br />
</blockquote></div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Error_log&diff=5509Error log2026-02-13T10:25:13Z<p>Simoon: </p>
<hr />
<div>This page documents (some of) the quirks of using free/libre open-source software to make graphic design ''in Octomode''.<br />
<br />
These are all Paged.js related atm.<br />
<br />
== Left-justifying a last line in a full justified paragraph ==<br />
<br />
=== the problem ===<br />
The text is full justified throughout, with text indentations before each paragraph, and a mix of line breaks and paragraph breaks. But the last sentence of the paragraph is also full justified, because there is a ```<br>``` that makes the paragraph break. You could drive a truck through those word spaces.<br />
[[File:you-could-drive-a-truck-through-those-wordspaces.png|thumb|Last line is also full justified :sadface:]]<br />
<br />
=== the solution ===<br />
Lazy method: add a whole heap of non-breaking spaces into the content<code>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<code><br />
[[File:non-breaking-spaces-hack.png|thumb|packing a bunch of non-breaking spaces]]<br />
<br />
=== the result ===<br />
Voila! The last line is now left-justified. There must be a more elegant way to do this, but we go to print in 2 days (!)<br />
[[File:last-line-full-justified.png|thumb|hackity hack works!]]<br />
<br />
== An unexpected column jump ==<br />
[[File:firefox-image-cutoff.png|thumb|Images cut off in PDF exported from Firefox]]<br />
[[File:column-jump-issue.png|thumb|The automagical column jump]]<br />
<br />
=== The situation ===<br />
The intention was to make a multi-page report, which has a cover page and text flowing across two columns, beginning on page 2. The document was made using the Firefox browser over the course of a week or so. Everything looked great, until the PDF was exported, which showed images breaking across columns. Strange, as this was not how it appeared in the PDF as it was rendered in the browser.<br />
<br />
So, the switch was made to Chrome, which was recommended as a more stable browser to work with. But in Chrome, there was an entirely different issue. On page 2, the text did not flow across two columns. Instead, it jumped from the left-hand column on page 2, to page 3.<br />
<br />
=== Inspecting... ===<br />
In the CSS, the property and values <code>columns: 2 auto;</code> were previously applied to a class called <code>.columns</code>. In the pad, this class had also been added on page 2, like so: <br />
<br />
<section class="columns"><br />
<br />
When inspecting the elements, it appeared that the <code><section></code> tag had been closed at the end of the first column automagically. So, the text did not flow to the second column, as the browser thought this was the end of the section?<br />
<br />
=== Resolution ===<br />
After much searching online, gnashing of teeth and hand-wringing, the issue was solved by adding <code><section class="columns"></code> to the cover (page 1), then a bunch of break tags: <pre><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/></pre><br />
<br />
This pushed the text down to page 2, where it flowed across both columns, as originally intended.<br />
<br />
<br />
== Disappearing sentences ==<br />
<br />
Since OSP has been working on [http://diversions.constantvzw.org/ DiVersions] in 2020, which is made with Paged.js, stories of disappearing sentences on page breaks have been circulating in the web-to-print networks-of-networks. It also emerged in the context of making [https://volumetricregimes.xyz/index.php?title=Main_Page Volumetric Regimes]. <br />
<br />
Below is a log of messages and exchanges on the Mattermost instance of Coko around this issue. <br />
<br />
<blockquote>'''m---b''': Hey all, hope you are well! A couple of months ago i have been hanging around here (or actually in the other chat instance before the move to this one) to learn about paged.js as i was working on a 300+ pages book. It has been my first bigger project made with paged.js and it has been an amazing learning curve! The making of the book has been on hold for a while and i’m picking it up again these days, but unfortunately a mysterious problem suddenly appeared again: sentences are “eaten” and thus disappearing at the bottom of pages. I had bumped into this in the very beginning of the project too, and @julien was so nice to talk me through possible things that could have caused it. We talked about documenting this in some way, as i have heard stories of designers around me who also bumped into this and said how much anxiety it gives them to not understand when or why sentences disappear. Specially when they work with deadlines, this can easily create all-nighters to make sure that a PDF can be send to print on time. We did not find the time to talk and document it at the end of 2021, but since i’m bumping into this problem again now, and it feels interesting and relevant to document this, i was wondering if @julien or someone else would be up for a short conversation somewhere next week to chat about it?<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': About the missing sentence in the 342 pages book (Volumetric Regimes): <br />
<br />
* i checked the zoom, the browser is at 100% <br />
* all my sizes are in px, including the baseline and top and bottom margins of the page, to avoid the rounding issue <br />
* when i turn Hyphenology off, the issue disappears<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': I tried again to tweak the page margins, but without success. If i make them smaller, the missing line reappears, but … the next one is missing.<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': I feel quite desperate now… don’t know what to do anymore, the “hack” of this afternoon (working with the CTRL+S saved copy) messes up the text flow, … which leaves me out of options to try other things or find other hack-ish ways to send this file to print :slightly_frowning_face:<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': It turns out that without Hyphenology everything is oke, but we need Hyphenology for the hyphenation of the book… Did you encounter this missing sentences bug before by any chance, in combination with Hyphenology? Is there anything i can do?<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': Meanwhile…. i am back at my 342 pages book project, we are sending it to print, but unfortunately the missing sentences bug reappeared……<br />
</blockquote><br />
<br />
<blockquote>'''m---b''': Hey Julien, hope you are well! I wanted to let you know that the missing sentences problem strangely enough suddenly disappeared again. The PDF renders oke now, and i’m crossing fingers for it to stay like this!<br />
</blockquote><br />
<br />
<blockquote><br />
'''m---b''': Hello all! I'm writing with a question around the mystery of sentences disappearing on page breaks... It appeared again, while making a 1st of May anarchist newspaper in Varia. I'm not working on it myself, but it made me curious to check in here and ask what the current status is around these haunting moments? <br />
<br />
'''julien''': hey there. i think we had some interesting experiments with @harshna, it seems that when you have some element with a subpixel height, the rounding/conversion seems to break things. Do you have anything set using em? to explain quickly: on screen, chrome will consider that 8.8px is equal to 8px (6pt). but when it puts the same content on the paper, it consider that 8.8px = 6.6pt. The amount of content it can add on screen is a bit different than what you have on paper. But since paged,js already made the break between pages. the content moves a little bit. <br />
<br />
I have an idea to test later with @harshna so we could come with a more usable solution (i hope)<br />
<br />
'''m---b''': Thanks so much for the reply, will forward this to the others at Varia who were making the newspaper! And would you recommend to work in pixels or in points? I think I asked you this before... but i can't find my notes back :confused:...<br />
<br />
'''julien''': pixel. because the screen is used to draw the pages first. (we’re exploring options to change a bit how pagedjs do the conversion but it’s not really that simple)<br />
</blockquote><br />
<br />
<blockquote><br />
'''decentral1se''': Hmmmm, yeh, it doesn't seem to be working. I'm only working with px now across the entire stylesheet<br />
<br />
'''decentral1se''': things are getting dissapeared on the page breaks between columns (image 1: pdf view image 2: print preview) <br />
<br />
[[File:Missing-sentences-decentral1se-1.png|300px]] [[File:Missing-sentences-decentral1se-2.png|300px]]<br />
<br />
'''decentral1se''': there is also a report about 2 column layout doing strange things so i might try 3 column layout :thinking_face: <br />
<br />
'''harshna''': I agree its still breaking in some places. Its not only about 2 column layout, we tried with single column layout and it has missing lines too. We are working on a fix for that now.<br />
<br />
'''decentral1se''': aha ok, cool! thanks for the efforts :star2: <br />
<br />
'''decentral1se''': happy to test stuff if that helps<br />
<br />
'''harshna''': it would be great if you could report abnormalities/ any patterns that you find<br />
<br />
'''decentral1se''': thank you<br />
</blockquote><br />
<br />
<blockquote><br />
'''julien''': @decentral1se do you have any footnotes?<br />
<br />
we may have found a way to hack our way out of those weird rounding issues.<br />
<br />
by adding and then removing some emtpy space.<br />
<br />
(a hack,really}<br />
<br />
'''decentral1se''': no footnotes, some text in @page:first { @top-left { content: "..."; ... and page numbers tho. Everythings in https://octomode.vvvvvvaria.org/anarcho-krant-mvp-issue-1/stylesheet/ (DM me for username/password).<br />
<br />
'''decentral1se''': curious about the hack :nerd_face: <br />
<br />
'''julien''': ok so, the idea is to leverage the footnote space by giving it some empty space, and run a hook to remove that space just before printing.<br />
<br />
really, a hack<br />
<br />
<pre><br />
class fixMissingLine extends Paged.Handler {<br />
constructor(chunker, polisher, caller) {<br />
super(chunker, polisher, caller);<br />
this.moveToParentFig = [];<br />
}<br />
afterRendered(pages) {<br />
document.querySelectorAll('.pagedjs_sheet').forEach(sheet => sheet.style.setProperty('--pagedjs-footnotes-height', '0px'))<br />
}<br />
}<br />
Paged.registerHandlers(fixMissingLine);<br />
<br />
and add to your css:<br />
.pagedjs_sheet {<br />
--pagedjs-footnotes-height: 12px<br />
}<br />
</pre><br />
<br />
i hope the children never learn we did such a trick.<br />
<br />
'''decentral1se''': it's hacks all the way down :smile_cat: <br />
<br />
i will see about integrating this into octomode to test<br />
<br />
have you had some luck testing this already? <br />
<br />
oh hmm if i don't already have footnotes, then i can't use this? :thinking_face: <br />
<br />
'''julien''': yep you can <br />
<br />
and yes we tried.<br />
<br />
it’s completely untested and quite dangerous but hey, who wants to live a long and nice and peaceful life right? :sunglasses: <br />
<br />
'''decentral1se''': haha lovely stuff, will try tmoz, thx!<br />
</blockquote><br />
===Links===<br />
<br />
* https://git.vvvvvvaria.org/varia/octomode/issues/25<br />
* https://github.com/pagedjs/pagedjs/issues/130<br />
* https://github.com/pagedjs/pagedjs/issues/87<br />
* https://github.com/pagedjs/pagedjs/issues/87#issuecomment-1476958035<br />
<br />
==Differences in PDF renderings in Mac/Linux==<br />
<br />
https://mattermost.coko.foundation/coko/pl/6jdgxiybridq5bg4scx63tirgh<br />
<br />
[[File:Screenshot-page-77-78-mb.png|thumb|right|screenshot on Linux]] <br />
[[File:Screenshot-page-77-78-simon-sm.png|thumb|right|screenshot on Mac]]<br />
<br />
<blockquote><br />
'''m---b''': Hey all! Hope you are having a lovely summer. @simoon and i're slowly picking up work again in Rotterdam and are wrapping up a remake of the APRJA journal, which is now produced with Paged.js. :wink:<br />
<br />
While going to the list of last changes, we noticed that Paged.js renders the pages differently on a Mac and Linux computer, even though we are on the exact same version of Chrome :grimacing:.<br />
Have you noticed that before? Is there anything we can do?<br />
</blockquote><br />
<br />
<blockquote><br />
'''julien''': hey there!<br />
yeah it’s one of those thing we can’t really do anything about because it’s about mac and linux use their fonts.<br />
<br />
so for example. hypens have been available on mac for much longer than for linux :confused:<br />
<br />
The only workaround is by using pagedjs-cli on a server, which comes with the problem of having a hardest time to make small changes.<br />
</blockquote></div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Compresspdf.sh&diff=5508Compresspdf.sh2026-02-04T17:08:03Z<p>Simoon: </p>
<hr />
<div>==Script==<br />
<br />
[[File:compresspdf-2.png|thumb|right|A PDF's size before compression]]<br />
[[File:compresspdf-1.png|thumb|right|The resampled PDF's size, after compression]]<br />
<br />
<pre><br />
#! /bin/bash<br />
<br />
pdffile=$1;<br />
dpi=$2 <br />
<br />
gs \<br />
-o "${pdffile%.pdf}-resampled.pdf" \<br />
-sDEVICE=pdfwrite \<br />
-dDownsampleColorImages=true \<br />
-dDownsampleGrayImages=true \<br />
-dDownsampleMonoImages=true \<br />
-dColorImageResolution=$dpi \<br />
-dGrayImageResolution=$dpi \<br />
-dMonoImageResolution=$dpi \<br />
-dColorImageDownsampleThreshold=1.0 \<br />
-dGrayImageDownsampleThreshold=1.0 \<br />
-dMonoImageDownsampleThreshold=1.0 \<br />
"${pdffile}"<br />
<br />
</pre><br />
<br />
==How to work with it?==<br />
<br />
'''What does this script do?'''<br><br />
This script squashes large PDFs into very small ones.<br />
<br />
'''In which context was it made?'''<br> <br />
The script is written by [http://osp.kitchen Open Source Publishing]. It has since travelled through other practices to be used for a variety of applications, usually at the eleventh hour before sending PDFs via email and webforms.<br />
<br />
'''What software does it use?'''<br><br />
[https://www.ghostscript.com/ <code>ghostscript</code>]<br />
<br />
'''How to download these pieces of software?'''<br><br />
Go to the URL https://www.ghostscript.com/, you can download it from there.<br />
<br />
'''On which systems can this script run?'''<br><br />
This works from the command line in terminal sessions on Linux systems, also on Mac OS. Windows has a different shell, and it is likely it won't work there.<br />
<br />
'''How to run the script?'''<br><br />
After installing the software <code>ghostscript</code> (see above), save the code above as a bash script with the <code>.sh</code> extension, for example: <code>compresspdf.sh</code>. Don't forget to add <code>#! /bin/bash</code> to the top of your script!<br />
<br />
Make the script executable with<br />
<br />
<code>$ chmod a+x compresspdf.sh</code><br />
<br />
Then, in a terminal session add the PDF you want to compress to the same directory as where <code>compresspdf.sh</code> is saved. <br />
<br />
Then do:<br />
<br />
<code>$ ./compresspdf.sh <file.pdf> <resolution in DPI></code><br />
<br />
For example:<br />
<br />
<code>$ ./compresspdf.sh input.pdf 300</code><br />
<br />
The output will be something like:<br />
<br />
<code>input-resampled.pdf</code><br />
<br />
==Making a portfolio PDF at the last minute==<br />
<br />
This script has been used many times on many machines by many users. It's super handy when making files that need to be sent quickly over a network. One particular use was when making a final final final portfolio PDF for a grant application at the eleventh hour.<br />
<br />
Usually, the portfolio is the last thing I make after I write the application text. I should use a template to work from, but I almost always make a file from scratch. I should be better organised! I add images willy-nilly, tailoring them to the particular grant application. And using CSS-to-print to make a PDF means that your software doesn't have a handy option to compress files when exporting, you have to add this in to the workflow manually.<br />
<br />
On the final day of application, January 31st, the resulting PDF was quite large (122,5mb!). I needed to send this through a webform, and the specification was that it could not be bigger than 10mb.<br />
<br />
So, I used this script just several hours before submitting the PDF. I managed to get the file down to a manageable size without stress, and pressed send in time. In the end I did not get the grant, but I got the script :)<br />
<br />
[[Category:Boilerplates]]</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Compresspdf.sh&diff=5507Compresspdf.sh2026-02-04T17:07:28Z<p>Simoon: /* How to work with it? */</p>
<hr />
<div>==Script==<br />
<br />
[[File:compresspdf-2.png|thumb|right|A PDF's size before compression]]<br />
[[File:compresspdf-1.png|thumb|right|The resampled PDF's size, after compression]]<br />
<br />
<pre><br />
#! /bin/bash<br />
<br />
pdffile=$1;<br />
dpi=$2 <br />
<br />
gs \<br />
-o "${pdffile%.pdf}-resampled.pdf" \<br />
-sDEVICE=pdfwrite \<br />
-dDownsampleColorImages=true \<br />
-dDownsampleGrayImages=true \<br />
-dDownsampleMonoImages=true \<br />
-dColorImageResolution=$dpi \<br />
-dGrayImageResolution=$dpi \<br />
-dMonoImageResolution=$dpi \<br />
-dColorImageDownsampleThreshold=1.0 \<br />
-dGrayImageDownsampleThreshold=1.0 \<br />
-dMonoImageDownsampleThreshold=1.0 \<br />
"${pdffile}"<br />
<br />
</pre><br />
<br />
==How to work with it?==<br />
<br />
'''What does this script do?'''<br><br />
This script squashes large PDFs into very small ones.<br />
<br />
'''In which context was it made?'''<br> <br />
The script is written by [http://osp.kitchen Open Source Publishing]. It has since travelled through other practices to be used for a variety of applications, usually at the eleventh hour before sending PDFs via email and webforms.<br />
<br />
'''What software does it use?'''<br><br />
[https://www.ghostscript.com/ <code>ghostscript</code>]<br />
<br />
'''How to download these pieces of software?'''<br><br />
Go to the URL https://www.ghostscript.com/, you can download it from there.<br />
<br />
'''On which systems can this script run?'''<br><br />
This works from the command line in terminal sessions on Linux systems, also on Mac OS. Windows has a different shell, and it is likely it won't work there.<br />
<br />
'''How to run the script?'''<br><br />
After installing the software <code>ghostscript</code> (see above), save the code above as a bash script with the <code>.sh</code> extension, for example: <code>compresspdf.sh</code>. Don't forget to add <code>#! /bin/bash</code> to the top of your script!<br />
<br />
Make the script executable with<br />
<br />
<code>$ chmod a+x compresspdf.sh</code><br />
<br />
Then, in a terminal session add the PDF you want to compress to the same directory as where <code>compresspdf.sh</code> is saved. <br />
<br />
Then do:<br />
<br />
<code>./compresspdf.sh <file.pdf> <resolution in DPI></code><br />
<br />
For example:<br />
<br />
<code>./compresspdf.sh input.pdf 300</code><br />
<br />
The output will be something like:<br />
<br />
<code>input-resampled.pdf</code><br />
<br />
==Making a portfolio PDF at the last minute==<br />
<br />
This script has been used many times on many machines by many users. It's super handy when making files that need to be sent quickly over a network. One particular use was when making a final final final portfolio PDF for a grant application at the eleventh hour.<br />
<br />
Usually, the portfolio is the last thing I make after I write the application text. I should use a template to work from, but I almost always make a file from scratch. I should be better organised! I add images willy-nilly, tailoring them to the particular grant application. And using CSS-to-print to make a PDF means that your software doesn't have a handy option to compress files when exporting, you have to add this in to the workflow manually.<br />
<br />
On the final day of application, January 31st, the resulting PDF was quite large (122,5mb!). I needed to send this through a webform, and the specification was that it could not be bigger than 10mb.<br />
<br />
So, I used this script just several hours before submitting the PDF. I managed to get the file down to a manageable size without stress, and pressed send in time. In the end I did not get the grant, but I got the script :)<br />
<br />
[[Category:Boilerplates]]</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Server_move&diff=5457Server move2026-01-23T13:59:25Z<p>Simoon: /* Server move */</p>
<hr />
<div><br />
==Server move==<br />
<br />
Notes here: [[Services on CC]]<br />
<br />
* ✅ migrate etherpad<br />
** ✅ install etherpad (<code>/opt/etherpad/</code>)<br />
** ✅ configure nginx <br />
** ✅ set etherpad up as a systemd background process<br />
** ✅ test migration of database<br />
** ✅ migrate the database<br />
* ✅ install mediawiki (<code>/var/www/wiki/</code>, version 1.45)<br />
** ✅ configure nginx<br />
** ✅ install php + php-fpm + mariadb<br />
** ✅ migrate the extensions<br />
** ✅ <del>re-download all extensions</del> not needed, only EtherpadLite<br />
** ✅ applied the hack again to EtherpadLite to hide ip-adresses <br />
** ✅ migrate the images folder<br />
** ✅ make new database<br />
** ✅ test migration of database<br />
** ✅ migrate the database<br />
** ✅ check extensions<br />
** update URL in Localsettings<br />
*** ✅ check if etherpadlite extension works<br />
** ✅ check if wiki works again!<br />
** ✅ check CreatePage extension, disabled now as it threw an error<br />
* ✅ enable home folders<br />
* ✅ migrate home folders<br />
* ✅ migrate /var/www/html/<br />
* ✅ install octomode (<code>/opt/octomode/</code>, running on port 3333)<br />
** ✅ update pad URL in .env file <br />
** test if octomode works<br />
* ✅ install wiki-to-print (<code>/opt/wiki-to-print/</code>, running on port 4444)<br />
** test if wiki-to-print works<br />
** ✅ update wiki URL in config.json<br />
** ✅ update wiki URL in [[MediaWiki:Common.js]]<br />
* change DNS of cc.practices.tools (point to our servus ip-address)<br />
* enable HTTPS<br />
** ✅ install certbot<br />
** ✅ activate cronjob<br />
* decide on http/https redirect in nginx<br />
* ✅ redirect / to /wiki/<br />
* check if https://cc.vvvvvvaria.org still works<br />
** check with Constant, they use the old URL: https://circulations.constantvzw.org/octomode/genocidal_tech/pad/<br />
* ✅ let ServPub people know that the new URL is https://cc.practices.tools<br />
<br />
==SSH==<br />
<br />
Old server:<br />
<br />
Host cc<br />
Hostname 51.195.117.20<br />
User USERNAME<br />
localcommand xtermcontrol --bg "#ffffe0"<br />
<br />
New server:<br />
<br />
Host cc<br />
Hostname 193.170.194.207<br />
User USERNAME<br />
localcommand xtermcontrol --bg "#ffff00"<br />
<br />
[[Category:Sysadmin]]</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Server_move&diff=5454Server move2026-01-23T13:46:04Z<p>Simoon: /* Server move */</p>
<hr />
<div><br />
==Server move==<br />
<br />
Notes here: [[Services on CC]]<br />
<br />
* ✅ migrate etherpad<br />
** ✅ install etherpad (<code>/opt/etherpad/</code>)<br />
** ✅ configure nginx <br />
** ✅ set etherpad up as a systemd background process<br />
** ✅ test migration of database<br />
** ✅ migrate the database<br />
* ✅ install mediawiki (<code>/var/www/wiki/</code>, version 1.45)<br />
** ✅ configure nginx<br />
** ✅ install php + php-fpm + mariadb<br />
** ✅ migrate the extensions<br />
** ✅ <del>re-download all extensions</del> not needed, only EtherpadLite<br />
** ✅ applied the hack again to EtherpadLite to hide ip-adresses <br />
** ✅ migrate the images folder<br />
** ✅ make new database<br />
** ✅ test migration of database<br />
** ✅ migrate the database<br />
** ✅ check extensions<br />
** update URL in Localsettings<br />
*** ✅ check if etherpadlite extension works<br />
** ✅ check if wiki works again!<br />
** ✅ check CreatePage extension, disabled now as it threw an error<br />
* ✅ enable home folders<br />
* ✅ migrate home folders<br />
* ✅ migrate /var/www/html/<br />
* ✅ install octomode (<code>/opt/octomode/</code>, running on port 3333)<br />
** update pad URL in .env file <br />
* ✅ install wiki-to-print (<code>/opt/wiki-to-print/</code>, running on port 4444)<br />
** test if wiki-to-print works<br />
** ✅ update wiki URL in config.json<br />
** ✅ update wiki URL in [[MediaWiki:Common.js]]<br />
* change DNS of cc.practices.tools (point to our servus ip-address)<br />
* enable HTTPS<br />
** install certbot<br />
** ✅ activate cronjob<br />
* decide on http/https redirect in nginx<br />
* ✅ redirect / to /wiki/<br />
* check if https://cc.vvvvvvaria.org still works<br />
** check with Constant, they use the old URL: https://circulations.constantvzw.org/octomode/genocidal_tech/pad/<br />
* let ServPub people know that the new URL is https://cc.practices.tools<br />
<br />
==SSH==<br />
<br />
Old server:<br />
<br />
Host cc<br />
Hostname 51.195.117.20<br />
User USERNAME<br />
localcommand xtermcontrol --bg "#ffffe0"<br />
<br />
New server:<br />
<br />
Host cc<br />
Hostname 193.170.194.207<br />
User USERNAME<br />
localcommand xtermcontrol --bg "#ffff00"<br />
<br />
[[Category:Sysadmin]]</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Server_move&diff=5422Server move2026-01-23T10:29:40Z<p>Simoon: </p>
<hr />
<div><br />
==Server move==<br />
<br />
Notes here: [[Services on CC]]<br />
<br />
* migrate etherpad<br />
** ✅ install etherpad (<code>/opt/etherpad/</code>)<br />
** ✅ configure nginx <br />
** ✅ set etherpad up as a systemd background process<br />
** ✅ test migration of database<br />
** migrate the database<br />
* ✅ install mediawiki (<code>/var/www/wiki/</code>, version 1.45)<br />
** ✅ configure nginx<br />
** ✅ install php + php-fpm + mariadb<br />
** ✅ migrate the extensions<br />
** ✅ <del>re-download all extensions</del> not needed, only EtherpadLite<br />
** ✅ applied the hack again to EtherpadLite to hide ip-adresses <br />
** migrate the images folder<br />
** ✅ make new database<br />
** ✅ test migration of database<br />
** migrate the database<br />
** ✅ check extensions<br />
*** check if etherpadlite extension works<br />
** ✅ check if wiki works again!<br />
** ✅ check CreatePage extension, disabled now as it threw an error<br />
* ✅ enable home folders<br />
* migrate home folders<br />
* migrate /var/www/html/<br />
* ✅ install octomode (<code>/opt/octomode/</code>, running on port 3333)<br />
* ✅ install wiki-to-print (<code>/opt/wiki-to-print/</code>, running on port 4444)<br />
** ✅ test if wiki-to-print works<br />
* change DNS of cc.practices.tools (point to our servus ip-address)<br />
* enable HTTPS<br />
** install certbot<br />
** ✅ activate cronjob<br />
* decide on http/https redirect in nginx<br />
* ✅ redirect / to /wiki/<br />
* check if https://cc.vvvvvvaria.org still works<br />
* let ServPub people know that the new URL is https://cc.practices.tools<br />
<br />
==SSH==<br />
<br />
Old server:<br />
<br />
Host cc<br />
Hostname 51.195.117.20<br />
User USERNAME<br />
localcommand xtermcontrol --bg "#ffffe0"<br />
<br />
New server:<br />
<br />
Host cc<br />
Hostname 193.170.194.207<br />
User USERNAME<br />
localcommand xtermcontrol --bg "#ffff00"<br />
<br />
[[Category:Sysadmin]]</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Working_with_what%27s_there&diff=5357Working with what's there2025-12-24T23:16:37Z<p>Simoon: </p>
<hr />
<div>[[File:varia-darktimes-sticker-sheet.jpeg|thumb|The full sticker set]]<br />
[[File:varia-darktimes-sticker-on-laptop.jpeg|thumb|One of the stickers on my laptop]]<br />
<br />
If we consider design to be a collaborative, transformative activity of world-building as opposed to just problem-solving, how to think about the materials, entities, and groups that are there to work with?<br />
<br />
What does it mean to ''work with material that is already there''? What does this bring to a design practice?<br />
<br />
I'm trying to articulate this in writing on this page. Here is a place to start gathering thoughts around these topics:<br />
<br />
* starting from the middle<br />
* entry points into ongoing conversations around collaborative and collective practices<br />
* working within a material practice (I want to relate this to [[With_Simon_about_experimental_publishing|these thoughts]] about experimental publishing)<br />
* autonomy (choosing inter-dependencencies)<br />
* subsistence and frugality<br />
* immediacy and DIY<br />
* collaboration and DIWO<br />
* finding joy and inspiration within limitations<br />
* pedagogy and figuring things out together<br />
* improvisation and ad-hoc approaches<br />
<br />
One example of working with what's there is an improvised sticker set I made for an issue of SomeTimes with Danny at Varia. We were struggling to find inspiration while designing stickers that reflected the theme of Varia's 2025/2026 Seasonal Computing public programme. Danny suggested making a "dark" sticker set, which contained inside jokes and puns. I had some pre-cut circular sticker sheets laying around from a project in 2012, so I decided to try out some designs that I could print myself. I designed a sheet using a font I bootlegged in 2015 from an Inuit calendar. I've been using this font quite a lot lately, because it is there. The apostrophes as accidentally reversed, but I don't want to fix that because it is not necessary and the font will only be used for display text. What is more important is that the font, like the pre-cut sticker sheets, is at easily at hand.</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Working_with_what%27s_there&diff=5356Working with what's there2025-12-24T23:15:50Z<p>Simoon: </p>
<hr />
<div>[[File:varia-darktimes-sticker-sheet.jpeg|thumb|The full sticker set]]<br />
[[File:varia-darktimes-sticker-on-laptop.jpeg|thumb|One of the stickers on my laptop]]<br />
<br />
If we consider design to be a collaborative, transformative activity of world-building as opposed to just problem-solving, how to think about the materials, entities, and groups that are there to work with?<br />
<br />
What does it mean to ''work with material that is already there''? What does this bring to a design practice?<br />
<br />
I'm trying to articulate this in writing on this page. Here is a place to start gathering thoughts around these topics:<br />
<br />
* starting from the middle<br />
* entry points into ongoing conversations around collaborative and collective practices<br />
* working within a material practice (I want to relate this to [[With_Simon_about_experimental_publishing|these thoughts]] about experimental publishing)<br />
* autonomy (choosing inter-dependencencies)<br />
* subsistence and frugality<br />
* immediacy and DIY<br />
* collaboration and DIWO<br />
* finding joy and inspiration within limitations<br />
* pedagogy and figuring things out together<br />
* improvisation and ad-hoc approaches<br />
<br />
While making design and art in the past years, I've noticed that working with what is around me has brought the most joy, and simplified my approach.<br />
<br />
One example is an improvised sticker set I made while working on SomeTimes with Danny at Varia. We were struggling to find inspiration while designing stickers that reflected the theme of Varia's 2025/2026 Seasonal Computing public programme. Danny suggested making a "DarkTimes" sticker set, which contained inside jokes and puns. I had some pre-cut circular sticker sheets laying around from a project in 2012, so I decided to try out some designs that I could print myself. I designed a sheet using a font I bootlegged in 2015 from an Inuit calendar. I've been using this font quite a lot lately, because it is there. The apostrophes as accidentally reversed, but I don't want to fix that because it is not necessary and the font will only be used for display text. What is more important is that the font, like the pre-cut sticker sheets, is at easily at hand.</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=User:Simoon&diff=5355User:Simoon2025-12-24T23:14:35Z<p>Simoon: /* Puns */</p>
<hr />
<div>''F/LOSS design + publishing at [https://varia.zone Varia], [https://osp.kitchen OSP] and here at CC''<br />
<br />
[[File:simon-bio-pic-2025.jpeg|thumb|2025 bio pic, photo courtesy of Clara Pasteau]]<br />
<br />
==CC-Housekeeping==<br />
''Keeping up with sysadmin work''<br />
<br />
*[[CC_to_do_list|CC to do list]]<br />
*[[:Category:Sysadmin]]<br />
*[[CC-collective conditions for use]]<br />
<br />
==CC-Conversations==<br />
''Conversations with others about publishing and design''<br />
<br />
===about wiki publishing===<br />
* [[Relearning layout]] with Manetta<br />
* [[Wiki-to-print, Wiki2print, Wiki-to-pdf,_and_so_on...]] together with Manetta (as Varia), and with Anja, Karl & Heerko (as Hackers & Designers)<br />
* [[Wiki_publishing_chapter|Wiki publishing]] with Manetta, in the context of ServPub<br />
<br />
==Puns==<br />
''Jokes that will change the world''<br />
<br />
* Abode (for) Creative Crowds<br />
* Two's company, three's a creative crowd<br />
* Sime's New Roman<br />
* You are in CC<br />
* My work is at the intersection of Wolphaertstraat and Gouwstraat<br />
<br />
==Snippets==<br />
''Bits and pieces of writing''<br />
<br />
* [[Re-pairing]]<br />
* [[D*signweek 2025]]<br />
* [[Working with what's there]]<br />
<br />
==Typography==<br />
''Keeping links and references here in one place''<br />
<br />
*[https://www.msarnoff.org/millitext/ Millitext], using subpixels (via Doriane)<br />
<br />
==Zines==<br />
<br />
* [[Why Bootleg Books? / Pourquoi des livres pirates?|''Why Bootleg Books? / Pourquoi des livres pirates?'']] published February 2025 at esam Caen (FR)<br />
* [[Octomode#so,_you_decided_to_make_a_zine_using_octomode|''So, you decided to make a zine using Octomode'']] published June 2025 at the Leitrim Sculpture Center (IE)</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Finances&diff=5354Finances2025-12-21T08:35:54Z<p>Simoon: /* CC costs */</p>
<hr />
<div>This is a collective log of our finances.<br />
<br />
==CC costs==<br />
<br />
{| class="wikitable sortable"<br />
|+ <br />
|-<br />
! what !! date !! who paid !! amount !! shared<br />
|-<br />
| OVH server purchase || 22 December 2023 || manetta || € 150 || 50/50<br />
|-<br />
| Servus membership || 01-04-2024 till 30-06-2024 || manetta || € 90 || 50/50<br />
|-<br />
| Servus membership || 01-07-2024 till 31-12-2024 || manetta || € 90 || 50/50<br />
|-<br />
| OVH backups 1 year || 24-12-2024 till 24-12-2025 || simon || € 67,35 || 50/50<br />
|-<br />
| OVH server renewal 1 month || 22-12-2024 || simon || € 23,11 || 50/50<br />
|-<br />
| OVH server renewal 1 month || 18-01-2025 || simon || € 23,11 || 50/50<br />
|-<br />
| OVH server renewal 1 month|| 19-02-2025 || simon || € 23,11 || 50/50<br />
|-<br />
| OVH server renewal 3 months || 11-03-2025 || simon || € 69,33 || 50/50<br />
|-<br />
| OVH server renewal 3 months || 27-05-2025 || simon || € 69,33 || 50/50<br />
|-<br />
| OVH server renewal 3 months || 10-09-2025 || simon || € 69,33 || 50/50<br />
|-<br />
| Servus membership || 2025 Q1 + Q2 || manetta || € 180 || 50/50<br />
|-<br />
| stickers PrinterPro || November 2025 || manetta || € 111,61 || not needed<br />
|-<br />
| OVH server renewal 1 month|| 21-12-2025 || simon || € 23,11 || not yet<br />
|- <br />
| xxx || xxx || xxx || xxx || xxx<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx<br />
|}<br />
<br />
==CC income==<br />
<br />
{| class="wikitable sortable"<br />
|+ <br />
|-<br />
! what !! date !! from who !! to whom !! amount !! recirculated<br />
|-<br />
| Toward a Minor Tech (phase 1) || 16-02-2023 || CSNI (through Varia) || manetta || € 1796,88 || manetta + simon's part??<br />
|-<br />
| Toward a Minor Tech (phase 2) || ??? || CSNI (through Varia) || manetta || € ??? || manetta's part<br />
|-<br />
| Toward a Minor Tech (phase 1) || 19-02-2023 || CSNI (through Varia) || simon || € 934,38 || simon's part<br />
|-<br />
| Toward a Minor Tech (phase 2) || 23-08-2023 || CSNI (through Varia) || simon || € 305,47 || simon's part<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx || xxx<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx || xxx<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx || xxx<br />
|-<br />
| Content/Form || xxx || xxx || xxx || £ 1,000.00 || split between manetta & simon<br />
|-<br />
| contribution to CC for using octomode during a workshop at Utrecht University || 21-04-2023 || Winnie & Geoff || Varia || € 400 || split between manetta & simon <br />
|-<br />
| contribution to CC for using the pads || soon, December 2025 || Constant || simon || € 500 || to production costs of self-published version of servpub contribution<br />
|-<br />
| ServPub book event || 26-11-2025 || Coventry University || simon || € 249,39 || yes, to simon<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx || xxx<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx || xxx<br />
|}<br />
<br />
[[Category:Sysadmin]]</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Technotextual_editorial_guidelines&diff=5254Technotextual editorial guidelines2025-11-30T14:39:25Z<p>Simoon: /* Who commits to be responsible for what?= */</p>
<hr />
<div>== Technotextual editorial guidelines for wiki layout practices ==<br />
<br />
''Wiki software has an attitude! The following are a set of handles to be reused as guidelines during a conversation between editor-designers and design-editors at the start of a publishing project, to shape the editorial workflow together.''<br />
<br />
Open questions:<br />
* the scope of this document: focus on wiki-to-print or wiki-layout practices (which includes websites, printed publications, ...)<br />
* do we want to include examples of wiki projects?<br />
* check references<br />
* opinionated enough?<br />
<br />
<br />
===What role does the wiki play?===<br />
<br />
A wiki invites readers to become writers. And to be messy, to repeat and re-embed material, to let unfinished thoughts linger around and to let structure emerge collectively and over time. <br />
<br />
As a writing environment, it invites us to bend the idea of an individual genius author into a distributed practice of writing.<br />
<br />
* Is the wiki an online environment that readers can find and browse?<br />
* Can readers also write?<br />
<br />
<br />
===Is the wiki a temporary production environment or continuous infrastructure?===<br />
<br />
We understand infrastructure as something that exist because multiple people depend on it, something that is present for a longer amount of time, and something that does not change a lot but needs maintenance. <br />
<br />
When using a wiki to publish from, writing can go through phases of transformation, versioning and change.<br />
<br />
* Is this publication a snapshot of a particular state of a wiki in flux? <br />
* Or is this wiki a production environment for the making of this publication? <br />
<br />
<!-- <br />
<br />
https://post.lurk.org/@hannah@posts.rat.pictures/114333527919107597<br />
<br />
--><br />
<br />
===What can a page become?===<br />
<br />
What we like about the wiki as a writing environment, is that it comes with a very open understanding of a page. Wiki’s are based on the idea that everything is a page. By default, a wiki does not work with templates and input fields for a title, subtitle, introduction, etc, such as Wordpress for example does. There is no structural difference between the landing page or any other page, even the uploaded images are stored on a specific File namespace page. This radical horizontal approach gives the space to turn each wiki page into any kind of page you want. A wiki page can turn into an essay, an annotated image gallery, a piece of code, a logbook or a budget sheet. <br />
<br />
* What limits do we want to set for a page?<br />
<br />
<!--<br />
<br />
(ontology of the page)<br />
<br />
How does the wiki understand pages?<br />
<br />
What do the contributors want pages to be?<br />
<br />
Can there be different understanding of a page within the publication?<br />
<br />
How much structure is needed for the production of the layout?<br />
<br />
[example of placing an image on a page]<br />
<br />
WikiWikiWeb (the first wiki, made by Ward Cunningham) describes its culture as distinctly different from WikiPedia: https://wiki.c2.com/?WikiIsNotWikipedia. For example, they do not always give attribution to content &quot;shamelessly ripped off from other forums&quot;.<br />
<br />
* not making one centralized structure<br />
* but structure emerging through writing and practice situated in a cultural context<br />
<br />
[example of the User pages in the pzwiki]<br />
<br />
--><br />
<br />
===Does hypertext shape our writing?===<br />
<br />
Can the content be written in smaller pieces that can be assembled together in different ways?<br />
<br />
non-sequential writing<br />
<br />
finding different paths through the material<br />
<br />
Ted Nelson describes a feature of hypertext: to create a public repository through which new texts can be re-assembled<br />
<br />
when writing smaller pieces, it's easier to "hook in" to each others writing<br />
<br />
How to motivate others to write?<br />
<br />
How can a page become an invitation to write another page in response?<br />
<br />
role of red-links, parking an idea<br />
<br />
[ref olia lialina "links" in A Vernacular Web text?] https://art.teleportacia.org/observation/vernacular/links.html<br />
<br />
===Who is the author of this publication?===<br />
<br />
Which authorship regimes does the publication cross with? <br />
How does this shape our common understanding of an author? <br />
How does this shape our approach to referencing?<br />
<br />
* wiki understanding: "a wiki is actually hyper-authored" (Michael), everything is traced through revisions, based on a single branch (no diverging and merging), there is always just one published version of the text, disagreement is not visible (there is space for it in Talk pages and in the History)<br />
* academic economy of referencing, footnotes/endnotes<br />
* practice based attribution<br />
* CC4r: i as an author am not disconnected from all the authors that i learned from and have grown with, plus i want to keep their living conditions into account<br />
<br />
What is the difference between:<br />
<br />
* contributor (multiple ways to contribute to a larger body of text)<br />
* author (having the authority/responsibility to speak)<br />
<br />
Let's not say: this publication is made by us all in "collective authorship". That might mean that we avoid any conversation about this. Has there been a consensus about this, really? <br />
At the same time, collective authorship can be a strategic way to share responsibility across a group.<br />
<br />
Who can reuse the material?<br />
<br />
[[File:Revisions-New media art in Slovakia 1990s 2000s.dot.png|thumb|First outcome of our wiki technotext ethnographic trajectory. The graph above was generated with [https://cc.vvvvvvaria.org/~friends/recentchanges.py this script], using Python, Jinja and GraphViz and working with the wiki of monoskop.org.]]<br />
<br />
[Something about authorship as revisions? About the hidden position of the version tracker under the “View history” tab?]<br />
<br />
In a forum, for instance, the focus lies much more on individual voices. Different authors state their ideas, and formulate them clearly in a post. On a wiki however, the focus is on the text on a page. The name of an author is not even visible by default. The text that is written is the central point of attention.<br />
<br />
[ref olia lialina "tilde" in A Vernacular Web text?] https://art.teleportacia.org/observation/vernacular/tilde.html<br />
<br />
<br style="clear:both;"><br />
<br />
===Who commits to be responsible for what?===<br />
<br />
- wiki understanding: bureaucrats, administrators, moderators, editor<br />
- design-editors and editor-designers: it's not about anyone can do anything, it's about committment!<br />
<br />
===How does the wiki shape our collaboration (or not)?===<br />
<br />
The role of the RecentChanges page, the diff's, the wiki as an async collaboration environment. <br />
The need to switch to pads sometimes to be close to a thought process in real time.<br />
<br />
How can traces of our collaboration be included in the layout?<br />
<br />
What we know of layout comes from the history of the printing press.. The traces of the digital are often invisible... How can we show that this layout comes from another timeline/history/context?<br />
<br />
How does the visibility of edits and editors co-shape the writing?<br />
What kind of paratext can the recent changes become? What role can they get in a book?<br />
<br />
<br />
[[File:Recentchanges-cc.vvvvvvaria.org_wiki-2025-04-11.dot.png|thumb|April 11th, 2025: Snapshot layout of the recent changes to the wiki of cc.vvvvvvaria.org.]]<br />
<br />
[[File:recentchanges-monoskop.org-2025-04-11.dot.png|thumb|April 11th, 2025: Snapshot layout of the recent changes to the wiki of monoskop.org.]]<br />
<br />
[[File:recentchanges-wiki4print.servpub.net-2025-04-03.dot.png|thumb|April 11th, 2025: Snapshot layout of the recent changes to the wiki of wiki4print.servpub.net.]]<br />
<br />
[recent changes snapshots thinking here?]<br />
<br />
The RecentChanges page as the (backstage?) a wiki, as a place that reveals both the social dynamics and also its specific culture. Who is there? Who wrote something today? It's a page that signals that a wiki page, that has maybe been forgotten for years, is relevant again and connects to a specific activity happening today.<br />
<br />
The RecentChanges page as a social environment is exciting. <br />
<br />
Taking samples at different moments to make layouts. It introduces an element of time and temporality. <br />
<br />
<br style="clear:both;"><br />
<br />
===Which medium will this publication transform into?===<br />
<br />
* wiki-to-print<br />
* wiki-to-pdf<br />
* wiki-to-graphs<br />
* wiki-to-slideshow<br />
* wiki-to-stickers<br />
* wiki-to-podcast<br />
* wiki-to-website<br />
* wiki-to-index-cards<br />
* wiki-to-stencil<br />
* wiki-to-riso<br />
* wiki-to-polymer-clay<br />
* wiki-to-email-thread<br />
* wiki-to-rss-feed<br />
* wiki-to-video<br />
* wiki-to-puppet-show<br />
<br />
A layout engine is an environment that defines the parameters with which you can produce layout.<br />
Layout is about situated meaning making through positioning/arranging graphic elements spatially.<br />
<br />
Thoughts about Graphviz? <br />
<br />
Notes about Paged.js and wiki-to-print?<br />
<br />
====wiki-as-wiki====<br />
<br />
'''browser'''<br />
<br />
A wiki skin is a layout in itself.<br />
<br />
====wiki-to-print====<br />
<br />
'''Paged.js, Python, Jinja, Flask, Pandoc, Mediawiki:Common.js, Mediawiki:Common.css'''<br />
<br />
polyfill, codex logics<br />
<br />
====wiki-to-graphs====<br />
<br />
'''GraphViz, Python, Jinja'''<br />
<br />
Taking snapshots of a wiki using [https://graphviz.org/ GraphViz] to make layout. As a layout engine, GraphViz is not easy to control, and that's meant to be so. You can control some things like fontsize and shape of the nodes, but the placement of nodes and edges is controlled by the software.<br />
<br />
If you make something for print, or for the web, you think about how long something will last. We tend to then simplify layout, to make it accessible for people for as long as the layout exists. We follow conventions based on our reading direction (left to right, top to bottom in our language). Putting something on the top-left of the page (like a link to a homepage), is a decision that feels very accessible.<br />
<br />
But GraphViz follows a different approach. It places the nodes and the edges without thinking about usual hierarchies, or usual ways of reading. We have done a bit of that with the title of the graphs. Here the placement at the top is important, it is different information to the content of the graph. But the rest of the layout of the graph is decided upon by GraphViz. And also placed differently once the content of the graph changes. It connects the act of making snapshots and taking a particular slice from the bigger whole in the form of a graph at a particular moment in time. From the start, we were excited about the aesthetics of the wiki that are structural. The GraphViz output comes close to this, as it starts to show this structure.<br />
<br />
[include link to the code we wrote]<br />
<br />
<noinclude><br />
[[Category:ServPub]]<br />
</noinclude></div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Finances&diff=5253Finances2025-11-30T10:05:14Z<p>Simoon: /* CC income */</p>
<hr />
<div>This is a collective log of our finances.<br />
<br />
==CC costs==<br />
<br />
{| class="wikitable sortable"<br />
|+ <br />
|-<br />
! what !! date !! who paid !! amount !! shared<br />
|-<br />
| OVH server purchase || 22 December 2023 || manetta || € 150 || yes<br />
|-<br />
| Servus membership || 01-04-2024 till 30-06-2024 || manetta || € 90 || not yet<br />
|-<br />
| Servus membership || 01-07-2024 till 31-12-2024 || manetta || € 90 || not yet<br />
|-<br />
| OVH backups 1 year || 24-12-2024 till 24-12-2025 || simon || € 67,35 || not yet<br />
|-<br />
| OVH server renewal 1 month || 22-12-2024 || simon || € 23,11 || not yet<br />
|-<br />
| OVH server renewal 1 month || 18-01-2025 || simon || € 23,11 || not yet<br />
|-<br />
| OVH server renewal 1 month|| 19-02-2025 || simon || € 23,11 || not yet<br />
|-<br />
| OVH server renewal 3 months || 11-03-2025 || simon || € 69,33 || not yet<br />
|-<br />
| OVH server renewal 3 months || 27-05-2025 || simon || € 69,33 || not yet<br />
|-<br />
| OVH server renewal 3 months || 10-09-2025 || simon || € 69,33 || not yet<br />
|-<br />
| Servus membership || 2025 Q1 + Q2 || manetta || € 180 || not yet<br />
|-<br />
| stickers PrinterPro || November 2025 || manetta || € 111,61 || not yet<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx<br />
|- <br />
| xxx || xxx || xxx || xxx || xxx<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx<br />
|}<br />
<br />
==CC income==<br />
<br />
{| class="wikitable sortable"<br />
|+ <br />
|-<br />
! what !! date !! from who !! to whom !! amount !! recirculated<br />
|-<br />
| Toward a Minor Tech (phase 1) || 16-02-2023 || CSNI (through Varia) || manetta || € 1796,88 || manetta's part<br />
|-<br />
| Toward a Minor Tech (phase 2) || ??? || CSNI (through Varia) || manetta || € ??? || manetta's part<br />
|-<br />
| Toward a Minor Tech (phase 1) || 19-02-2023 || CSNI (through Varia) || simon || € 934,38 || simon's part<br />
|-<br />
| Toward a Minor Tech (phase 2) || 23-08-2023 || CSNI (through Varia) || simon || € 305,47 || simon's part<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx || xxx<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx || xxx<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx || xxx<br />
|-<br />
| Content/Form || xxx || xxx || xxx || £ 1,000.00 || split between manetta & simon<br />
|-<br />
| contribution to CC for using octomode during a workshop at Utrecht University || 21-04-2023 || Winnie & Geoff || Varia || € 400 || split between manetta & simon <br />
|-<br />
| contribution to CC for using the pads || soon, December 2025 || Constant || ?? || € 500 || not yet<br />
|-<br />
| ServPub book event || 26-11-2025 || Coventry University || simon || € 249,39 || yes, to simon<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx || xxx<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx || xxx<br />
|}</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Finances&diff=5252Finances2025-11-30T09:55:31Z<p>Simoon: </p>
<hr />
<div>This is a collective log of our finances.<br />
<br />
==CC costs==<br />
<br />
{| class="wikitable sortable"<br />
|+ <br />
|-<br />
! what !! date !! who paid !! amount !! shared<br />
|-<br />
| OVH server purchase || 22 December 2023 || manetta || € 150 || yes<br />
|-<br />
| Servus membership || 01-04-2024 till 30-06-2024 || manetta || € 90 || not yet<br />
|-<br />
| Servus membership || 01-07-2024 till 31-12-2024 || manetta || € 90 || not yet<br />
|-<br />
| OVH backups 1 year || 24-12-2024 till 24-12-2025 || simon || € 67,35 || not yet<br />
|-<br />
| OVH server renewal 1 month || 22-12-2024 || simon || € 23,11 || not yet<br />
|-<br />
| OVH server renewal 1 month || 18-01-2025 || simon || € 23,11 || not yet<br />
|-<br />
| OVH server renewal 1 month|| 19-02-2025 || simon || € 23,11 || not yet<br />
|-<br />
| OVH server renewal 3 months || 11-03-2025 || simon || € 69,33 || not yet<br />
|-<br />
| OVH server renewal 3 months || 27-05-2025 || simon || € 69,33 || not yet<br />
|-<br />
| OVH server renewal 3 months || 10-09-2025 || simon || € 69,33 || not yet<br />
|-<br />
| Servus membership || 2025 Q1 + Q2 || manetta || € 180 || not yet<br />
|-<br />
| stickers PrinterPro || November 2025 || manetta || € 111,61 || not yet<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx<br />
|- <br />
| xxx || xxx || xxx || xxx || xxx<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx<br />
|}<br />
<br />
==CC income==<br />
<br />
{| class="wikitable sortable"<br />
|+ <br />
|-<br />
! what !! date !! from who !! to whom !! amount !! recirculated<br />
|-<br />
| Toward a Minor Tech (phase 1) || 16-02-2023 || CSNI (through Varia) || manetta || € 1796,88 || manetta's part<br />
|-<br />
| Toward a Minor Tech (phase 2) || ??? || CSNI (through Varia) || manetta || € ??? || manetta's part<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx || xxx<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx || xxx<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx || xxx<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx || xxx<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx || xxx<br />
|-<br />
| Content/Form || xxx || xxx || xxx || £ 1,000.00 || split between manetta & simon<br />
|-<br />
| contribution to CC for using octomode during a workshop at Utrecht University || 21-04-2023 || Winnie & Geoff || Varia || € 400 || split between manetta & simon <br />
|-<br />
| contribution to CC for using the pads || soon, December 2025 || Constant || ?? || € 500 || not yet<br />
|-<br />
| ServPub book event || 26-11-2025 || Coventry University || simon || € 249,39 || yes, to simon<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx || xxx<br />
|-<br />
| xxx || xxx || xxx || xxx || xxx || xxx<br />
|}</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=PdfCSS:Dw&diff=5240PdfCSS:Dw2025-11-29T15:32:01Z<p>Simoon: </p>
<hr />
<div>@page{<br />
size:a5;<br />
}<br />
<br />
p {<br />
color: purple;<br />
}</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Pdf:Dw&diff=5239Pdf:Dw2025-11-29T15:30:45Z<p>Simoon: </p>
<hr />
<div>hello<br />
<br />
=[[Tools]]=<br />
{{ :Tools }}<br />
<br />
=[[Howtos]]=<br />
{{ :Howtos }}</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Pdf:Dw&diff=5238Pdf:Dw2025-11-29T15:29:46Z<p>Simoon: </p>
<hr />
<div>hello<br />
<br />
=Tools=<br />
{{ :Tools }}<br />
<br />
=Howtos=<br />
{{ :Howtos }}</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Pdf:Dw&diff=5237Pdf:Dw2025-11-29T15:28:59Z<p>Simoon: </p>
<hr />
<div>hello<br />
<br />
{{ :Tools }}<br />
<br />
{{ :Howtos }}</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Pdf:Dw&diff=5236Pdf:Dw2025-11-29T15:28:35Z<p>Simoon: </p>
<hr />
<div>hello<br />
<br />
{{ :Tools }}</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=PdfCSS:Dw&diff=5235PdfCSS:Dw2025-11-29T15:27:12Z<p>Simoon: </p>
<hr />
<div>* {<br />
border: 1px solid red;<br />
}<br />
<br />
@page{<br />
size:a5;<br />
}</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=PdfCSS:Dw&diff=5234PdfCSS:Dw2025-11-29T15:23:30Z<p>Simoon: Created page with "@page{ size:a5; }"</p>
<hr />
<div>@page{<br />
size:a5;<br />
}</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Pdf:Dw&diff=5233Pdf:Dw2025-11-29T15:22:45Z<p>Simoon: </p>
<hr />
<div>hello</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Pdf:Dw&diff=5232Pdf:Dw2025-11-29T15:22:31Z<p>Simoon: Created blank page</p>
<hr />
<div></div>Simoonhttp://cc.practices.tools/wiki/index.php?title=MediaWiki:Sidebar&diff=5219MediaWiki:Sidebar2025-11-28T16:42:25Z<p>Simoon: </p>
<hr />
<div>* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
* Installed on CC<br />
** Octomode|octomode<br />
** Wiki-to-print|wiki-to-print<br />
** Cobbled-paths|cobbled-paths<br />
* Possibly handy pages<br />
** Tools|tools<br />
** Links|links<br />
** Fonts|fonts<br />
** Howtos|howtos<br />
** CSS Print|CSS print<br />
** Error log|error log<br />
** Category:Sysadmin|sysadmin<br />
** Editing Guide|editing guide<br />
* Things we made<br />
** https://cc.practices.tools/pdf/so-you-decided-to-make-a-zine-in-octomode.pdf|so, you decided to make a zine in octomode<br />
** Pdf:Tools_shape_practice_shapes_tools|Tools shape practices shape tools<br />
** Content-Form|Content-Form<br />
** Toward a Minor Tech|Toward a Minor Tech<br />
* TOOLBOX</div>Simoonhttp://cc.practices.tools/wiki/index.php?title=Working_with_what%27s_there&diff=5214Working with what's there2025-11-26T12:02:48Z<p>Simoon: </p>
<hr />
<div>[[File:varia-darktimes-sticker-sheet.jpeg|thumb|The full sticker set]]<br />
[[File:varia-darktimes-sticker-on-laptop.jpeg|thumb|One of the stickers on my laptop]]<br />
<br />
If we consider design to be a collaborative, transformative activity of world-building as opposed to just problem-solving, how to think about the materials, entities, and groups that are there to work with?<br />
<br />
What does it mean to ''work with material that is already there''? What does this bring to a design practice?<br />
<br />
I'm trying to articulate this in writing on this page. Here is a place to start gathering thoughts around these topics:<br />
<br />
* starting from the middle<br />
* entry points into ongoing conversations around collaborative and collective practices<br />
* working within a material practice (I want to relate this to [[With_Simon_about_experimental_publishing|these thoughts]] about experimental publishing)<br />
* autonomy (choosing inter-dependencencies)<br />
* subsistence and frugality<br />
* immediacy and DIY<br />
* collaboration and DIWO<br />
* finding joy and inspiration within limitations<br />
* pedagogy and figuring things out together<br />
* improvisation and ad-hoc approaches<br />
<br />
While making design and art in the past years, I've noticed that working with what is around me has been a successful approach.<br />
<br />
One example is an improvised sticker set I made while working on SomeTimes with Danny at Varia. We were struggling to find inspiration while designing stickers that reflected the theme of Varia's 2025/2026 Seasonal Computing public programme. Danny suggested making a "DarkTimes" sticker set, which contained inside jokes and puns. I had some pre-cut circular sticker sheets laying around from a project in 2012, so I decided to try out some designs that I could print myself. I designed a sheet using a font I bootlegged in 2015 from an Inuit calendar. I've been using this font quite a lot lately, because it is there. The apostrophes as accidentally reversed, but I don't want to fix that because it is not necessary and the font will only be used for display text. What is more important is that the font, like the pre-cut sticker sheets, is at easily at hand.</div>Simoon