summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/latex/skb/user-guide/repository/story
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/latex/skb/user-guide/repository/story')
-rw-r--r--Master/texmf-dist/doc/latex/skb/user-guide/repository/story/long.tex5
-rw-r--r--Master/texmf-dist/doc/latex/skb/user-guide/repository/story/long2.tex4
-rw-r--r--Master/texmf-dist/doc/latex/skb/user-guide/repository/story/short.tex20
3 files changed, 13 insertions, 16 deletions
diff --git a/Master/texmf-dist/doc/latex/skb/user-guide/repository/story/long.tex b/Master/texmf-dist/doc/latex/skb/user-guide/repository/story/long.tex
index 081a16dd14d..b03ebcb51ae 100644
--- a/Master/texmf-dist/doc/latex/skb/user-guide/repository/story/long.tex
+++ b/Master/texmf-dist/doc/latex/skb/user-guide/repository/story/long.tex
@@ -1,5 +1,4 @@
\opt{text}{\skbheading{The Long Story}}
-\opt{note}{\skbheading{The Long Story, Part I}}
Over several years of writing documents (articles, books, reports, standards, research proposals)
ideas and concepts became distributed (actually a euphemism for 'hidden') within many many documents
@@ -9,11 +8,11 @@ are manifold:
\begin{skbnotelist}
\item Ideas/concepts are hidden, often un-accessible and, as I experienced, search tools are of limited help.
\item The documents are written in all sorts of formats or available only in (usually proprietary) binary
- formats. Ever tried to open a document written in MS WinWord 6.0 with customised document
+ formats. Ever tried to open a document written in \skbacft{company:MS} WinWord 6.0 with customised document
template in a newer version of the same programme? You know then what I am talking about.
\item Reusing the ideas/concepts, once found in a document and managed to open that very document,
usually involves huge amount of re-formatting. This will produce mistakes. Ever tried to
- use a {\scshape Bib}\TeX) generated reference list, found in a PDF file in a new article?
+ use a {\scshape Bib}\TeX) generated reference list, found in a \skbacft{ISO:PDF} file in a new article?
I found better ways to spend my nights and weekends (yes, I am married and I have a garden).
\item Over time, it can become very difficult to distinguish between different versions of a
document, concept and/or idea. As it happens in real life, things move on even in computing
diff --git a/Master/texmf-dist/doc/latex/skb/user-guide/repository/story/long2.tex b/Master/texmf-dist/doc/latex/skb/user-guide/repository/story/long2.tex
index 60ddd759ea2..27eaeea3fb5 100644
--- a/Master/texmf-dist/doc/latex/skb/user-guide/repository/story/long2.tex
+++ b/Master/texmf-dist/doc/latex/skb/user-guide/repository/story/long2.tex
@@ -1,5 +1,3 @@
-\opt{note}{\skbheading{The Long Story, Part II}}
-
A solution is to create a unified document repository, then use
this repository as 'normative source' to create documents for specific
purposes while leaving the text blocks, headings, figures, presentations,
@@ -23,7 +21,7 @@ times). I ended up with 1,314 files in 87 folders, which create 9 articles, 2
books, 1 textbook, 3 lecture notes and this document (note: the number of
articles increased, because I could re-assemble 'stuff' for new uses,
spending some five minutes per one new article). I did remove roughly 100
-pages of text (take the classic Spring LNCS format and you get the point
+pages of text (take the classic Spring \skbacft{Springer:LNCS} format and you get the point
of the number of characters) and some 40 figures (all duplicates). I did
find way too many errors in the original sources (most of which have been
created by 're-using' them earlier from even more-original-sources).
diff --git a/Master/texmf-dist/doc/latex/skb/user-guide/repository/story/short.tex b/Master/texmf-dist/doc/latex/skb/user-guide/repository/story/short.tex
index 26824e29408..330f72a1066 100644
--- a/Master/texmf-dist/doc/latex/skb/user-guide/repository/story/short.tex
+++ b/Master/texmf-dist/doc/latex/skb/user-guide/repository/story/short.tex
@@ -1,4 +1,4 @@
-\skbheading{The Short Story}
+\opt{text}{\skbheading{The Short Story}}
I have written papers, done a lot of presentations, provided some book chapters,
still working on a book, participated in many research proposals and projects, and
@@ -6,7 +6,7 @@ created tons of notes and figures. As of early 2009, most of that information wa
distributed over the repositories of different projects and organisations I worked
for, in some document management systems, on several websites, databases, my preferred
email client (which changed twice), different computers and later even different
-external hard drives and USB sticks. Looking for specific text or a particular figure
+external hard drives and \skbacft{USB} sticks. Looking for specific text or a particular figure
could easily end in a days work. Tools like desktop search engines can help to find
'stuff'. I used them, but if they found anything it was hard to maintain the context
it was written in and some formats or sources were out of reach for them. Even worse
@@ -15,17 +15,17 @@ jobs and several years, all I had is kind of a very messy base of knowledge, wel
somewhere, thus very difficult to locate and impossible to maintain.
So I started early 2009 to re-organise my 'stuff'. At the same time, I did realise that
-moving away from \LaTeX was part of the problem (and I thought using the other text
-processor would help, it actually didn't, long-term). So \LaTeX became, again, the
+moving away from \LaTeX~was part of the problem (and I thought using the other text
+processor would help, it actually didn't, long-term). So \LaTeX~became, again, the
text processor of choice, and with it the ability for a complete different approach
-to organise my 'stuff'. This was the moment the \SKB~was created. \SKB~stands for Sven's
-Knowledge Base. The \LaTeX package \skbem[code]{skb}, described in this article, forms part of a larger
-software system that uses SQLite databases, a small PHP framework, Apache for HTML access
+to organise my 'stuff'. This was the moment the \skbacft{A3DS:SKB} was created. \skbacft{A3DS:SKB} stands for Sven's
+Knowledge Base. The \LaTeX~package \skbem[code]{skb}, described in this article, forms part of a larger
+software system that uses \skbacft{ISO:SQL}ite databases, a small \skbacft{PHP} framework, Apache for \skbacft{W3C:HTML} access
and recently also a Java port.
My document repository uses the \skbem[code]{skb} package, so most of my documents are eventually
-\LaTeX documents. I am saying eventually because I still use other tools (like Microsoft's Powerpoint),
+\LaTeX~documents. I am saying eventually because I still use other tools (like Microsoft's Powerpoint),
but integrate their output in my repository. I do all my figures these days using Inkscape, so the source
-is SVG and the output for \LaTeX documents PDF. For editing the text files I do flip between UE Studio
-and LeD. Parts of the content (such as acronyms and bibliographic information) are maintained in SQLite
+is \skbacft{W3C:SVG} and the output for \LaTeX~documents \skbacft{ISO:PDF}. For editing the text files I do flip between UE Studio
+and LeD. Parts of the content (such as acronyms and bibliographic information) are maintained in \skbacft{ISO:SQL}ite
databases and exported to \LaTeX. This package now shows how I build my documents. \ No newline at end of file