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 2e831ee25f8d6160fe227d92ba7d401ce741fd6f..9b5128f196ee881d65f4b864aa035b2a25ed23a1 100644 (file)
--- 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
 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>
 {
 
 <p><img src="http://people.skolelinux.org/pere/blog/images/2016-03-19-qr-invoice.png" align="right"><pre>
 {


@@ -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 href="http://www.paperspecs.com/paper-news/beware-the-qr-code-patent-trap/">a
 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
 
 <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/03.rss b/blog/archive/2016/03/03.rss
index d84113d5158af454e298ae11d4452dc1b0d60f7e..10a7e4ab63f546a0b74238720e475d7cae238d38 100644 (file)
--- 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
 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>
 {
 
 <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
 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
 
 <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 1ea68a9d0785035e185779a5cf5f823ebe2a2c59..6da191e2c0cad6afdc180577e6a7586944c9fd64 100644 (file)
--- 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
 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>
 {
 
 <p><img src="http://people.skolelinux.org/pere/blog/images/2016-03-19-qr-invoice.png" align="right"><pre>
 {


@@ -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 href="http://www.paperspecs.com/paper-news/beware-the-qr-code-patent-trap/">a
 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
 
 <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/index.html b/blog/index.html
index eb36b8ec8873c2a9ef33cb12d2caa7ddb8e9ba68..f52364f70846cb73b0c2314a0408279a2eba9051 100644 (file)
--- 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
 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>
 {
 
 <p><img src="http://people.skolelinux.org/pere/blog/images/2016-03-19-qr-invoice.png" align="right"><pre>
 {


@@ -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 href="http://www.paperspecs.com/paper-news/beware-the-qr-code-patent-trap/">a
 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
 
 <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/index.rss b/blog/index.rss
index 7364c0cb7cdfba73518cd42c2d10c7bb29d77748..5be2cbecbb7950697be4713b20228923736e9aba 100644 (file)
--- 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
 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>
 {
 
 <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
 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
 
 <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 d043b5b1d4456a3efca6302969854f282101ebc8..63aa56de72caac946fb8ea23ebd427021b5faa0f 100644 (file)
--- 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
 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>
 {
 
 <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
 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
 
 <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 24437079eaf8585a28990a82efecc8fda6a1f33f..aa2343079252f2e1682f44b3ed4586c0e4f7a2b9 100644 (file)
--- 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
 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>
 {
 
 <p><img src="http://people.skolelinux.org/pere/blog/images/2016-03-19-qr-invoice.png" align="right"><pre>
 {


@@ -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 href="http://www.paperspecs.com/paper-news/beware-the-qr-code-patent-trap/">a
 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
 
 <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/standard/index.html b/blog/tags/standard/index.html
index dc915b9d364001e372aba6a4b0bef97518d8a50c..0c25644015d840d70516491239cf3151ea1e6c54 100644 (file)
--- 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
 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>
 {
 
 <p><img src="http://people.skolelinux.org/pere/blog/images/2016-03-19-qr-invoice.png" align="right"><pre>
 {


@@ -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 href="http://www.paperspecs.com/paper-news/beware-the-qr-code-patent-trap/">a
 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
 
 <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/standard/standard.rss b/blog/tags/standard/standard.rss
index 110714eedcf6b106c129e4c847de2f97f3c16669..7cd04175b29b05295ca2adac825f9a9d8bdb91d3 100644 (file)
--- 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
 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>
 {
 
 <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
 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
 
 <p>I also asked if they planned to maintain the format in an
 independent standard organization to give others more confidence that