blog/index.rss

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