From: Petter Reinholdtsen Date: Thu, 2 Apr 2020 20:32:06 +0000 (+0200) Subject: Generated. X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/fcc939eae6ac7268c0b60b364913c5de89494c77?ds=inline Generated. --- diff --git a/blog/PlantUML_for_text_based_UML_diagram_modelling___nice_free_software.html b/blog/PlantUML_for_text_based_UML_diagram_modelling___nice_free_software.html index 6bc08cecdd..c740504670 100644 --- a/blog/PlantUML_for_text_based_UML_diagram_modelling___nice_free_software.html +++ b/blog/PlantUML_for_text_based_UML_diagram_modelling___nice_free_software.html @@ -120,7 +120,7 @@ entities and relations, and there is little layout related fluff. One can reuse content by using include files, allowing for consistent naming across several diagrams. The include files can be standalone PlantUML too. Here is the content of -media/uml-class-arkivskaper.iuml:

+media/uml-class-arkivskaper.iuml:

 @startuml
diff --git a/blog/archive/2019/03/03.rss b/blog/archive/2019/03/03.rss
index 56da5b63ce..a1faad6352 100644
--- a/blog/archive/2019/03/03.rss
+++ b/blog/archive/2019/03/03.rss
@@ -109,7 +109,7 @@ entities and relations, and there is little layout related fluff.  One
 can reuse content by using include files, allowing for consistent
 naming across several diagrams.  The include files can be standalone
 PlantUML too.  Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
 
 <pre>
 @startuml
diff --git a/blog/archive/2019/03/index.html b/blog/archive/2019/03/index.html
index 2b04734d73..2d96af730a 100644
--- a/blog/archive/2019/03/index.html
+++ b/blog/archive/2019/03/index.html
@@ -127,7 +127,7 @@ entities and relations, and there is little layout related fluff.  One
 can reuse content by using include files, allowing for consistent
 naming across several diagrams.  The include files can be standalone
 PlantUML too.  Here is the content of
-media/uml-class-arkivskaper.iuml:

+media/uml-class-arkivskaper.iuml:

 @startuml
diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss
index 951efc383f..55d7d790fc 100644
--- a/blog/tags/english/english.rss
+++ b/blog/tags/english/english.rss
@@ -968,7 +968,7 @@ entities and relations, and there is little layout related fluff.  One
 can reuse content by using include files, allowing for consistent
 naming across several diagrams.  The include files can be standalone
 PlantUML too.  Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
 
 <pre>
 @startuml
diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html
index 6394b01ead..a358e37430 100644
--- a/blog/tags/english/index.html
+++ b/blog/tags/english/index.html
@@ -1141,7 +1141,7 @@ entities and relations, and there is little layout related fluff.  One
 can reuse content by using include files, allowing for consistent
 naming across several diagrams.  The include files can be standalone
 PlantUML too.  Here is the content of
-media/uml-class-arkivskaper.iuml:

+media/uml-class-arkivskaper.iuml:

 @startuml
diff --git a/blog/tags/nice free software/index.html b/blog/tags/nice free software/index.html
index 90afd525b7..6a18c57f40 100644
--- a/blog/tags/nice free software/index.html	
+++ b/blog/tags/nice free software/index.html	
@@ -126,7 +126,7 @@ entities and relations, and there is little layout related fluff.  One
 can reuse content by using include files, allowing for consistent
 naming across several diagrams.  The include files can be standalone
 PlantUML too.  Here is the content of
-media/uml-class-arkivskaper.iuml:

+media/uml-class-arkivskaper.iuml:

 @startuml
diff --git a/blog/tags/nice free software/nice free software.rss b/blog/tags/nice free software/nice free software.rss
index 7d3007bfec..34874fbbb0 100644
--- a/blog/tags/nice free software/nice free software.rss	
+++ b/blog/tags/nice free software/nice free software.rss	
@@ -109,7 +109,7 @@ entities and relations, and there is little layout related fluff.  One
 can reuse content by using include files, allowing for consistent
 naming across several diagrams.  The include files can be standalone
 PlantUML too.  Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
 
 <pre>
 @startuml
diff --git a/blog/tags/noark5/index.html b/blog/tags/noark5/index.html
index bb12a47b94..50c22ee4a6 100644
--- a/blog/tags/noark5/index.html
+++ b/blog/tags/noark5/index.html
@@ -885,7 +885,7 @@ entities and relations, and there is little layout related fluff.  One
 can reuse content by using include files, allowing for consistent
 naming across several diagrams.  The include files can be standalone
 PlantUML too.  Here is the content of
-media/uml-class-arkivskaper.iuml:

+media/uml-class-arkivskaper.iuml:

 @startuml
diff --git a/blog/tags/noark5/noark5.rss b/blog/tags/noark5/noark5.rss
index 5a05fad3e1..3f15ab3e93 100644
--- a/blog/tags/noark5/noark5.rss
+++ b/blog/tags/noark5/noark5.rss
@@ -748,7 +748,7 @@ entities and relations, and there is little layout related fluff.  One
 can reuse content by using include files, allowing for consistent
 naming across several diagrams.  The include files can be standalone
 PlantUML too.  Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
 
 <pre>
 @startuml
diff --git a/blog/tags/nuug/index.html b/blog/tags/nuug/index.html
index d2eca7b648..c2a11b1ae6 100644
--- a/blog/tags/nuug/index.html
+++ b/blog/tags/nuug/index.html
@@ -370,7 +370,7 @@ entities and relations, and there is little layout related fluff.  One
 can reuse content by using include files, allowing for consistent
 naming across several diagrams.  The include files can be standalone
 PlantUML too.  Here is the content of
-media/uml-class-arkivskaper.iuml:

+media/uml-class-arkivskaper.iuml:

 @startuml
diff --git a/blog/tags/nuug/nuug.rss b/blog/tags/nuug/nuug.rss
index e90b4aca9c..fa8e1a5fdf 100644
--- a/blog/tags/nuug/nuug.rss
+++ b/blog/tags/nuug/nuug.rss
@@ -317,7 +317,7 @@ entities and relations, and there is little layout related fluff.  One
 can reuse content by using include files, allowing for consistent
 naming across several diagrams.  The include files can be standalone
 PlantUML too.  Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
 
 <pre>
 @startuml
diff --git a/blog/tags/standard/index.html b/blog/tags/standard/index.html
index b9f464b188..863f4ffe73 100644
--- a/blog/tags/standard/index.html
+++ b/blog/tags/standard/index.html
@@ -838,7 +838,7 @@ entities and relations, and there is little layout related fluff.  One
 can reuse content by using include files, allowing for consistent
 naming across several diagrams.  The include files can be standalone
 PlantUML too.  Here is the content of
-media/uml-class-arkivskaper.iuml:

+media/uml-class-arkivskaper.iuml:

 @startuml
diff --git a/blog/tags/standard/standard.rss b/blog/tags/standard/standard.rss
index a2dcd1f7fc..2a969f0ce7 100644
--- a/blog/tags/standard/standard.rss
+++ b/blog/tags/standard/standard.rss
@@ -713,7 +713,7 @@ entities and relations, and there is little layout related fluff.  One
 can reuse content by using include files, allowing for consistent
 naming across several diagrams.  The include files can be standalone
 PlantUML too.  Here is the content of
-<tt>media/uml-class-arkivskaper.iuml<tt>:</p>
+<tt>media/uml-class-arkivskaper.iuml</tt>:</p>
 
 <pre>
 @startuml