From: Petter Reinholdtsen Date: Sat, 19 Mar 2016 14:30:26 +0000 (+0100) Subject: Generated. X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/756e31d2872fbfcdf4bad79df6ab3e36cc6f3862?ds=inline Generated. --- diff --git a/blog/UsingQR____Electronic__paper_invoices_using_JSON_and_QR_codes.html b/blog/UsingQR____Electronic__paper_invoices_using_JSON_and_QR_codes.html index 2e831ee25f..9b5128f196 100644 --- a/blog/UsingQR____Electronic__paper_invoices_using_JSON_and_QR_codes.html +++ b/blog/UsingQR____Electronic__paper_invoices_using_JSON_and_QR_codes.html @@ -40,7 +40,7 @@ a QR code with the key information of the invoice in JSON format. This is the typical content of a QR code following the UsingQR specification (based on a real world example, some numbers replaced to get a more bogus entry). I've reformatted the JSON to make it easier -to read. Normally this is all on one long line: +to read. Normally this is all on one long line:

 {
@@ -86,7 +86,7 @@ risk, but if this happen there is some legal defense in the fact that
 the people behind the format claimed it was safe to do so.  At least
 with patents, there is always
 a
-chance of getting sued...
+chance of getting sued...

 
 
I also asked if they planned to maintain the format in an
 independent standard organization to give others more confidence that
diff --git a/blog/archive/2016/03/03.rss b/blog/archive/2016/03/03.rss
index d84113d515..10a7e4ab63 100644
--- a/blog/archive/2016/03/03.rss
+++ b/blog/archive/2016/03/03.rss
@@ -29,7 +29,7 @@ a QR code with the key information of the invoice in JSON format.
 This is the typical content of a QR code following the UsingQR
 specification (based on a real world example, some numbers replaced to
 get a more bogus entry).  I've reformatted the JSON to make it easier
-to read.  Normally this is all on one long line:
+to read.  Normally this is all on one long line:</p>
 
 <p><img src="http://people.skolelinux.org/pere/blog/images/2016-03-19-qr-invoice.png" align="right"><pre>
 {
@@ -75,7 +75,7 @@ risk, but if this happen there is some legal defense in the fact that
 the people behind the format claimed it was safe to do so.  At least
 with patents, there is always
 <a href="http://www.paperspecs.com/paper-news/beware-the-qr-code-patent-trap/">a
-chance of getting sued...</a>
+chance of getting sued...</a></p>
 
 <p>I also asked if they planned to maintain the format in an
 independent standard organization to give others more confidence that
diff --git a/blog/archive/2016/03/index.html b/blog/archive/2016/03/index.html
index 1ea68a9d07..6da191e2c0 100644
--- a/blog/archive/2016/03/index.html
+++ b/blog/archive/2016/03/index.html
@@ -47,7 +47,7 @@ a QR code with the key information of the invoice in JSON format.
 This is the typical content of a QR code following the UsingQR
 specification (based on a real world example, some numbers replaced to
 get a more bogus entry).  I've reformatted the JSON to make it easier
-to read.  Normally this is all on one long line:
+to read.  Normally this is all on one long line:

 
 
 {
@@ -93,7 +93,7 @@ risk, but if this happen there is some legal defense in the fact that
 the people behind the format claimed it was safe to do so.  At least
 with patents, there is always
 a
-chance of getting sued...
+chance of getting sued...

 
 
I also asked if they planned to maintain the format in an
 independent standard organization to give others more confidence that
diff --git a/blog/index.html b/blog/index.html
index eb36b8ec88..f52364f708 100644
--- a/blog/index.html
+++ b/blog/index.html
@@ -40,7 +40,7 @@ a QR code with the key information of the invoice in JSON format.
 This is the typical content of a QR code following the UsingQR
 specification (based on a real world example, some numbers replaced to
 get a more bogus entry).  I've reformatted the JSON to make it easier
-to read.  Normally this is all on one long line:
+to read.  Normally this is all on one long line:

 
 
 {
@@ -86,7 +86,7 @@ risk, but if this happen there is some legal defense in the fact that
 the people behind the format claimed it was safe to do so.  At least
 with patents, there is always
 a
-chance of getting sued...
+chance of getting sued...

 
 
I also asked if they planned to maintain the format in an
 independent standard organization to give others more confidence that
diff --git a/blog/index.rss b/blog/index.rss
index 7364c0cb7c..5be2cbecbb 100644
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -29,7 +29,7 @@ a QR code with the key information of the invoice in JSON format.
 This is the typical content of a QR code following the UsingQR
 specification (based on a real world example, some numbers replaced to
 get a more bogus entry).  I've reformatted the JSON to make it easier
-to read.  Normally this is all on one long line:
+to read.  Normally this is all on one long line:</p>
 
 <p><img src="http://people.skolelinux.org/pere/blog/images/2016-03-19-qr-invoice.png" align="right"><pre>
 {
@@ -75,7 +75,7 @@ risk, but if this happen there is some legal defense in the fact that
 the people behind the format claimed it was safe to do so.  At least
 with patents, there is always
 <a href="http://www.paperspecs.com/paper-news/beware-the-qr-code-patent-trap/">a
-chance of getting sued...</a>
+chance of getting sued...</a></p>
 
 <p>I also asked if they planned to maintain the format in an
 independent standard organization to give others more confidence that
diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss
index d043b5b1d4..63aa56de72 100644
--- a/blog/tags/english/english.rss
+++ b/blog/tags/english/english.rss
@@ -29,7 +29,7 @@ a QR code with the key information of the invoice in JSON format.
 This is the typical content of a QR code following the UsingQR
 specification (based on a real world example, some numbers replaced to
 get a more bogus entry).  I've reformatted the JSON to make it easier
-to read.  Normally this is all on one long line:
+to read.  Normally this is all on one long line:</p>
 
 <p><img src="http://people.skolelinux.org/pere/blog/images/2016-03-19-qr-invoice.png" align="right"><pre>
 {
@@ -75,7 +75,7 @@ risk, but if this happen there is some legal defense in the fact that
 the people behind the format claimed it was safe to do so.  At least
 with patents, there is always
 <a href="http://www.paperspecs.com/paper-news/beware-the-qr-code-patent-trap/">a
-chance of getting sued...</a>
+chance of getting sued...</a></p>
 
 <p>I also asked if they planned to maintain the format in an
 independent standard organization to give others more confidence that
diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html
index 24437079ea..aa23430792 100644
--- a/blog/tags/english/index.html
+++ b/blog/tags/english/index.html
@@ -46,7 +46,7 @@ a QR code with the key information of the invoice in JSON format.
 This is the typical content of a QR code following the UsingQR
 specification (based on a real world example, some numbers replaced to
 get a more bogus entry).  I've reformatted the JSON to make it easier
-to read.  Normally this is all on one long line:
+to read.  Normally this is all on one long line:

 
 
 {
@@ -92,7 +92,7 @@ risk, but if this happen there is some legal defense in the fact that
 the people behind the format claimed it was safe to do so.  At least
 with patents, there is always
 a
-chance of getting sued...
+chance of getting sued...

 
 
I also asked if they planned to maintain the format in an
 independent standard organization to give others more confidence that
diff --git a/blog/tags/standard/index.html b/blog/tags/standard/index.html
index dc915b9d36..0c25644015 100644
--- a/blog/tags/standard/index.html
+++ b/blog/tags/standard/index.html
@@ -46,7 +46,7 @@ a QR code with the key information of the invoice in JSON format.
 This is the typical content of a QR code following the UsingQR
 specification (based on a real world example, some numbers replaced to
 get a more bogus entry).  I've reformatted the JSON to make it easier
-to read.  Normally this is all on one long line:
+to read.  Normally this is all on one long line:

 
 
 {
@@ -92,7 +92,7 @@ risk, but if this happen there is some legal defense in the fact that
 the people behind the format claimed it was safe to do so.  At least
 with patents, there is always
 a
-chance of getting sued...
+chance of getting sued...

 
 
I also asked if they planned to maintain the format in an
 independent standard organization to give others more confidence that
diff --git a/blog/tags/standard/standard.rss b/blog/tags/standard/standard.rss
index 110714eedc..7cd04175b2 100644
--- a/blog/tags/standard/standard.rss
+++ b/blog/tags/standard/standard.rss
@@ -29,7 +29,7 @@ a QR code with the key information of the invoice in JSON format.
 This is the typical content of a QR code following the UsingQR
 specification (based on a real world example, some numbers replaced to
 get a more bogus entry).  I've reformatted the JSON to make it easier
-to read.  Normally this is all on one long line:
+to read.  Normally this is all on one long line:</p>
 
 <p><img src="http://people.skolelinux.org/pere/blog/images/2016-03-19-qr-invoice.png" align="right"><pre>
 {
@@ -75,7 +75,7 @@ risk, but if this happen there is some legal defense in the fact that
 the people behind the format claimed it was safe to do so.  At least
 with patents, there is always
 <a href="http://www.paperspecs.com/paper-news/beware-the-qr-code-patent-trap/">a
-chance of getting sued...</a>
+chance of getting sued...</a></p>
 
 <p>I also asked if they planned to maintain the format in an
 independent standard organization to give others more confidence that