blog/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2           "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
   4   <head>
   5     <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
   6     <title>Petter Reinholdtsen</title>
   7     <link rel="stylesheet" type="text/css" media="screen" href="https://people.skolelinux.org/pere/blog/style.css" />
   8     <link rel="stylesheet" type="text/css" media="screen" href="https://people.skolelinux.org/pere/blog/vim.css" />
   9     <link rel="alternate" title="RSS Feed" href="https://people.skolelinux.org/pere/blog/index.rss" type="application/rss+xml" />
  10   </head>
  11   <body>
  12     <div class="title">
  13  <h1>
  14      <a href="https://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  15
  16  </h1>
  17
  18 </div>
  19
  20
  21
  22     <div class="entry">
  23       <div class="title"><a href="https://people.skolelinux.org/pere/blog/Plain_text_accounting_file_from_your_bitcoin_transactions.html">Plain text accounting file from your bitcoin transactions</a></div>
  24       <div class="date"> 7th March 2024</div>
  25       <div class="body"><p>A while back I wrote a small script to extract the Bitcoin
  26 transactions in a wallet in the
  27 <ahref="https://plaintextaccounting.org/">ledger plain text accounting
  28 format</a>.  The last few days I spent some time to get it working
  29 better with more special cases.  In case it can be useful for others,
  30 here is a copy:</p>
  31
  32 <p><blockquote><pre>
  33 #!/usr/bin/python3
  34 #  -*- coding: utf-8 -*-
  35 #  Copyright (c) 2023-2024 Petter Reinholdtsen
  36
  37 from decimal import Decimal
  38 import json
  39 import subprocess
  40 import time
  41
  42 import numpy
  43
  44 def format_float(num):
  45     return numpy.format_float_positional(num, trim='-')
  46
  47 accounts = {
  48     u'amount' : 'Assets:BTC:main',
  49 }
  50
  51 addresses = {
  52     '<some address>' : 'Assets:bankkonto',
  53     '<some address>' : 'Assets:bankkonto',
  54 }
  55
  56 def exec_json(cmd):
  57     proc = subprocess.Popen(cmd,stdout=subprocess.PIPE)
  58     j = json.loads(proc.communicate()[0], parse_float=Decimal)
  59     return j
  60
  61 def list_txs():
  62     # get all transactions for all accounts / addresses
  63     c = 0
  64     txs = []
  65     txidfee = {}
  66     limit=100000
  67     cmd = ['bitcoin-cli', 'listtransactions', '*', str(limit)]
  68     if True:
  69         txs.extend(exec_json(cmd))
  70     else:
  71         # Useful for debugging
  72         with open('transactions.json') as f:
  73             txs.extend(json.load(f, parse_float=Decimal))
  74     #print txs
  75     for tx in sorted(txs, key=lambda a: a['time']):
  76 #        print tx['category']
  77         if 'abandoned' in tx and tx['abandoned']:
  78             continue
  79         if 'confirmations' in tx and 0 >= tx['confirmations']:
  80             continue
  81         when = time.strftime('%Y-%m-%d %H:%M', time.localtime(tx['time']))
  82         if 'message' in tx:
  83             desc = tx['message']
  84         elif 'comment' in tx:
  85             desc = tx['comment']
  86         elif 'label' in tx:
  87             desc = tx['label']
  88         else:
  89             desc = 'n/a'
  90         print("%s %s" % (when, desc))
  91         if 'address' in tx:
  92             print("  ; to bitcoin address %s" % tx['address'])
  93         else:
  94             print("  ; missing address in transaction, txid=%s" % tx['txid'])
  95         print(f"  ; amount={tx['amount']}")
  96         if 'fee'in tx:
  97             print(f"  ; fee={tx['fee']}")
  98         for f in accounts.keys():
  99             if f in tx and Decimal(0) != tx[f]:
 100                 amount = tx[f]
 101                 print("  %-20s   %s BTC" % (accounts[f], format_float(amount)))
 102         if 'fee' in tx and Decimal(0) != tx['fee']:
 103             # Make sure to list fee used in several transactions only once.
 104             if 'fee' in tx and tx['txid'] in txidfee \
 105                and tx['fee'] == txidfee[tx['txid']]:
 106                 True
 107             else:
 108                 fee = tx['fee']
 109                 print("  %-20s   %s BTC" % (accounts['amount'], format_float(fee)))
 110                 print("  %-20s   %s BTC" % ('Expences:BTC-fee', format_float(-fee)))
 111                 txidfee[tx['txid']] = tx['fee']
 112
 113         if 'address' in tx and tx['address'] in addresses:
 114             print("  %s" % addresses[tx['address']])
 115         else:
 116             if 'generate' == tx['category']:
 117                 print("  Income:BTC-mining")
 118             else:
 119                 if amount < Decimal(0):
 120                     print(f"  Assets:unknown:sent:update-script-addr-{tx['address']}")
 121                 else:
 122                     print(f"  Assets:unknown:received:update-script-addr-{tx['address']}")
 123
 124         print()
 125         c = c + 1
 126     print("# Found %d transactions" % c)
 127     if limit == c:
 128         print(f"# Warning: Limit {limit} reached, consider increasing limit.")
 129
 130 def main():
 131     list_txs()
 132
 133 main()
 134 </pre></blockquote></p>
 135
 136 <p>It is more of a proof of concept, and I do not expect it to handle
 137 all edge cases, but it worked for me, and perhaps you can find it
 138 useful too.</p>
 139
 140 <p>To get a more interesting result, it is useful to map accounts sent
 141 to or received from to accounting accounts, using the
 142 <tt>addresses</tt> hash.  As these will be very context dependent, I
 143 leave out my list to allow each user to fill out their own list of
 144 accounts.  Out of the box, 'ledger reg BTC:main' should be able to
 145 show the amount of BTCs present in the wallet at any given time in the
 146 past.  For other and more valuable analysis, a account plan need to be
 147 set up in the <tt>addresses</tt> hash.  Here is an example
 148 transaction:</p>
 149
 150 <p><blockquote><pre>
 151 2024-03-07 17:00 Donated to good cause
 152     Assets:BTC:main                           -0.1 BTC
 153     Assets:BTC:main                       -0.00001 BTC
 154     Expences:BTC-fee                       0.00001 BTC
 155     Expences:donations                         0.1 BTC
 156 </pre></blockquote></p>
 157
 158 <p>It need a running Bitcoin Core daemon running, as it connect to it
 159 using <tt>bitcoin-cli listtransactions * 100000</tt> to extract the
 160 transactions listed in the Wallet.</p>
 161
 162 <p>As usual, if you use Bitcoin and want to show your support of my
 163 activities, please send Bitcoin donations to my address
 164 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 165 </div>
 166       <div class="tags">
 167
 168
 169         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>.
 170
 171
 172       </div>
 173     </div>
 174     <div class="padding"></div>
 175
 176     <div class="entry">
 177       <div class="title"><a href="https://people.skolelinux.org/pere/blog/RAID_status_from_LSI_Megaraid_controllers_using_free_software.html">RAID status from LSI Megaraid controllers using free software</a></div>
 178       <div class="date"> 3rd March 2024</div>
 179       <div class="body"><p>The last few days I have revisited RAID setup using the LSI
 180 Megaraid controller.  These are a family of controllers called PERC by
 181 Dell, and is present in several old PowerEdge servers, and I recently
 182 got my hands on one of these.  I had forgotten how to handle this RAID
 183 controller in Debian, so I had to take a peek in the
 184 <a href="https://wiki.debian.org/LinuxRaidForAdmins">Debian wiki page
 185 "Linux and Hardware RAID: an administrator's summary"</a> to remember
 186 what kind of software is available to configure and monitor the disks
 187 and controller.  I prefer Free Software alternatives to proprietary
 188 tools, as the later tend to fall into disarray once the manufacturer
 189 loose interest, and often do not work with newer Linux Distributions.
 190 Sadly there is no free software tool to configure the RAID setup, only
 191 to monitor it. RAID can provide improved reliability and resilience in
 192 a storage solution, but only if it is being regularly checked and any
 193 broken disks are being replaced in time.  I thus want to ensure some
 194 automatic monitoring is available.</p>
 195
 196 <p>In the discovery process, I came across a old free software tool to
 197 monitor PERC2, PERC3, PERC4 and PERC5 controllers, which to my
 198 surprise is not present in debian.  To help change that I created a
 199 <a href="https://bugs.debian.org/1065322">request for packaging of the
 200 megactl package</a>, and tried to track down a usable version.
 201 <a href="https://sourceforge.net/p/megactl/">The original project
 202 site</a> is on Sourceforge, but as far as I can tell that project has
 203 been dead for more than 15 years.  I managed to find a
 204 <a href="https://github.com/hmage/megactl">more recent fork on
 205 github</a> from user hmage, but it is unclear to me if this is still
 206 being maintained.  It has not seen much improvements since 2016.  A
 207 <a href="https://github.com/namiltd/megactl">more up to date
 208 edition</a> is a git fork from the original github fork by user
 209 namiltd, and this newer fork seem a lot more promising.  The owner of
 210 this github repository has replied to change proposals within hours,
 211 and had already added some improvements and support for more hardware.
 212 Sadly he is reluctant to commit to maintaining the tool and stated in
 213 <a href="https://github.com/namiltd/megactl/pull/1">my first pull
 214 request</A> that he think a new release should be made based on the
 215 git repository owned by hmage.  I perfectly understand this
 216 reluctance, as I feel the same about maintaining yet another package
 217 in Debian when I barely have time to take care of the ones I already
 218 maintain, but do not really have high hopes that hmage will have time
 219 to spend on it and hope namiltd will change his mind.</p>
 220
 221 <p>In any case, I created
 222 <a href="https://salsa.debian.org/debian/megactl">a draft package</a>
 223 based on the namiltd edition and put it under the debian group on
 224 salsa.debian.org.  If you own a Dell PowerEdge server with one of the
 225 PERC controllers, or any other RAID controller using the megaraid or
 226 megaraid_sas Linux kernel modules, you might want to check it out.  If
 227 enough people are interested, perhaps the package will make it into
 228 the Debian archive.</p>
 229
 230 <p>There are two tools provided, megactl for the megaraid Linux kernel
 231 module, and megasasctl for the megaraid_sas Linux kernel module. The
 232 simple output from the command on one of my machines look like this
 233 (yes, I know some of the disks have problems. :).</p>
 234
 235 <pre>
 236 # megasasctl
 237 a0       PERC H730 Mini           encl:1 ldrv:2  batt:good
 238 a0d0       558GiB RAID 1   1x2  optimal
 239 a0d1      3067GiB RAID 0   1x11 optimal
 240 a0e32s0     558GiB  a0d0  online   errs: media:0  other:19
 241 a0e32s1     279GiB  a0d1  online
 242 a0e32s2     279GiB  a0d1  online
 243 a0e32s3     279GiB  a0d1  online
 244 a0e32s4     279GiB  a0d1  online
 245 a0e32s5     279GiB  a0d1  online
 246 a0e32s6     279GiB  a0d1  online
 247 a0e32s8     558GiB  a0d0  online   errs: media:0  other:17
 248 a0e32s9     279GiB  a0d1  online
 249 a0e32s10    279GiB  a0d1  online
 250 a0e32s11    279GiB  a0d1  online
 251 a0e32s12    279GiB  a0d1  online
 252 a0e32s13    279GiB  a0d1  online
 253
 254 #
 255 </pre>
 256
 257 <p>In addition to displaying a simple status report, it can also test
 258 individual drives and print the various event logs.  Perhaps you too
 259 find it useful?</p>
 260
 261 <p>In the packaging process I provided some patches upstream to
 262 improve installation and ensure
 263 <ahref="https://github.com/namiltd/megactl/pull/2">a Appstream
 264 metainfo file is provided</a> to list all supported HW, to allow
 265 <a href="https://tracker.debian.org/isenkram">isenkram</a> to propose
 266 the package on all servers with a relevant PCI card.</p>
 267
 268 <p>As usual, if you use Bitcoin and want to show your support of my
 269 activities, please send Bitcoin donations to my address
 270 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 271
 272 </div>
 273       <div class="tags">
 274
 275
 276         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/isenkram">isenkram</a>, <a href="https://people.skolelinux.org/pere/blog/tags/raid">raid</a>.
 277
 278
 279       </div>
 280     </div>
 281     <div class="padding"></div>
 282
 283     <div class="entry">
 284       <div class="title"><a href="https://people.skolelinux.org/pere/blog/Frokostseminar_om_Noark_5_i_Oslo_tirsdag_2024_03_12.html">Frokostseminar om Noark 5 i Oslo tirsdag 2024-03-12</a></div>
 285       <div class="date">27th February 2024</div>
 286       <div class="body"><p>Nikita-prosjektet, der jeg er involvert, inviterer i samarbeid med
 287 Oslo Byarkiv, forskningsgruppen METAINFO og foreningen NUUG, til et
 288 frokostseminar om Noark 5 og Noark 5 Tjenestegrensesnitt tirsdag
 289 2024-03-12.  Seminaret finner sted ved Oslo byarkiv.  Vi håper å få
 290 til videostrømming via Internett av presentasjoner og paneldiskusjon.
 291 Oppdatert program og lenker til påmeldingsskjema er
 292 <a href="https://noark.codeberg.page/noark5-seminars/2023-03-12-noark-workshop.html">tilgjengelig
 293 fra Nikita-prosjektet</a>.  Arrangementet er gratis.
 294
 295 <p>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
 296 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
 297 til min adresse
 298 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>. Merk,
 299 betaling med bitcoin er ikke anonymt. :)</p>
 300 </div>
 301       <div class="tags">
 302
 303
 304         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/noark5">noark5</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="https://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 305
 306
 307       </div>
 308     </div>
 309     <div class="padding"></div>
 310
 311     <div class="entry">
 312       <div class="title"><a href="https://people.skolelinux.org/pere/blog/Welcome_out_of_prison__Mickey__hope_you_find_some_freedom_.html">Welcome out of prison, Mickey, hope you find some freedom!</a></div>
 313       <div class="date"> 1st January 2024</div>
 314       <div class="body"><p align="center"><img src="https://people.skolelinux.org/pere/blog/images/2024-01-01-mikke-verk-i-det-fri.jpeg"/></p>
 315
 316 <p>Today, the animation figure Mickey Mouse finally was released from
 317 the corporate copyright prison, as the 1928 movie
 318 <a href="https://en.wikipedia.org/wiki/Steamboat_Willie">Steamboat
 319 Willie</a> entered the public domain in USA.  This movie was the first
 320 public appearance of Mickey Mouse.  Sadly the figure is still on
 321 probation, thanks to trademark laws and a the Disney corporations
 322 powerful pack of lawyers, as described in the 2017 article
 323 in <a href="https://priceonomics.com/how-mickey-mouse-evades-the-public-domain/">"How
 324 Mickey Mouse Evades the Public Domain"</a> from Priceonomics.  On the
 325 positive side, the primary driver for repeated extentions of the
 326 duration of copyright has been Disney thanks to Mickey Mouse and the
 327 2028 movie, and as it now in the public domain I hope it will cause
 328 less urge to extend the already unreasonable long copyright
 329 duration.</p>
 330
 331 <p>The first book I published, the 2004 book <a
 332 href="https://free-culture.cc/">"Free Culture" by Lawrence Lessig</a>,
 333 published 2015 in
 334 <a href="https://people.skolelinux.org/pere/publisher/#frikultur">English,
 335 French and Norwegian Bokmål</a>, touch on the story of Disney pushed
 336 for extending the copyright duration in USA.  It is a great book
 337 explaining problems with the current copyright regime and why we need
 338 Creative Commons movement, and I strongly recommend everyone to read
 339 it.</p>
 340
 341 <p>This movie (with
 342 <a href="https://www.imdb.com/title/tt0019422/">IMDB ID tt0019422</a>)
 343 is now available from the Internet Archive.  Two copies have been
 344 uploaded so far, one uploaded
 345 <a href="https://archive.org/details/SteamboatWillie">2015-11-04</a>
 346 (<a href="https://archive.org/download/SteamboatWillie/SteamboatWillie_archive.torrent">torrent</a>)
 347 and the other
 348 <a href="https://archive.org/details/steamboat-willie-mickey">2023-01-01</a>
 349 (<a href="https://archive.org/download/steamboat-willie-mickey/steamboat-willie-mickey_archive.torrent">torrent</a>) - see
 350 <a href="https://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_still_going_strong__new_upload_2_14_4.html">VLC
 351 bittorrent plugin</a> for streaming the video using the torrent link.
 352 I am very happy to see
 353 <a href="https://people.skolelinux.org/pere/blog/Legal_to_share_more_than_16_000_movies_listed_on_IMDB_.html">the
 354 number of public domain movies</a> increasing.  I look forward to
 355 when those are the majority.  Perhaps it will reduce the urge of the
 356 copyright industry to control its customers.</p>
 357
 358 <p>A more
 359 <a href="https://publicdomainreview.org/features/entering-the-public-domain/2024/">comprehensive
 360 list of works entering the public domain in 2024</a> is available from
 361 the Public Domain Review.</p>
 362
 363 <p>As usual, if you use Bitcoin and want to show your support of my
 364 activities, please send Bitcoin donations to my address
 365 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 366 </div>
 367       <div class="tags">
 368
 369
 370         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri</a>.
 371
 372
 373       </div>
 374     </div>
 375     <div class="padding"></div>
 376
 377     <div class="entry">
 378       <div class="title"><a href="https://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_still_going_strong__new_upload_2_14_4.html">VLC bittorrent plugin still going strong, new upload 2.14-4</a></div>
 379       <div class="date">31st December 2023</div>
 380       <div class="body"><p>The other day I uploaded a new version of
 381 <a href="https://tracker.debian.org/pkg/vlc-plugin-bittorrent">the VLC
 382 bittorrent plugin</a> to Debian, version 2.14-4, to fix a few
 383 packaging issues.  This plugin extend VLC allowing it to stream videos
 384 directly from a bittorrent source using both torrent files and magnet
 385 links, as easy as using a HTTP or local file source.  I believe such
 386 protocol support is a vital feature in VLC, allowing efficient
 387 streaming from sources such at the 11 million movies in
 388 <a href="https://archive.org/">the Internet Archive</a>.  Bittorrent is
 389 one of the most efficient content distribution protocols on the
 390 Internet, without centralised control, and should be used more.</p>
 391
 392 <p>The new version is now both in Debian Unstable and Testing, as well
 393 as Ubuntu.  While looking after the package, I decided to ask the VLC
 394 upstream community if there was any hope to get Bittorrent support
 395 into the official VLC program, and was very happy to learn that
 396 someone is already working on it.  I hope we can see some fruits of
 397 that labour next year, but do not hold my breath.  In the mean time we
 398 can use the plugin, which is already
 399 <a href="https://qa.debian.org/popcon.php?package=vlc-plugin-bittorrent">installed
 400 by 0.23 percent of the Debian population</a> according to
 401 popularity-contest.  It could use a new upstream release, and I hope
 402 the upstream developer soon find time to polish it even more.</p>
 403
 404 <p>It is worth noting that the plugin store the downloaded files in
 405 <tt>~/Downloads/vlc-bittorrent/</tt>, which can quickly fill up the
 406 user home directory during use.  Users of the plugin should keep an
 407 eye with disk usage when streaming a bittorrent source.</p>
 408
 409 <p>As usual, if you use Bitcoin and want to show your support of my
 410 activities, please send Bitcoin donations to my address
 411 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 412 </div>
 413       <div class="tags">
 414
 415
 416         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>.
 417
 418
 419       </div>
 420     </div>
 421     <div class="padding"></div>
 422
 423     <div class="entry">
 424       <div class="title"><a href="https://people.skolelinux.org/pere/blog/_N_r__p___blir__p_____Et_reservoar_av_tegn_sett_fra_depotet__i_tidsskriftet_Aksess.html">«Når «på» blir «pÃ¥»: Et reservoar av tegn sett fra depotet» i tidsskriftet Aksess</a></div>
 425       <div class="date">15th November 2023</div>
 426       <div class="body"><p>For noen uker siden skrev en kamerat og meg
 427 <a href="https://www.aksess-tidsskrift.no/fordypning/175530">en
 428 artikkel om tegnsett</a> i
 429 <a href="https://www.aksess-tidsskrift.no/">arkivtidsskriftet
 430 Aksess</a> både på web og i papirutgave nr. 3 2023.  Her er det som
 431 nettopp ble publisert.</p>
 432
 433 <blockquote>
 434
 435 <p><strong>Når «på» blir «pÃ¥»: Et reservoar av tegn sett fra
 436 depotet</strong></p>
 437
 438 <p>av Thomas Sødring og Petter Reinholdtsen</p>
 439
 440 <p>De færreste av oss tenker over hva som skjer dypere i datamaskinen
 441 mens vi sitter der og skriver noe på tastaturet. Når du trykker på
 442 tasten «Å», så vises bokstaven Å. Men noen ganger blir det
 443 feil. Hvorfor det – og hva er viktig å være klar over i
 444 arkivsammenheng?</p>
 445
 446 <p>Dersom bokstaver tolkes forskjellig mellom systemer, blir det fort
 447 rot, dette kalles mojibake blant kjennere, etter det japanske
 448 uttrykket for tegnomforming. Det er en lang historie her som tidvis
 449 har vært preget av rot.  Noen husker kanskje tilbake til en tid der
 450 bokstavene æ, ø og å ofte var ødelagt i e-poster – et klassisk
 451 eksempel på tegnsettproblemstilling.</p>
 452
 453 <p id="tegnsett_access_nå_og_før"><strong>«Nå» og «før»</strong></p>
 454
 455 <p>Tid er et skjult problem for depot fordi vi danner dokumentasjon i
 456 en kontekst som er preget av å være «nå».  Vår forståelse av verden og
 457 bruken av teknologi er utgangspunktet for denne konteksten. Tenk selv
 458 hvordan verden har utviklet seg de siste 20 årene, hva samfunnet er
 459 opptatt av, og hvordan vi bruker teknologi i hverdagen. Tid er et
 460 skjult problem fordi når vi trekker dokumentasjon ut av systemer og
 461 deponerer for langtidsbevaring, er konteksten til materialet «nå», men
 462 verden går videre. Ettersom teknologien og måten vi bruker den på,
 463 utvikler seg, blir «nå» til «før», og dokumentasjonen befinner seg
 464 snart i en «før»-kontekst.</p>
 465
 466 <p>Dette med «før» og «nå» i forhold til dokumentasjonens kontekst er
 467 noe vi er veldig lite bevisste på, men det er en problemstilling
 468 depotarkivene eier og forvalter.  En av disse utfordringene er hvorfor
 469 «Ø» ikke nødvendigvis er det samme som «Ø», og hvorfor det i det hele
 470 tatt gir mening å si noe sånt. Vi snakker her om noe som heter
 471 tegnsett, som er en avtalt måte å representere bokstaver, tall og
 472 andre symboler på slik at vi på en feilfri måte kan utveksle tekst
 473 mellom datasystemer.</p>
 474
 475 <p>Tegnsettproblemstillingen er satt sammen av fire fasetter;
 476 repertoar, representasjon, koding og uttegning.</p>
 477
 478 <p id="tegnsett_access_repertoarer"><strong>Repertoarer</strong></p>
 479
 480 <p>Repertoar er en samling med tegn og symboler som kan
 481 representeres. Tenk norsk alfabet eller japanske piktogrammer, men
 482 også matematiske og elektroniske symboler. Bokstaven «stor a» kan være
 483 en oppføring i et slikt repertoar. For å kunne brukes i en datamaskin
 484 trenger hver oppføring i et slikt repertoar en representasjon, hvilket
 485 i datamaskinsammenheng betyr at det tilordnes et tall. Tallet kan
 486 lagres på ulike vis i en eller flere kodingsformater. For eksempel kan
 487 en skrive tallet ti som både 10, X og A, i henholdsvis
 488 titallssystemet, romertallssystemet og sekstentallssystemet.</p>
 489
 490 <p>Hvis en skal kunne lese inn filer og vite hvilket tall og hvilken
 491 representasjon og instans i et repertoar det er snakk om, så må en
 492 vite hvordan tallet er kodet. Sist, men ikke minst, for å kunne bruke
 493 symbolet til noe må det kunne være kjent hvordan det skal se ut eller
 494 tegnes på ark. Det finnes utallige skrifttyper med norske bokstaver,
 495 alle litt forskjellige, og skal en kunne tegne en stor A på skjermen,
 496 så må datamaskinen vite hva den skal tegne. Skrifttyper inneholder
 497 informasjon om hvordan ulike tall skal tegnes. De inneholder ikke
 498 alltid alle symbolene som er brukt i en tekst, hvilket gjør at ikke
 499 alle forståtte tegn vil kunne vises på skjerm eller ark.</p>
 500
 501 <p>Hver av disse fasettene må være avklart for å kunne ta vare på og vise
 502 frem tekst med en datamaskin. Kombinasjon av repertoar, representasjon
 503 og koding er det en kaller et tegnsett. Kombinasjonen av
 504 representasjon og uttegning kalles en skrifttype. De fleste
 505 skrifttyper har også informasjon om repertoar, men det finnes
 506 skrifttyper som kun kobler mellom tallkode og uttegning, uten å
 507 fortelle noe om hvordan tallkodene egentlig skal tolkes.</p>
 508
 509 <p id="tegnsett_access_fra_ascii_til_iso_8859"><strong>Fra ASCII til ISO-8859</strong></p>
 510
 511 <p>Vi begynner historien med ASCII (American Standard Code for
 512 Information Interchange) som har en historie som spores tilbake til
 513 1963. Utgangspunktet til ASCII var at det kunne kode opp til 128
 514 forskjellige symboler i vanlig bruk i USA. De visuelle symbolene i
 515 ASCII er de små og store bokstavene (a til z og A til Z), tall (0 til
 516 9) og tegnsettingssymboler (for eksempel semikolon, komma og
 517 punktum). ASCII har også noen usynlige symboler som ble brukt for
 518 bl.a. kommunikasjon. Før ASCII var det for eksempel teleks-tegnsett
 519 med plass til bare 32 tegn og EBCDIC med plass til 256 tegn, alle med
 520 en helt annen rekkefølge på symbolene enn ASCII, men de har vært lite
 521 brukt de siste femti årene. Et eksempel på noen utvalgte symboler i
 522 repertoaret til ASCII vises i tabell 1.</p>
 523
 524 <table align="center" width="50%">
 525
 526 <caption>Tabell 1. Eksempel på utvalgte symboler hentet fra
 527 ASCII-tegnsettet. Kolonnen «Binær» viser symbolets verdi i
 528 totallssystemet (1 og 0 tall), mens kolonnen «Desimal» viser symbolets
 529 verdi i titallssystemet.</caption>
 530
 531 <tbody>
 532 <tr>
 533 <th>Grafisk</th>
 534 <th>Binær</th>
 535 <th>Desimal</th>
 536 </tr>
 537 <tr>
 538 <td>A</td>
 539 <td>1000001</td>
 540 <td align="right">65</td>
 541 </tr>
 542 <tr>
 543 <td>M</td>
 544 <td>1001101</td>
 545 <td align="right">77</td>
 546 </tr>
 547 <tr>
 548 <td>Z</td>
 549 <td>1011010</td>
 550 <td align="right">90</td>
 551 </tr>
 552 <tr>
 553 <td>a</td>
 554 <td>1100001</td>
 555 <td align="right">97</td>
 556 </tr>
 557 <tr>
 558 <td>m</td>
 559 <td>1101101</td>
 560 <td align="right">109</td>
 561 </tr>
 562 <tr>
 563 <td>z</td>
 564 <td>1111010</td>
 565 <td align="right">122</td>
 566 </tr>
 567 <tr>
 568 <td>0</td>
 569 <td>0110000</td>
 570 <td align="right">48</td>
 571 </tr>
 572 <tr>
 573 <td>9</td>
 574 <td>0111001</td>
 575 <td align="right">58</td>
 576 </tr>
 577 <tr>
 578 <td>;</td>
 579 <td>0111011</td>
 580 <td align="right">59</td>
 581 </tr>
 582 </tbody>
 583 </table>
 584
 585 <p>Det opprinnelige ASCII-tegnsettet ble også omtalt som ASCII-7 og
 586 brukte 7 bits (0 og 1) for å representere symboler. Datamaskiner er
 587 ofte konfigurert til å jobbe med enheter der bits er gruppert som 4
 588 eller 8 bits . Det lå en mulighet i å ta i bruk bit åtte. En slik
 589 endring ville gjøre det mulig for datamaskiner å øke antall symboler
 590 de kunne representere, noe som ga en økning fra 128 forskjellige
 591 symboler til 256 forskjellige symboler. Det ble åpnet for å innlemme
 592 de nordiske bokstavene sammen med ASCII, og dette ble etter hvert
 593 standardisert som ISO-8859-1. Tabell 2 viser deler av ISO-8859-1 som
 594 støtter de norske bokstavene.</p>
 595
 596 <p>Det sier seg selv at muligheten til å representere inntil 256 symboler
 597 ikke holder når vi snakker om en global verden, og det ble gjort et
 598 standardiseringsløp som tok utgangspunkt i ASCII-7 med en utvidelse
 599 til å bruke den åttende biten for ulike språkgrupper. Denne standarden
 600 heter ISO-8859 og er inndelt i opptil 16 varianter, altså fra
 601 ISO-8859-1 til ISO-8859-16.</p>
 602
 603 <table align="center" width="50%">
 604
 605 <caption>Tabell 2. Koding av de norske symbolene slik de er definert i
 606 ISO-8859-1 tegnsettet.</caption>
 607
 608 <tbody>
 609 <tr>
 610 <th>Grafisk</th>
 611 <th>Binær</th>
 612 <th>Desimal</th>
 613 </tr>
 614 <tr>
 615 <td>Æ</td>
 616 <td>11000110</td>
 617 <td align="right">198</td>
 618 </tr>
 619 <tr>
 620 <td>Ø</td>
 621 <td>11011000</td>
 622 <td align="right">216</td>
 623 </tr>
 624 <tr>
 625 <td>Å</td>
 626 <td>11000101</td>
 627 <td align="right">197</td>
 628 </tr>
 629 <tr>
 630 <td>æ</td>
 631 <td>11100110</td>
 632 <td align="right">230</td>
 633 </tr>
 634 <tr>
 635 <td>ø</td>
 636 <td>11111000</td>
 637 <td align="right">248</td>
 638 </tr>
 639 <tr>
 640 <td>å</td>
 641 <td>11100101</td>
 642 <td align="right">229</td>
 643 </tr>
 644 </tbody>
 645 </table>
 646
 647 <p>Norske tegn er definert i ISO-8859-1, som også omtales som Latin 1, de
 648 fleste samiske tegn er definert i ISO-8859-4 (Latin 4) mens tilgang
 649 til €-symbolet kom med ISO-8859-15 (Latin 9). ISO-8859-15 er en
 650 revisjon av ISO-8859-1 som fjerner noen lite brukte symboler og
 651 erstatter bokstaver som er mer brukt, og introduserer €-symbolet.  Det
 652 er viktig å merke at alle ISO-8859-variantene har overlapp med
 653 ASCII-7, noe som ga samvirke med de engelskspråklige landene som ikke
 654 trengte å gjøre noe. Det innebærer også at de første 128 verdiene i
 655 ISO-8859-variantene representerer de samme symbolene. Det er først når
 656 du kommer til tolkningen av de resterende 128 verdiene med nummer 128
 657 til 255, at det oppsto tolkningsutfordringer mellom
 658 ISO-8859-variantene.</p>
 659
 660 <p>ISO-8859-verdenen fungerte godt så lenge tegnsettet som ble brukt når
 661 innhold ble skapt, også ble brukt når innhold ble gjengitt og du ikke
 662 trengte å kombinere innhold fra forskjellige tegnsett i samme
 663 dokument.  Utfordringen med bruken av ISO-8859-variantene ble raskt
 664 tydelig i en mer globalisert verden med utveksling av tekst på tvers
 665 av landegrenser der tekstlig innhold i dokumenter, e-poster og
 666 websider kunne bli skrevet med ett tegnsett og gjengitt med et annet
 667 tegnsett.</p>
 668
 669 <table align="center" width="60%">
 670
 671 <caption>Tabell 3. Viser tolkning av verdiene som er tilegnet de
 672 norske symbolene i ISO-8859-1 i de andre ISO 8859-variatene. Merk
 673 ISO-8859-12 ikke finnes da arbeidet ble avsluttet.<sup>[<a id="tegnsett_access_footnoteref_1" href="#tegnsett_access_footnotedef_1" title="View footnote.">1</a>]</sup></caption>
 674
 675 <tbody>
 676 <tr>
 677 <th>Binærverdi</th>
 678 <th>1</th>
 679 <th>2</th>
 680 <th>3</th>
 681 <th>4</th>
 682 <th>5</th>
 683 <th>6</th>
 684 <th>7</th>
 685 <th>8</th>
 686 <th>9</th>
 687 <th>10</th>
 688 <th>11</th>
 689 <th>13</th>
 690 <th>14</th>
 691 <th>15</th>
 692 <th>16</th>
 693 </tr>
 694 <tr>
 695 <td>11000110</td>
 696 <td>Æ</td>
 697 <td>Ć</td>
 698 <td>Ĉ</td>
 699 <td>Æ</td>
 700 <td>Ц</td>
 701 <td>ئ</td>
 702 <td>Ζ</td>
 703 <td></td>
 704 <td>Æ</td>
 705 <td>Æ</td>
 706 <td>ฦ</td>
 707 <td>Ę</td>
 708 <td>Æ</td>
 709 <td>Æ</td>
 710 <td>Æ</td>
 711 </tr>
 712 <tr>
 713 <td>11011000</td>
 714 <td>Ø</td>
 715 <td>Ř</td>
 716 <td>Ĝ</td>
 717 <td>Ø</td>
 718 <td>и</td>
 719 <td>ظ</td>
 720 <td>Ψ</td>
 721 <td></td>
 722 <td>Ø</td>
 723 <td>Ø</td>
 724 <td>ุ</td>
 725 <td>Ų</td>
 726 <td>Ø</td>
 727 <td>Ø</td>
 728 <td>Ű</td>
 729 </tr>
 730 <tr>
 731 <td>11000101</td>
 732 <td>Å</td>
 733 <td>Ĺ</td>
 734 <td>Ċ</td>
 735 <td>Å</td>
 736 <td>Х</td>
 737 <td>إ</td>
 738 <td>Ε</td>
 739 <td></td>
 740 <td>Å</td>
 741 <td>Å</td>
 742 <td>ล</td>
 743 <td>Å</td>
 744 <td>Å</td>
 745 <td>Å</td>
 746 <td>Ć</td>
 747 </tr>
 748 <tr>
 749 <td>11100110</td>
 750 <td>æ</td>
 751 <td>ć</td>
 752 <td>ĉ</td>
 753 <td>æ</td>
 754 <td>ц</td>
 755 <td>ن</td>
 756 <td>ζ</td>
 757 <td>ז</td>
 758 <td>æ</td>
 759 <td>æ</td>
 760 <td>ๆ</td>
 761 <td>ę</td>
 762 <td>æ</td>
 763 <td>æ</td>
 764 <td>v</td>
 765 </tr>
 766 <tr>
 767 <td>11111000</td>
 768 <td>ø</td>
 769 <td>ř</td>
 770 <td>ĝ</td>
 771 <td>ø</td>
 772 <td>ј</td>
 773 <td></td>
 774 <td>ψ</td>
 775 <td>ר</td>
 776 <td>ø</td>
 777 <td>ø</td>
 778 <td>๘</td>
 779 <td>ų</td>
 780 <td>ø</td>
 781 <td>ø</td>
 782 <td>ű</td>
 783 </tr>
 784 <tr>
 785 <td>11100101</td>
 786 <td>å</td>
 787 <td>ĺ</td>
 788 <td>ċ</td>
 789 <td>å</td>
 790 <td>х</td>
 791 <td>م</td>
 792 <td>ε</td>
 793 <td>ו</td>
 794 <td>å</td>
 795 <td>å</td>
 796 <td>ๅ</td>
 797 <td>å</td>
 798 <td>å</td>
 799 <td>å</td>
 800 <td>ć</td>
 801 </tr>
 802 </tbody>
 803 </table>
 804
 805 <p>Denne problemstillingen er illustrert i tabell 3, der vi ser verdiene
 806 tilegnet de norske symbolene i ISO-8859-1 i kolonne «1». I de øvrige
 807 kolonnene ser vi hvilket symbol verdien får i de andre
 808 ISO-8859-variantene. Tar vi utgangspunkt i tabell 3, kan vi se at
 809 ordet lærlingspørsmål gjengitt med ISO-8859-2 (kolonne 2) blir
 810 lćrlingspřrsmĺl, mens det blir lζrlingspψrsmεl med ISO- 8859-7
 811 (kolonne 7). Med ISO-8859-2 blir «æ» til «ć», «ø» til «ř» og «å» til
 812  «ĺ». I ISO-8859-7 blir «æ» til «ζ», «ø» til «ψ», mens «å» blir «ε».</p>
 813
 814 <p>Det er egentlig ingen utfordring med dette så lenge du vet hvilket
 815 tegnsett innholdet ditt er representert med, og det ikke har skjedd
 816 omforminger som du ikke er klar over. Det er det siste som er
 817 problematisk, spesielt de datasystemene som har vært i bruk de siste
 818 20 årene, som ikke har noe innebygd funksjonalitet for å forvalte
 819 tegnsettproblematikken. Et godt eksempel på dette er
 820 Microsoft-tegnsettet Windows-1252, som ble forvekslet som 100 %
 821 kompatibel med ISO-8859-1, men hadde byttet ut plassene fra 127 til
 822 159. Historisk vil det finnes en del variasjon i hvilket tegnsett som
 823 har vært i bruk, og hvor vellykket konvertering mellom tegnsett har
 824 vært.</p>
 825
 826 <p id="tegnsett_access_unicode_som_løsning"><strong>Unicode som løsning</strong></p>
 827
 828 <p>Tegnsettforvirring ble etter hvert et irritasjonsmoment og
 829 samvirkeproblem. Ofte fikk man en e-post der æøå var erstattet av rare
 830 symboler fordi e-posten hadde vært innom et eller annet datasystem som
 831 ikke brukte samme tegnsett.</p>
 832
 833 <p>For å løse dette samvirkeproblemet for tegnsett ble det startet et
 834 arbeid og en ny standard så dagens lys etter hvert. Denne standarden
 835 fikk navnet Unicode (ISO/ IEC 10646) og skulle resultere i et tegnsett
 836 som alle skulle være enige om. Unicode er et repertoar og en
 837 representasjon, dvs. navngivning og tilordning av tallverdi til alle
 838 symboler i bruk i verden i dag.  Oppføringer i Unicode skrives gjerne
 839 U+XXXX der XXXX er tallkoden i sekstentallssystemet som oppføringen
 840 har i Unicode-katalogen. Her finner vi tegn brukt av både levende og
 841 døde språk, konstruerte språk, tekniske symboler, morsomme tegninger
 842 (såkalte emojier) og tegn ingen vet hva betyr eller skal brukes
 843 til. Et morsomt eksempel er i nettartikkelen: U+237C ⍼ RIGHT ANGLE
 844 WITH DOWNWARDS ZIGZAG ARROW, av Jonathan Chan.<sup>[<a id="tegnsett_access_footnoteref_2" href="#tegnsett_access_footnotedef_2" title="View footnote.">2</a>]</sup></p>
 845
 846 <p>Sammen med Unicode kom det tre måter å kode disse tallene på; UTF-8,
 847 UTF-16 og UTF-32. Av datatekniske årsaker er UTF-8 mye brukt, spesielt
 848 når det gjelder utveksling av tekst over Internett, mens UTF-16 er
 849 brukt en del til tekstfiler lagret på Windows. En utfordring med
 850 Unicode og UTF-variantene er at disse gir flere måter å kode samme
 851 symbol på med en kombinasjonsmekanisme. Dette kan gi utfordringer ved
 852 søk, hvis en skal søke etter et ord som har ett eller flere symboler
 853 som kan skrives på ulikt vis, så er det ikke sikkert at søkesystemet
 854 vil finne alle forekomster. For eksempel kan bokstaven U+00F8 «Latin
 855 Small Letter O with Stroke» kodes som den tradisjonelle norske tegnet
 856 ø, men også som o kombinert med skråstrek U+0338. Begge deler er
 857 gyldig bruk av Unicode, selv om det er tradisjon for å foretrekke å
 858 «normalisere» kombinasjoner som enkelttegn der det er mulig, nettopp
 859 for å forenkle søk.</p>
 860
 861 <p id="tegnsett_access_bare_unicode_fremover"><strong>Bare Unicode fremover</strong></p>
 862
 863 <p>Forvaltningens bruk av tegnsett er regulert i Forskrift om
 864 IT-standarder i offentlig forvaltning<sup>[<a id="tegnsett_access_footnoteref_3" href="#tegnsett_access_footnotedef_3" title="View footnote.">3</a>]</sup>. Her står det: «Ved all
 865 utveksling av informasjon mellom forvaltningsorganer og fra
 866 forvaltningsorgan til innbyggere og næringsliv skal tegnsettstandarden
 867 ISO/IEC 10646 representert ved UTF8 benyttes.»  Det er forskjellige
 868 bruksområder til UTF-8, UTF-16 og UTF-32, men UTF-8 er kodingen vi
 869 kjenner mest til.  Det er flere grunner at UTF-8 «vant» konkurransen
 870 til å bli den utvalgte. Den kanskje viktigste er at UTF-8 er fullt
 871 samvirkende med ASCII-7, slik at den engelskspråklige delen av verden
 872 kunne rulle ut UTF-8 uten å merke noe forskjell. En tekstfil med kun
 873 ASCII-tekst vil være identisk på disken hvis den lagres som UTF-8 og
 874 ASCII. UTF-16 og UTF-32 byr på noen optimaliseringer som gjør dem
 875 relevant for spesifikke problemområder, men for det meste vil vi aldri
 876 oppleve disse standardene på nært hold i hverdagen. Det er uansett kun
 877 bruken av UTF-8 som er lovregulert i Norge.</p>
 878
 879 <p>Det er ikke slik at hele verden bruker ISO/IEC 10646 og UTF-8. Kina
 880 har egne standarder for tegnsett, mye brukt er GB 18030, som er
 881 Unicode med en annen koding enn UTF-8, mens Taiwan og andre asiatiske
 882 land gjerne bruker Big5 eller andre tegnsett.</p>
 883
 884 <p>UTF-8 er dominerende i Norge, men det er tidsperioder der forskjellige
 885 datasystemer utvekslet data i henhold til ISO-8859-1, ISO-8859-15,
 886 Windows-1252, Codepage 865 og ISO-646-60 / Codepage 1016 mens
 887 overgangen til UTF-8 pågikk. Det er ikke slik at et datasystem enkelt
 888 kan tvinges til å bruke et tegnsett, da det er flere lag i et
 889 datasystem som må settes opp til å bruke riktig tegnsett, og
 890 tegnsettproblemet fort oppstår når det er et eller annet i
 891 datasystemet som bruker feil tegnsett.</p>
 892
 893 <p>Et klassisk eksempel på problemet er en utveksling av tekst mellom to
 894 systemer der teksten i utgangspunktet er kodet i UTF-8, men går
 895 gjennom noe som er ISO-8859-1 underveis. Dette kan vises med at ordet
 896 «på» i et slik scenario ender opp som «pÃ¥». Det er mulig å spore
 897 dette tilbake til verdiene symbolene er tilordnet i tegnsettene. «på»
 898 blir til «pÃ¥» fordi «å» i UTF-8 er representert med U+C3AF, og dersom
 899 vi ser på hva disse verdiene representerer, ser vi at
 900 sekstentallssystemverdien C3 er 1100 0011 i totallssystemet og
 901 symbolet med dette tallet i ISO-8859-1 er Ã.</p>
 902
 903 <p>Vi ser det samme med sekstentallssystemverdien A5, som er 1010 0101 i
 904 totallssystemet, og tilsvarende symbol i ISO-8859-1 er ¥. Slik
 905 mojibake kan lett skje hvis «på» i utgangspunktet var representert med
 906 UTF-8, men ble behandlet med et system som bruker ISO-8859-1. Det er
 907 ingen automatikk i å fange opp slike ødeleggelser mens tekstlig
 908 innhold utveksles mellom datasystemer.</p>
 909
 910 <p>En utfordring for depotarkivene er at bruken av tegnsett ikke alltid
 911 har vært regulert, og at det kan finnes flere dokumentasjonssamlinger
 912 som er opprettet med varierende tegnsett før gjeldende forskrift
 913 inntraff – uten at det er mulig å avlede fra filene hvilket tegnsett
 914 som ble brukt. Et eksempel på dette er €-symbolet, som kom først etter
 915 at ISO-8859-1 var tatt i bruk. Det kan bli en utfordring for et
 916 depotarkiv, men så lenge det er kjent hvilket tegnsett var i bruk, så
 917 bør det gå bra.  Riksarkivarens
 918 forskrift<sup>[<a id="tegnsett_access_footnoteref_4" href="#tegnsett_access_footnotedef_4" title="View footnote.">4</a>]</sup>
 919 formaliserer dette ved å kreve følgende:</p>
 920
 921 <blockquote>
 922 <p>§ 5-11. Tegnsett i arkivuttrekk</p>
 923
 924 <ol>
 925   <li>Arkivuttrekk og medfølgende struktur- og innholdsbeskrivelser skal
 926       overføres som ren tekst i ukryptert form, og benytte godkjent
 927       tegnsett.</li>
 928
 929   <li>Godkjente tegnsett er:
 930     <ol>
 931       <li>Unicode UTF-8<br>
 932           (ISO/IEC 10646-1:2000 Annex D)</li>
 933       <li>ISO 8859-1:1998, Latin 1</li>
 934       <li>ISO 8859-4:1998, Latin 4 for samiske tegn.</li>
 935     </ol></li>
 936
 937   <li>Andre tegnsett aksepteres bare etter avtale med Arkivverket.</li>
 938 </ol>
 939 </blockquote>
 940
 941 <p id="tegnsett_access_ditt_ansvar"><strong>Ditt ansvar</strong></p>
 942
 943 <p>På mange måter burde ikke tegnsett være et problem i 2023, men sånn er
 944 det nok ikke. Land som har oppgradert til UTF-8 som primærtegnsett for
 945 utveksling av tekstlig innhold, begrenser problematikken betraktelig,
 946 men globalt sett så er tegnsettutfordringen ikke løst fordi ikke alle
 947 er enige om å bruke samme tegnsett.  Det kan være geopolitiske eller
 948 kulturelle hensyn som ligger til grunn for dette.</p>
 949
 950 <p>Det er uansett verdt å merke at selv om bruken av UTF-8 skulle bli
 951 100% utbredt, så er det et historisk perspektiv (ASCII-7,
 952 ISO-8859-variantene, UTF-8) her som gjør tegnsett til et problemområde
 953 arkivarene må forstå og håndtere.  Som danningsarkivar har du et
 954 ansvar for å vite hvilket tegnsett systemene og databasene dere
 955 forvalter, er i samsvar med. Det er noe IT-avdelingen din eller
 956 programvareleverandørene enkelt skal kunne svare på, og svaret skal
 957 være UTF-8 for alle nye systemer.</p>
 958
 959 <hr>
 960
 961 <p id="tegnsett_access_footnotedef_1"><a href="#tegnsett_access_footnoteref_1">1</a>. Tegnsettkilde <a href="https://en.wikipedia.org/wiki/ISO/IEC_8859">https://en.wikipedia.org/wiki/ISO/IEC_8859</a></p>
 962
 963 <p id="tegnsett_access_footnotedef_2"><a href="#tegnsett_access_footnoteref_2">2</a>. <a href="https://ionathan.ch/2022/04/09/angzarr.html">https://ionathan.ch/2022/04/09/angzarr.html</a></p>
 964
 965 <p id="tegnsett_access_footnotedef_3"><a href="#tegnsett_access_footnoteref_3">3</a>. <a href="https://lovdata.no/dokument/SF/forskrift/2013-04-05-959/%C2%A78#%C2%A78">https://lovdata.no/dokument/SF/forskrift/2013-04-05-959/%C2%A78#%C2%A78</a></p>
 966
 967 <p id="tegnsett_access_footnotedef_4"><a href="#tegnsett_access_footnoteref_4">4</a>. <a href="https://lovdata.no/forskrift/2017-12-19-2286/§5-11">https://lovdata.no/forskrift/2017-12-19-2286/§5-11</a></p>
 968
 969 </blockquote>
 970
 971 <p>For øvrig burde varsleren Edward Snowden få politisk asyl i Norge.</p>
 972
 973 <p>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
 974 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
 975 til min adresse
 976 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>. Merk,
 977 betaling med bitcoin er ikke anonymt. :)</p>
 978 </div>
 979       <div class="tags">
 980
 981
 982         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/noark5">noark5</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 983
 984
 985       </div>
 986     </div>
 987     <div class="padding"></div>
 988
 989     <div class="entry">
 990       <div class="title"><a href="https://people.skolelinux.org/pere/blog/New_and_improved_sqlcipher_in_Debian_for_accessing_Signal_database.html">New and improved sqlcipher in Debian for accessing Signal database</a></div>
 991       <div class="date">12th November 2023</div>
 992       <div class="body"><p>For a while now I wanted to have direct access to the
 993 <a href="https://signal.org/">Signal</a> database of messages and
 994 channels of my Desktop edition of Signal.  I prefer the enforced end
 995 to end encryption of Signal these days for my communication with
 996 friends and family, to increase the level of safety and privacy as
 997 well as raising the cost of the mass surveillance government and
 998 non-government entities practice these days.  In August I came across
 999 a nice
1000 <a href="https://www.yoranbrondsema.com/post/the-guide-to-extracting-statistics-from-your-signal-conversations/">recipe
1001 on how to use sqlcipher to extract statistics from the Signal
1002 database</a> explaining how to do this.  Unfortunately this did not
1003 work with the version of sqlcipher in Debian.  The
1004 <a href="http://tracker.debian.org/sqlcipher/">sqlcipher</a>
1005 package is a "fork" of the sqlite package with added support for
1006 encrypted databases.  Sadly the current Debian maintainer
1007 <a href="https://bugs.debian.org/961598">announced more than three
1008 years ago that he did not have time to maintain sqlcipher</a>, so it
1009 seemed unlikely to be upgraded by the maintainer.  I was reluctant to
1010 take on the job myself, as I have very limited experience maintaining
1011 shared libraries in Debian.  After waiting and hoping for a few
1012 months, I gave up the last  week, and set out to update the package.  In
1013 the process I orphaned it to make it more obvious for the next person
1014 looking at it that the package need proper maintenance.</p>
1015
1016 <p>The version in Debian was around five years old, and quite a lot of
1017 changes had taken place upstream into the Debian maintenance git
1018 repository.  After spending a few days importing the new upstream
1019 versions, realising that upstream did not care much for SONAME
1020 versioning as I saw library symbols being both added and removed with
1021 minor version number changes to the project, I concluded that I had to
1022 do a SONAME bump of the library package to avoid surprising the
1023 reverse dependencies.  I even added a simple
1024 autopkgtest script to ensure the package work as intended.  Dug deep
1025 into the hole of learning shared library maintenance, I set out a few
1026 days ago to upload the new version to Debian experimental to see what
1027 the quality assurance framework in Debian had to say about the result.
1028 The feedback told me the pacakge was not too shabby, and yesterday I
1029 uploaded the latest version to Debian unstable.  It should enter
1030 testing today or tomorrow, perhaps delayed by
1031 <a href="https://bugs.debian.org/1055812">a small library
1032 transition</a>.</p>
1033
1034 <p>Armed with a new version of sqlcipher, I can now have a look at the
1035 SQL database in ~/.config/Signal/sql/db.sqlite.  First, one need to
1036 fetch the encryption key from the Signal configuration using this
1037 simple JSON extraction command:</p>
1038
1039 <pre>/usr/bin/jq -r '."key"' ~/.config/Signal/config.json</pre>
1040
1041 <p>Assuming the result from that command is 'secretkey', which is a
1042 hexadecimal number representing the key used to encrypt the database.
1043 Next, one can now connect to the database and inject the encryption
1044 key for access via SQL to fetch information from the database.  Here
1045 is an example dumping the database structure:</p>
1046
1047 <pre>
1048 % sqlcipher ~/.config/Signal/sql/db.sqlite
1049 sqlite> PRAGMA key = "x'secretkey'";
1050 sqlite> .schema
1051 CREATE TABLE sqlite_stat1(tbl,idx,stat);
1052 CREATE TABLE conversations(
1053       id STRING PRIMARY KEY ASC,
1054       json TEXT,
1055
1056       active_at INTEGER,
1057       type STRING,
1058       members TEXT,
1059       name TEXT,
1060       profileName TEXT
1061     , profileFamilyName TEXT, profileFullName TEXT, e164 TEXT, serviceId TEXT, groupId TEXT, profileLastFetchedAt INTEGER);
1062 CREATE TABLE identityKeys(
1063       id STRING PRIMARY KEY ASC,
1064       json TEXT
1065     );
1066 CREATE TABLE items(
1067       id STRING PRIMARY KEY ASC,
1068       json TEXT
1069     );
1070 CREATE TABLE sessions(
1071       id TEXT PRIMARY KEY,
1072       conversationId TEXT,
1073       json TEXT
1074     , ourServiceId STRING, serviceId STRING);
1075 CREATE TABLE attachment_downloads(
1076     id STRING primary key,
1077     timestamp INTEGER,
1078     pending INTEGER,
1079     json TEXT
1080   );
1081 CREATE TABLE sticker_packs(
1082     id TEXT PRIMARY KEY,
1083     key TEXT NOT NULL,
1084
1085     author STRING,
1086     coverStickerId INTEGER,
1087     createdAt INTEGER,
1088     downloadAttempts INTEGER,
1089     installedAt INTEGER,
1090     lastUsed INTEGER,
1091     status STRING,
1092     stickerCount INTEGER,
1093     title STRING
1094   , attemptedStatus STRING, position INTEGER DEFAULT 0 NOT NULL, storageID STRING, storageVersion INTEGER, storageUnknownFields BLOB, storageNeedsSync
1095       INTEGER DEFAULT 0 NOT NULL);
1096 CREATE TABLE stickers(
1097     id INTEGER NOT NULL,
1098     packId TEXT NOT NULL,
1099
1100     emoji STRING,
1101     height INTEGER,
1102     isCoverOnly INTEGER,
1103     lastUsed INTEGER,
1104     path STRING,
1105     width INTEGER,
1106
1107     PRIMARY KEY (id, packId),
1108     CONSTRAINT stickers_fk
1109       FOREIGN KEY (packId)
1110       REFERENCES sticker_packs(id)
1111       ON DELETE CASCADE
1112   );
1113 CREATE TABLE sticker_references(
1114     messageId STRING,
1115     packId TEXT,
1116     CONSTRAINT sticker_references_fk
1117       FOREIGN KEY(packId)
1118       REFERENCES sticker_packs(id)
1119       ON DELETE CASCADE
1120   );
1121 CREATE TABLE emojis(
1122     shortName TEXT PRIMARY KEY,
1123     lastUsage INTEGER
1124   );
1125 CREATE TABLE messages(
1126         rowid INTEGER PRIMARY KEY ASC,
1127         id STRING UNIQUE,
1128         json TEXT,
1129         readStatus INTEGER,
1130         expires_at INTEGER,
1131         sent_at INTEGER,
1132         schemaVersion INTEGER,
1133         conversationId STRING,
1134         received_at INTEGER,
1135         source STRING,
1136         hasAttachments INTEGER,
1137         hasFileAttachments INTEGER,
1138         hasVisualMediaAttachments INTEGER,
1139         expireTimer INTEGER,
1140         expirationStartTimestamp INTEGER,
1141         type STRING,
1142         body TEXT,
1143         messageTimer INTEGER,
1144         messageTimerStart INTEGER,
1145         messageTimerExpiresAt INTEGER,
1146         isErased INTEGER,
1147         isViewOnce INTEGER,
1148         sourceServiceId TEXT, serverGuid STRING NULL, sourceDevice INTEGER, storyId STRING, isStory INTEGER
1149         GENERATED ALWAYS AS (type IS 'story'), isChangeCreatedByUs INTEGER NOT NULL DEFAULT 0, isTimerChangeFromSync INTEGER
1150         GENERATED ALWAYS AS (
1151           json_extract(json, '$.expirationTimerUpdate.fromSync') IS 1
1152         ), seenStatus NUMBER default 0, storyDistributionListId STRING, expiresAt INT
1153         GENERATED ALWAYS
1154         AS (ifnull(
1155           expirationStartTimestamp + (expireTimer * 1000),
1156           9007199254740991
1157         )), shouldAffectActivity INTEGER
1158         GENERATED ALWAYS AS (
1159           type IS NULL
1160           OR
1161           type NOT IN (
1162             'change-number-notification',
1163             'contact-removed-notification',
1164             'conversation-merge',
1165             'group-v1-migration',
1166             'keychange',
1167             'message-history-unsynced',
1168             'profile-change',
1169             'story',
1170             'universal-timer-notification',
1171             'verified-change'
1172           )
1173         ), shouldAffectPreview INTEGER
1174         GENERATED ALWAYS AS (
1175           type IS NULL
1176           OR
1177           type NOT IN (
1178             'change-number-notification',
1179             'contact-removed-notification',
1180             'conversation-merge',
1181             'group-v1-migration',
1182             'keychange',
1183             'message-history-unsynced',
1184             'profile-change',
1185             'story',
1186             'universal-timer-notification',
1187             'verified-change'
1188           )
1189         ), isUserInitiatedMessage INTEGER
1190         GENERATED ALWAYS AS (
1191           type IS NULL
1192           OR
1193           type NOT IN (
1194             'change-number-notification',
1195             'contact-removed-notification',
1196             'conversation-merge',
1197             'group-v1-migration',
1198             'group-v2-change',
1199             'keychange',
1200             'message-history-unsynced',
1201             'profile-change',
1202             'story',
1203             'universal-timer-notification',
1204             'verified-change'
1205           )
1206         ), mentionsMe INTEGER NOT NULL DEFAULT 0, isGroupLeaveEvent INTEGER
1207         GENERATED ALWAYS AS (
1208           type IS 'group-v2-change' AND
1209           json_array_length(json_extract(json, '$.groupV2Change.details')) IS 1 AND
1210           json_extract(json, '$.groupV2Change.details[0].type') IS 'member-remove' AND
1211           json_extract(json, '$.groupV2Change.from') IS NOT NULL AND
1212           json_extract(json, '$.groupV2Change.from') IS json_extract(json, '$.groupV2Change.details[0].aci')
1213         ), isGroupLeaveEventFromOther INTEGER
1214         GENERATED ALWAYS AS (
1215           isGroupLeaveEvent IS 1
1216           AND
1217           isChangeCreatedByUs IS 0
1218         ), callId TEXT
1219         GENERATED ALWAYS AS (
1220           json_extract(json, '$.callId')
1221         ));
1222 CREATE TABLE sqlite_stat4(tbl,idx,neq,nlt,ndlt,sample);
1223 CREATE TABLE jobs(
1224         id TEXT PRIMARY KEY,
1225         queueType TEXT STRING NOT NULL,
1226         timestamp INTEGER NOT NULL,
1227         data STRING TEXT
1228       );
1229 CREATE TABLE reactions(
1230         conversationId STRING,
1231         emoji STRING,
1232         fromId STRING,
1233         messageReceivedAt INTEGER,
1234         targetAuthorAci STRING,
1235         targetTimestamp INTEGER,
1236         unread INTEGER
1237       , messageId STRING);
1238 CREATE TABLE senderKeys(
1239         id TEXT PRIMARY KEY NOT NULL,
1240         senderId TEXT NOT NULL,
1241         distributionId TEXT NOT NULL,
1242         data BLOB NOT NULL,
1243         lastUpdatedDate NUMBER NOT NULL
1244       );
1245 CREATE TABLE unprocessed(
1246         id STRING PRIMARY KEY ASC,
1247         timestamp INTEGER,
1248         version INTEGER,
1249         attempts INTEGER,
1250         envelope TEXT,
1251         decrypted TEXT,
1252         source TEXT,
1253         serverTimestamp INTEGER,
1254         sourceServiceId STRING
1255       , serverGuid STRING NULL, sourceDevice INTEGER, receivedAtCounter INTEGER, urgent INTEGER, story INTEGER);
1256 CREATE TABLE sendLogPayloads(
1257         id INTEGER PRIMARY KEY ASC,
1258
1259         timestamp INTEGER NOT NULL,
1260         contentHint INTEGER NOT NULL,
1261         proto BLOB NOT NULL
1262       , urgent INTEGER, hasPniSignatureMessage INTEGER DEFAULT 0 NOT NULL);
1263 CREATE TABLE sendLogRecipients(
1264         payloadId INTEGER NOT NULL,
1265
1266         recipientServiceId STRING NOT NULL,
1267         deviceId INTEGER NOT NULL,
1268
1269         PRIMARY KEY (payloadId, recipientServiceId, deviceId),
1270
1271         CONSTRAINT sendLogRecipientsForeignKey
1272           FOREIGN KEY (payloadId)
1273           REFERENCES sendLogPayloads(id)
1274           ON DELETE CASCADE
1275       );
1276 CREATE TABLE sendLogMessageIds(
1277         payloadId INTEGER NOT NULL,
1278
1279         messageId STRING NOT NULL,
1280
1281         PRIMARY KEY (payloadId, messageId),
1282
1283         CONSTRAINT sendLogMessageIdsForeignKey
1284           FOREIGN KEY (payloadId)
1285           REFERENCES sendLogPayloads(id)
1286           ON DELETE CASCADE
1287       );
1288 CREATE TABLE preKeys(
1289         id STRING PRIMARY KEY ASC,
1290         json TEXT
1291       , ourServiceId NUMBER
1292         GENERATED ALWAYS AS (json_extract(json, '$.ourServiceId')));
1293 CREATE TABLE signedPreKeys(
1294         id STRING PRIMARY KEY ASC,
1295         json TEXT
1296       , ourServiceId NUMBER
1297         GENERATED ALWAYS AS (json_extract(json, '$.ourServiceId')));
1298 CREATE TABLE badges(
1299         id TEXT PRIMARY KEY,
1300         category TEXT NOT NULL,
1301         name TEXT NOT NULL,
1302         descriptionTemplate TEXT NOT NULL
1303       );
1304 CREATE TABLE badgeImageFiles(
1305         badgeId TEXT REFERENCES badges(id)
1306           ON DELETE CASCADE
1307           ON UPDATE CASCADE,
1308         'order' INTEGER NOT NULL,
1309         url TEXT NOT NULL,
1310         localPath TEXT,
1311         theme TEXT NOT NULL
1312       );
1313 CREATE TABLE storyReads (
1314         authorId STRING NOT NULL,
1315         conversationId STRING NOT NULL,
1316         storyId STRING NOT NULL,
1317         storyReadDate NUMBER NOT NULL,
1318
1319         PRIMARY KEY (authorId, storyId)
1320       );
1321 CREATE TABLE storyDistributions(
1322         id STRING PRIMARY KEY NOT NULL,
1323         name TEXT,
1324
1325         senderKeyInfoJson STRING
1326       , deletedAtTimestamp INTEGER, allowsReplies INTEGER, isBlockList INTEGER, storageID STRING, storageVersion INTEGER, storageUnknownFields BLOB, storageNeedsSync INTEGER);
1327 CREATE TABLE storyDistributionMembers(
1328         listId STRING NOT NULL REFERENCES storyDistributions(id)
1329           ON DELETE CASCADE
1330           ON UPDATE CASCADE,
1331         serviceId STRING NOT NULL,
1332
1333         PRIMARY KEY (listId, serviceId)
1334       );
1335 CREATE TABLE uninstalled_sticker_packs (
1336         id STRING NOT NULL PRIMARY KEY,
1337         uninstalledAt NUMBER NOT NULL,
1338         storageID STRING,
1339         storageVersion NUMBER,
1340         storageUnknownFields BLOB,
1341         storageNeedsSync INTEGER NOT NULL
1342       );
1343 CREATE TABLE groupCallRingCancellations(
1344         ringId INTEGER PRIMARY KEY,
1345         createdAt INTEGER NOT NULL
1346       );
1347 CREATE TABLE IF NOT EXISTS 'messages_fts_data'(id INTEGER PRIMARY KEY, block BLOB);
1348 CREATE TABLE IF NOT EXISTS 'messages_fts_idx'(segid, term, pgno, PRIMARY KEY(segid, term)) WITHOUT ROWID;
1349 CREATE TABLE IF NOT EXISTS 'messages_fts_content'(id INTEGER PRIMARY KEY, c0);
1350 CREATE TABLE IF NOT EXISTS 'messages_fts_docsize'(id INTEGER PRIMARY KEY, sz BLOB);
1351 CREATE TABLE IF NOT EXISTS 'messages_fts_config'(k PRIMARY KEY, v) WITHOUT ROWID;
1352 CREATE TABLE edited_messages(
1353         messageId STRING REFERENCES messages(id)
1354           ON DELETE CASCADE,
1355         sentAt INTEGER,
1356         readStatus INTEGER
1357       , conversationId STRING);
1358 CREATE TABLE mentions (
1359         messageId REFERENCES messages(id) ON DELETE CASCADE,
1360         mentionAci STRING,
1361         start INTEGER,
1362         length INTEGER
1363       );
1364 CREATE TABLE kyberPreKeys(
1365         id STRING PRIMARY KEY NOT NULL,
1366         json TEXT NOT NULL, ourServiceId NUMBER
1367         GENERATED ALWAYS AS (json_extract(json, '$.ourServiceId')));
1368 CREATE TABLE callsHistory (
1369         callId TEXT PRIMARY KEY,
1370         peerId TEXT NOT NULL, -- conversation id (legacy) | uuid | groupId | roomId
1371         ringerId TEXT DEFAULT NULL, -- ringer uuid
1372         mode TEXT NOT NULL, -- enum "Direct" | "Group"
1373         type TEXT NOT NULL, -- enum "Audio" | "Video" | "Group"
1374         direction TEXT NOT NULL, -- enum "Incoming" | "Outgoing
1375         -- Direct: enum "Pending" | "Missed" | "Accepted" | "Deleted"
1376         -- Group: enum "GenericGroupCall" | "OutgoingRing" | "Ringing" | "Joined" | "Missed" | "Declined" | "Accepted" | "Deleted"
1377         status TEXT NOT NULL,
1378         timestamp INTEGER NOT NULL,
1379         UNIQUE (callId, peerId) ON CONFLICT FAIL
1380       );
1381 [ dropped all indexes to save space in this blog post ]
1382 CREATE TRIGGER messages_on_view_once_update AFTER UPDATE ON messages
1383       WHEN
1384         new.body IS NOT NULL AND new.isViewOnce = 1
1385       BEGIN
1386         DELETE FROM messages_fts WHERE rowid = old.rowid;
1387       END;
1388 CREATE TRIGGER messages_on_insert AFTER INSERT ON messages
1389       WHEN new.isViewOnce IS NOT 1 AND new.storyId IS NULL
1390       BEGIN
1391         INSERT INTO messages_fts
1392           (rowid, body)
1393         VALUES
1394           (new.rowid, new.body);
1395       END;
1396 CREATE TRIGGER messages_on_delete AFTER DELETE ON messages BEGIN
1397         DELETE FROM messages_fts WHERE rowid = old.rowid;
1398         DELETE FROM sendLogPayloads WHERE id IN (
1399           SELECT payloadId FROM sendLogMessageIds
1400           WHERE messageId = old.id
1401         );
1402         DELETE FROM reactions WHERE rowid IN (
1403           SELECT rowid FROM reactions
1404           WHERE messageId = old.id
1405         );
1406         DELETE FROM storyReads WHERE storyId = old.storyId;
1407       END;
1408 CREATE VIRTUAL TABLE messages_fts USING fts5(
1409         body,
1410         tokenize = 'signal_tokenizer'
1411       );
1412 CREATE TRIGGER messages_on_update AFTER UPDATE ON messages
1413       WHEN
1414         (new.body IS NULL OR old.body IS NOT new.body) AND
1415          new.isViewOnce IS NOT 1 AND new.storyId IS NULL
1416       BEGIN
1417         DELETE FROM messages_fts WHERE rowid = old.rowid;
1418         INSERT INTO messages_fts
1419           (rowid, body)
1420         VALUES
1421           (new.rowid, new.body);
1422       END;
1423 CREATE TRIGGER messages_on_insert_insert_mentions AFTER INSERT ON messages
1424       BEGIN
1425         INSERT INTO mentions (messageId, mentionAci, start, length)
1426
1427     SELECT messages.id, bodyRanges.value ->> 'mentionAci' as mentionAci,
1428       bodyRanges.value ->> 'start' as start,
1429       bodyRanges.value ->> 'length' as length
1430     FROM messages, json_each(messages.json ->> 'bodyRanges') as bodyRanges
1431     WHERE bodyRanges.value ->> 'mentionAci' IS NOT NULL
1432
1433         AND messages.id = new.id;
1434       END;
1435 CREATE TRIGGER messages_on_update_update_mentions AFTER UPDATE ON messages
1436       BEGIN
1437         DELETE FROM mentions WHERE messageId = new.id;
1438         INSERT INTO mentions (messageId, mentionAci, start, length)
1439
1440     SELECT messages.id, bodyRanges.value ->> 'mentionAci' as mentionAci,
1441       bodyRanges.value ->> 'start' as start,
1442       bodyRanges.value ->> 'length' as length
1443     FROM messages, json_each(messages.json ->> 'bodyRanges') as bodyRanges
1444     WHERE bodyRanges.value ->> 'mentionAci' IS NOT NULL
1445
1446         AND messages.id = new.id;
1447       END;
1448 sqlite>
1449 </pre>
1450
1451 <p>Finally I have the tool needed to inspect and process Signal
1452 messages that I need, without using the vendor provided client.  Now
1453 on to transforming it to a more useful format.</p>
1454
1455 <p>As usual, if you use Bitcoin and want to show your support of my
1456 activities, please send Bitcoin donations to my address
1457 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
1458 </div>
1459       <div class="tags">
1460
1461
1462         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>, <a href="https://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
1463
1464
1465       </div>
1466     </div>
1467     <div class="padding"></div>
1468
1469     <div class="entry">
1470       <div class="title"><a href="https://people.skolelinux.org/pere/blog/New_chrpath_release_0_17.html">New chrpath release 0.17</a></div>
1471       <div class="date">10th November 2023</div>
1472       <div class="body"><p>The chrpath package provide a simple command line tool to remove or
1473 modify the rpath or runpath of compiled ELF program.  It is almost 10
1474 years since I updated the code base, but I stumbled over the tool
1475 today, and decided it was time to move the code base from Subversion
1476 to git and find a new home for it, as the previous one (Debian Alioth)
1477 has been shut down.  I decided to go with
1478 <a href="https://codeberg.org/">Codeberg</a> this time, as it is my git
1479 service of choice these days, did a quick and dirty migration to git
1480 and updated the code with a few patches I found in the Debian bug
1481 tracker.  These are the release notes:</p>
1482
1483 <p>New in 0.17 released 2023-11-10:</p>
1484
1485 <ul>
1486 <li>Moved project to Codeberg, as Alioth is shut down.</li>
1487 <li>Add Solaris support (use &lt;sys/byteorder.h> instead of &lt;byteswap.h>).
1488    Patch from Rainer Orth.</li>
1489 <li>Added missing newline from printf() line.  Patch from Frank Dana.</li>
1490 <li>Corrected handling of multiple ELF sections. Patch from Frank Dana.</li>
1491 <li>Updated build rules for .deb.  Partly based on patch from djcj.</li>
1492 </ul>
1493
1494 <p>The latest edition is tagged and available from
1495 <a href="https://codeberg.org/pere/chrpath">https://codeberg.org/pere/chrpath</a>.
1496
1497 <p>As usual, if you use Bitcoin and want to show your support of my
1498 activities, please send Bitcoin donations to my address
1499 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
1500 </div>
1501       <div class="tags">
1502
1503
1504         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/chrpath">chrpath</a>, <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>.
1505
1506
1507       </div>
1508     </div>
1509     <div class="padding"></div>
1510
1511     <div class="entry">
1512       <div class="title"><a href="https://people.skolelinux.org/pere/blog/Test_framework_for_DocBook_processors___formatters.html">Test framework for DocBook processors / formatters</a></div>
1513       <div class="date"> 5th November 2023</div>
1514       <div class="body"><p>All the books I have published so far has been using
1515 <a href="https://docbook.org/">DocBook</a> somewhere in the process.
1516 For the first book, the source format was DocBook, while for every
1517 later book it was an intermediate format used as the stepping stone to
1518 be able to present the same manuscript in several formats, on paper,
1519 as ebook in ePub format, as a HTML page and as a PDF file either for
1520 paper production or for Internet consumption.  This is made possible
1521 with a wide variety of free software tools with DocBook support in
1522 Debian.  The source format of later books have been docx via rst,
1523 Markdown, Filemaker and Asciidoc, and for all of these I was able to
1524 generate a suitable DocBook file for further processing using
1525 <a href="https://tracker.debian.org/pkg/pandoc">pandoc</a>,
1526 <a href="https://tracker.debian.org/pkg/asciidoc">a2x</a> and
1527 <a href="https://tracker.debian.org/pkg/asciidoctor">asciidoctor</a>,
1528 as well as rendering using
1529 <a href="https://tracker.debian.org/pkg/xmlto">xmlto</a>,
1530 <a href="https://tracker.debian.org/pkg/dbtoepub">dbtoepub</a>,
1531 <a href="https://tracker.debian.org/pkg/dblatex">dblatex</a>,
1532 <a href="https://tracker.debian.org/pkg/docbook-xsl">docbook-xsl</a> and
1533 <a href="https://tracker.debian.org/pkg/fop">fop</a>.</p>
1534
1535 <p>Most of the <a href="http://www.hungry.com/~pere/publisher/">books I
1536 have published</a> are translated books, with English as the source
1537 language.  The use of
1538 <a href="https://tracker.debian.org/pkg/po4a">po4a</a> to
1539 handle translations using the gettext PO format has been a blessing,
1540 but publishing translated books had triggered the need to ensure the
1541 DocBook tools handle relevant languages correctly.  For every new
1542 language I have published, I had to submit patches dblatex, dbtoepub
1543 and docbook-xsl fixing incorrect language and country specific issues
1544 in the framework themselves.  Typically this has been missing keywords
1545 like 'figure' or sort ordering of index entries.  After a while it
1546 became tiresome to only discover issues like this by accident, and I
1547 decided to write a DocBook "test framework" exercising various
1548 features of DocBook and allowing me to see all features exercised for
1549 a given language.  It consist of a set of DocBook files, a version 4
1550 book, a version 5 book, a v4 book set, a v4 selection of problematic
1551 tables, one v4 testing sidefloat and finally one v4 testing a book of
1552 articles.  The DocBook files are accompanied with a set of build rules
1553 for building PDF using dblatex and docbook-xsl/fop, HTML using xmlto
1554 or docbook-xsl and epub using dbtoepub.  The result is a set of files
1555 visualizing footnotes, indexes, table of content list, figures,
1556 formulas and other DocBook features, allowing for a quick review on
1557 the completeness of the given locale settings.  To build with a
1558 different language setting, all one need to do is edit the lang= value
1559 in the .xml file to pick a different ISO 639 code value and run
1560 'make'.</p>
1561
1562 <p>The <a href="https://codeberg.org/pere/docbook-example/">test framework
1563 source code</a> is available from Codeberg, and a generated set of
1564 presentations of the various examples is available as Codeberg static
1565 web pages at
1566 <a href="https://pere.codeberg.page/docbook-example/">https://pere.codeberg.page/docbook-example/</a>.
1567 Using this test framework I have been able to discover and report
1568 several bugs and missing features in various tools, and got a lot of
1569 them fixed.  For example I got Northern Sami keywords added to both
1570 docbook-xsl and dblatex, fixed several typos in Norwegian bokmål and
1571 Norwegian Nynorsk, support for non-ascii title IDs added to pandoc,
1572 Norwegian index sorting support fixed in xindy and initial Norwegian
1573 Bokmål support added to dblatex.  Some issues still remains, though.
1574 Default index sorting rules are still broken in several tools, so the
1575 Norwegian letters æ, ø and å are more often than not sorted properly
1576 in the book index.</p>
1577
1578 <p>The test framework recently received some more polish, as part of
1579 publishing my latest book.  This book contained a lot of fairly
1580 complex tables, which exposed bugs in some of the tools.  This made me
1581 add a new test file with various tables, as well as spend some time to
1582 brush up the build rules.  My goal is for the test framework to
1583 exercise all DocBook features to make it easier to see which features
1584 work with different processors, and hopefully get them all to support
1585 the full set of DocBook features.  Feel free to send patches to extend
1586 the test set, and test it with your favorite DocBook processor.
1587 Please visit these two URLs to learn more:</p>
1588
1589 <ul>
1590 <li><a href="https://codeberg.org/pere/docbook-example/">https://codeberg.org/pere/docbook-example/</a></li>
1591 <li><a href="https://pere.codeberg.page/docbook-example/">https://pere.codeberg.page/docbook-example/</a></li>
1592 </ul>
1593
1594 <p>If you want to learn more on Docbook and translations, I recommend
1595 having a look at the <a href="https://docbook.org/">the DocBook
1596 web site</a>,
1597 <a href="https://doccookbook.sourceforge.net/html/en/">the DoCookBook
1598 site<a/> and my earlier blog post on
1599 <a href="https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html">how
1600 the Skolelinux project process and translate documentation</a>,  a talk I gave earlier this year on
1601 <a href="https://www.nuug.no/aktiviteter/20230314-oversetting-og-publisering-av-b%c3%b8ker-med-fri-programvare/">how
1602 to translate and publish books using free software</a> (Norwegian
1603 only).</p>
1604
1605 <!--
1606
1607 https://github.com/docbook/xslt10-stylesheets/issues/205 (docbook-xsl: sme support)
1608 https://bugs.debian.org/968437 (xindy: index sorting rules for nb/nn)
1609 https://bugs.debian.org/856123 (pandoc: markdown to docbook with non-english titles)
1610 https://bugs.debian.org/864813 (dblatex: missing nb words)
1611 https://bugs.debian.org/756386 (dblatex: index sorting rules for nb/nn)
1612 https://bugs.debian.org/796871 (dbtoepub: index sorting rules for nb/nn)
1613 https://bugs.debian.org/792616 (dblatex: PDF metadata)
1614 https://bugs.debian.org/686908 (docbook-xsl: index sorting rules for nb/nn)
1615 https://sourceforge.net/tracker/?func=detail&atid=373747&aid=3556630&group_id=21935 (docbook-xsl: nb/nn support)
1616 https://bugs.debian.org/684391 (dblatex: initial nb support)
1617
1618 -->
1619
1620 <p>As usual, if you use Bitcoin and want to show your support of my
1621 activities, please send Bitcoin donations to my address
1622 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
1623 </div>
1624       <div class="tags">
1625
1626
1627         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="https://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>.
1628
1629
1630       </div>
1631     </div>
1632     <div class="padding"></div>
1633
1634     <div class="entry">
1635       <div class="title"><a href="https://people.skolelinux.org/pere/blog/_Virkninger_av_angrefristloven___hovedfagsoppgaven_som_fikk_endret_en_lov.html">«Virkninger av angrefristloven», hovedfagsoppgaven som fikk endret en lov</a></div>
1636       <div class="date">29th October 2023</div>
1637       <div class="body"><img src="https://people.skolelinux.org/pere/blog/images/2023-10-29-bok-angrefrist.svg" width="20%" align="center"></a>
1638
1639 <p>I 1979 leverte Ole-Erik Yrvin en hovedfagsoppgave for Cand. Scient.
1640   ved Institutt for sosiologi på Universitetet i Oslo på oppdrag fra
1641   Forbruker- og administrasjonsdepartementet. Oppgaven evaluerte
1642   Angrefristloven fra 1972, og det han oppdaget førte til at loven ble
1643   endret fire år senere.</p>
1644
1645 <p>Jeg har kjent Ole-Erik en stund, og synes det var trist at hans
1646   oppgave ikke lenger er tilgjengelig, hverken fra oppdragsgiver
1647   eller fra universitetet.  Hans forsøk på å få den avbildet og lagt
1648   ut på Internett har vist seg fånyttes, så derfor tilbød jeg meg for
1649   en stund tilbake å publisere den og gjøre den tilgjengelig med
1650   fribruksvilkår på Internett.  Det er nå klart, og hovedfagsoppgaven
1651   er tilgjengelig blant annet via <a
1652   href="http://www.hungry.com/~pere/publisher/">min liste over
1653   publiserte bøker</a>, både som nettside,
1654   <a href="https://www.lulu.com/search?contributor=Ole-Erik+Yrvin">digital
1655   bok i ePub-format og på papir fra lulu.com</a>.  Jeg regner med at
1656   den også vil dukke opp på nettbokhandlere i løpet av en måned eller
1657   to.</p>
1658
1659 <p>Alle tabeller og figurer er gjenskapt for bedre lesbarhet, noen
1660   skrivefeil rettet opp og mange referanser har fått flere detaljer
1661   som ISBN-nummer og DOI-referanse.  Selv om jeg ikke regner med at
1662   dette blir en kioskvelter, så håper jeg denne nye utgaven kan komme
1663   fremtiden til glede.</p>
1664
1665 <p>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
1666 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
1667 til min adresse
1668 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>. Merk,
1669 betaling med bitcoin er ikke anonymt. :)</p>
1670 </div>
1671       <div class="tags">
1672
1673
1674         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>.
1675
1676
1677       </div>
1678     </div>
1679     <div class="padding"></div>
1680
1681     <p style="text-align: right;"><a href="index.rss"><img src="https://people.skolelinux.org/pere/blog/xml.gif" alt="RSS feed" width="36" height="14" /></a></p>
1682     <div id="sidebar">
1683
1684
1685
1686 <h2>Archive</h2>
1687 <ul>
1688
1689 <li>2024
1690 <ul>
1691
1692 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/01/">January (1)</a></li>
1693
1694 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/02/">February (1)</a></li>
1695
1696 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/03/">March (2)</a></li>
1697
1698 </ul></li>
1699
1700 <li>2023
1701 <ul>
1702
1703 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/01/">January (3)</a></li>
1704
1705 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/02/">February (1)</a></li>
1706
1707 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/04/">April (2)</a></li>
1708
1709 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/05/">May (3)</a></li>
1710
1711 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/06/">June (1)</a></li>
1712
1713 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/08/">August (1)</a></li>
1714
1715 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/09/">September (1)</a></li>
1716
1717 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/10/">October (1)</a></li>
1718
1719 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/11/">November (4)</a></li>
1720
1721 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/12/">December (1)</a></li>
1722
1723 </ul></li>
1724
1725 <li>2022
1726 <ul>
1727
1728 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/02/">February (1)</a></li>
1729
1730 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/03/">March (3)</a></li>
1731
1732 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/04/">April (2)</a></li>
1733
1734 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/06/">June (2)</a></li>
1735
1736 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/07/">July (1)</a></li>
1737
1738 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/09/">September (1)</a></li>
1739
1740 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/10/">October (1)</a></li>
1741
1742 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/12/">December (1)</a></li>
1743
1744 </ul></li>
1745
1746 <li>2021
1747 <ul>
1748
1749 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/01/">January (2)</a></li>
1750
1751 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/02/">February (1)</a></li>
1752
1753 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/05/">May (1)</a></li>
1754
1755 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/06/">June (1)</a></li>
1756
1757 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/07/">July (3)</a></li>
1758
1759 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/08/">August (1)</a></li>
1760
1761 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/09/">September (1)</a></li>
1762
1763 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/10/">October (1)</a></li>
1764
1765 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/12/">December (1)</a></li>
1766
1767 </ul></li>
1768
1769 <li>2020
1770 <ul>
1771
1772 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/02/">February (2)</a></li>
1773
1774 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/03/">March (2)</a></li>
1775
1776 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/04/">April (2)</a></li>
1777
1778 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/05/">May (3)</a></li>
1779
1780 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/06/">June (2)</a></li>
1781
1782 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/07/">July (1)</a></li>
1783
1784 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/09/">September (1)</a></li>
1785
1786 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/10/">October (1)</a></li>
1787
1788 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/11/">November (1)</a></li>
1789
1790 </ul></li>
1791
1792 <li>2019
1793 <ul>
1794
1795 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/01/">January (4)</a></li>
1796
1797 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/02/">February (3)</a></li>
1798
1799 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/03/">March (3)</a></li>
1800
1801 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/05/">May (2)</a></li>
1802
1803 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/06/">June (5)</a></li>
1804
1805 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/07/">July (2)</a></li>
1806
1807 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/08/">August (1)</a></li>
1808
1809 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/09/">September (1)</a></li>
1810
1811 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/11/">November (1)</a></li>
1812
1813 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/12/">December (4)</a></li>
1814
1815 </ul></li>
1816
1817 <li>2018
1818 <ul>
1819
1820 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/01/">January (1)</a></li>
1821
1822 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/02/">February (5)</a></li>
1823
1824 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/03/">March (5)</a></li>
1825
1826 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/04/">April (3)</a></li>
1827
1828 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/06/">June (2)</a></li>
1829
1830 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/07/">July (5)</a></li>
1831
1832 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/08/">August (3)</a></li>
1833
1834 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/09/">September (3)</a></li>
1835
1836 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/10/">October (5)</a></li>
1837
1838 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/11/">November (2)</a></li>
1839
1840 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/12/">December (4)</a></li>
1841
1842 </ul></li>
1843
1844 <li>2017
1845 <ul>
1846
1847 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/01/">January (4)</a></li>
1848
1849 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/02/">February (3)</a></li>
1850
1851 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/03/">March (5)</a></li>
1852
1853 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/04/">April (2)</a></li>
1854
1855 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/06/">June (5)</a></li>
1856
1857 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/07/">July (1)</a></li>
1858
1859 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/08/">August (1)</a></li>
1860
1861 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/09/">September (3)</a></li>
1862
1863 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/10/">October (5)</a></li>
1864
1865 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/11/">November (3)</a></li>
1866
1867 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/12/">December (4)</a></li>
1868
1869 </ul></li>
1870
1871 <li>2016
1872 <ul>
1873
1874 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/01/">January (3)</a></li>
1875
1876 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
1877
1878 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/03/">March (3)</a></li>
1879
1880 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/04/">April (8)</a></li>
1881
1882 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/05/">May (8)</a></li>
1883
1884 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/06/">June (2)</a></li>
1885
1886 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/07/">July (2)</a></li>
1887
1888 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/08/">August (5)</a></li>
1889
1890 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/09/">September (2)</a></li>
1891
1892 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/10/">October (3)</a></li>
1893
1894 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/11/">November (8)</a></li>
1895
1896 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/12/">December (5)</a></li>
1897
1898 </ul></li>
1899
1900 <li>2015
1901 <ul>
1902
1903 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/01/">January (7)</a></li>
1904
1905 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/02/">February (6)</a></li>
1906
1907 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/03/">March (1)</a></li>
1908
1909 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/04/">April (4)</a></li>
1910
1911 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/05/">May (3)</a></li>
1912
1913 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/06/">June (4)</a></li>
1914
1915 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/07/">July (6)</a></li>
1916
1917 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/08/">August (2)</a></li>
1918
1919 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/09/">September (2)</a></li>
1920
1921 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/10/">October (9)</a></li>
1922
1923 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/11/">November (6)</a></li>
1924
1925 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/12/">December (3)</a></li>
1926
1927 </ul></li>
1928
1929 <li>2014
1930 <ul>
1931
1932 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
1933
1934 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
1935
1936 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
1937
1938 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
1939
1940 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
1941
1942 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
1943
1944 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
1945
1946 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
1947
1948 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
1949
1950 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
1951
1952 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/11/">November (3)</a></li>
1953
1954 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/12/">December (5)</a></li>
1955
1956 </ul></li>
1957
1958 <li>2013
1959 <ul>
1960
1961 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
1962
1963 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
1964
1965 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
1966
1967 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
1968
1969 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
1970
1971 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
1972
1973 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
1974
1975 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
1976
1977 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
1978
1979 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
1980
1981 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
1982
1983 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
1984
1985 </ul></li>
1986
1987 <li>2012
1988 <ul>
1989
1990 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
1991
1992 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
1993
1994 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
1995
1996 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
1997
1998 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
1999
2000 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
2001
2002 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
2003
2004 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
2005
2006 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
2007
2008 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
2009
2010 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
2011
2012 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
2013
2014 </ul></li>
2015
2016 <li>2011
2017 <ul>
2018
2019 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
2020
2021 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
2022
2023 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
2024
2025 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
2026
2027 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
2028
2029 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
2030
2031 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
2032
2033 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
2034
2035 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
2036
2037 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
2038
2039 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
2040
2041 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
2042
2043 </ul></li>
2044
2045 <li>2010
2046 <ul>
2047
2048 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
2049
2050 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
2051
2052 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
2053
2054 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
2055
2056 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
2057
2058 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
2059
2060 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
2061
2062 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
2063
2064 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
2065
2066 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
2067
2068 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
2069
2070 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
2071
2072 </ul></li>
2073
2074 <li>2009
2075 <ul>
2076
2077 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
2078
2079 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
2080
2081 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
2082
2083 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
2084
2085 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
2086
2087 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
2088
2089 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
2090
2091 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
2092
2093 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
2094
2095 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
2096
2097 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
2098
2099 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
2100
2101 </ul></li>
2102
2103 <li>2008
2104 <ul>
2105
2106 <li><a href="https://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
2107
2108 <li><a href="https://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
2109
2110 </ul></li>
2111
2112 </ul>
2113
2114
2115
2116 <h2>Tags</h2>
2117 <ul>
2118
2119  <li><a href="https://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (19)</a></li>
2120
2121  <li><a href="https://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
2122
2123  <li><a href="https://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
2124
2125  <li><a href="https://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
2126
2127  <li><a href="https://people.skolelinux.org/pere/blog/tags/betalkontant">betalkontant (9)</a></li>
2128
2129  <li><a href="https://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (13)</a></li>
2130
2131  <li><a href="https://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (17)</a></li>
2132
2133  <li><a href="https://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
2134
2135  <li><a href="https://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (3)</a></li>
2136
2137  <li><a href="https://people.skolelinux.org/pere/blog/tags/debian">debian (197)</a></li>
2138
2139  <li><a href="https://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (159)</a></li>
2140
2141  <li><a href="https://people.skolelinux.org/pere/blog/tags/debian-handbook">debian-handbook (9)</a></li>
2142
2143  <li><a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan (11)</a></li>
2144
2145  <li><a href="https://people.skolelinux.org/pere/blog/tags/dld">dld (18)</a></li>
2146
2147  <li><a href="https://people.skolelinux.org/pere/blog/tags/docbook">docbook (32)</a></li>
2148
2149  <li><a href="https://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
2150
2151  <li><a href="https://people.skolelinux.org/pere/blog/tags/english">english (458)</a></li>
2152
2153  <li><a href="https://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
2154
2155  <li><a href="https://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (14)</a></li>
2156
2157  <li><a href="https://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (34)</a></li>
2158
2159  <li><a href="https://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
2160
2161  <li><a href="https://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (20)</a></li>
2162
2163  <li><a href="https://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
2164
2165  <li><a href="https://people.skolelinux.org/pere/blog/tags/intervju">intervju (43)</a></li>
2166
2167  <li><a href="https://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (17)</a></li>
2168
2169  <li><a href="https://people.skolelinux.org/pere/blog/tags/kart">kart (23)</a></li>
2170
2171  <li><a href="https://people.skolelinux.org/pere/blog/tags/kodi">kodi (6)</a></li>
2172
2173  <li><a href="https://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
2174
2175  <li><a href="https://people.skolelinux.org/pere/blog/tags/lego">lego (5)</a></li>
2176
2177  <li><a href="https://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
2178
2179  <li><a href="https://people.skolelinux.org/pere/blog/tags/linuxcnc">linuxcnc (5)</a></li>
2180
2181  <li><a href="https://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
2182
2183  <li><a href="https://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
2184
2185  <li><a href="https://people.skolelinux.org/pere/blog/tags/madewithcc">madewithcc (3)</a></li>
2186
2187  <li><a href="https://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
2188
2189  <li><a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (46)</a></li>
2190
2191  <li><a href="https://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (15)</a></li>
2192
2193  <li><a href="https://people.skolelinux.org/pere/blog/tags/noark5">noark5 (25)</a></li>
2194
2195  <li><a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk (324)</a></li>
2196
2197  <li><a href="https://people.skolelinux.org/pere/blog/tags/nuug">nuug (199)</a></li>
2198
2199  <li><a href="https://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (41)</a></li>
2200
2201  <li><a href="https://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
2202
2203  <li><a href="https://people.skolelinux.org/pere/blog/tags/opensnitch">opensnitch (4)</a></li>
2204
2205  <li><a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (76)</a></li>
2206
2207  <li><a href="https://people.skolelinux.org/pere/blog/tags/personvern">personvern (114)</a></li>
2208
2209  <li><a href="https://people.skolelinux.org/pere/blog/tags/raid">raid (3)</a></li>
2210
2211  <li><a href="https://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
2212
2213  <li><a href="https://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
2214
2215  <li><a href="https://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
2216
2217  <li><a href="https://people.skolelinux.org/pere/blog/tags/robot">robot (17)</a></li>
2218
2219  <li><a href="https://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
2220
2221  <li><a href="https://people.skolelinux.org/pere/blog/tags/ruter">ruter (7)</a></li>
2222
2223  <li><a href="https://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
2224
2225  <li><a href="https://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (60)</a></li>
2226
2227  <li><a href="https://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
2228
2229  <li><a href="https://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (5)</a></li>
2230
2231  <li><a href="https://people.skolelinux.org/pere/blog/tags/standard">standard (76)</a></li>
2232
2233  <li><a href="https://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (7)</a></li>
2234
2235  <li><a href="https://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (14)</a></li>
2236
2237  <li><a href="https://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (65)</a></li>
2238
2239  <li><a href="https://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (5)</a></li>
2240
2241  <li><a href="https://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
2242
2243  <li><a href="https://people.skolelinux.org/pere/blog/tags/valg">valg (9)</a></li>
2244
2245  <li><a href="https://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri (22)</a></li>
2246
2247  <li><a href="https://people.skolelinux.org/pere/blog/tags/video">video (80)</a></li>
2248
2249  <li><a href="https://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
2250
2251  <li><a href="https://people.skolelinux.org/pere/blog/tags/web">web (42)</a></li>
2252
2253 </ul>
2254
2255
2256     </div>
2257     <p style="text-align: right">
2258  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
2259 </p>
2260
2261   </body>
2262 </html>