perro
/
perrotuerto.blog
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Más correcciones al 5

This commit is contained in:
perro tuerto 2020-02-13 12:27:07 -06:00
parent cb3a629e23
commit f7e72431c7
1 changed files with 61 additions and 35 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

96
content/md/005_hiim-master.md
View File

@ -1,6 +1,6 @@
# How It Is Made: Master Research Thesis
> @published 2020/02/10, 12:00 {.published}
> @published 2020/02/13, 20:00 {.published}
Uff, after six months of writing, reviewing, deleting, yelling
and almost giving up, I finally finished the Master's research
@ -27,9 +27,10 @@ because:
In general the thesis is actually an automated repository where
you can see everything---including the entire bibliography, the
site and the writing history. The methodology is based on automated
and multiformat standardized publishing, or as I like to call
it: branched publishing.
site and the writing history. The research uses a [rolling release](https://en.wikipedia.org/wiki/Rolling_release)
model---“the concept of frequently delivering updates.” The methodology
is based on automated and multiformat standardized publishing,
or as I like to call it: branched publishing.
This isn't the space to discuss the method, but these are some
general ideas:
@ -76,16 +77,16 @@ for some formats as it helps me save a lot of time.
For inputs and output formats I think Pandoc is a great general
purpose tool, but not enough for a fussy publisher like this
perro. Plus, I love scripting so I prefer to employ my time on
that instead of configuring Pandoc's outputs---it helps me learn
more. So in this publishing process, Pandoc is used when I haven't
resolved something or I'm too lazy to do it, +++LOL+++.
_perro_. Plus, I love scripting so I prefer to employ my time
on that instead of configuring Pandoc's outputs---it helps me
learn more. So in this publishing process, Pandoc is used when
I haven't resolved something or I'm too lazy to do it, +++LOL+++.
Unlike text processing formats as +++ODT+++ or +++DOCX+++, +++MD+++
is very easy to customize. You don't need to install plugins,
rather you just generate more syntax!
So [Pecas Markdown](http://pecas.perrotuerto.blog/html/md.html)
So [Pecas' Markdown](http://pecas.perrotuerto.blog/html/md.html)
was the base format for the content. The additional syntax was
for citing the bibliography by its id.
@ -145,7 +146,7 @@ When the bibliography is processed I get something like this:
This syntax is based on LaTeX textual and parenthetical citations
styles for [BibLaTeX](http://tug.ctan.org/info/biblatex-cheatsheet/biblatex-cheatsheet.pdf).
The at sign (`@`) is the character I use at the beginning of
any additional syntax for Pecas Markdown. For processing purposes
any additional syntax for Pecas' Markdown. For processing purposes
I could use any other kind of syntax. But for writing and editing
tasks I found the at sign to be very accessible and easy to find.
@ -176,7 +177,7 @@ can pick what they like best.
Seeing how publishing is becoming more and more centralized,
unfortunately the deployment of +++MOBI+++ formats for Kindle
readers is recommendable---by the way, +++FUCK+++ Amazon, they
steal from writers and publishers. Use Amazon only if the text
steal from writers and publishers; use Amazon only if the text
isn't in another source. I don't like proprietary software as
Kindlegen, but it is the only _legal_ way to deploy +++MOBI+++
files. I hope that little by little Kindle readers at least start
@ -199,6 +200,7 @@ So, the following outputs are:
* +++EPUB+++ as standard ebook format.
* +++MOBI+++ for Kindle readers.
* +++PDF+++ for printing.
* +++HTML+++ for web surfers.
* +++DOCX+++ as editable file.
### Ebooks
@ -207,7 +209,7 @@ So, the following outputs are:
I don't use Pandoc for ebooks, instead I use a publishing tool
we are developing: [Pecas](pecas.perrotuerto.blog). “Pecas” means
“freckles”, but in this context it's in honor of a pinto dog
“freckles,” but in this context it's in honor of a pinto dog
from my childhood.
Pecas allows me to deploy +++EPUB+++ and +++MOBI+++ formats from
@ -250,6 +252,15 @@ to automate this process. In a further section I explain this.
![The research in its +++PDF+++ output; I don't like justified text, it's bad for your eyes.](../../../img/p005_i003.png)
### HTML
The +++EPUB+++ format is actually a bunch of compressed +++HTML+++
files plus metadata and a table of contents. So there is no reason
to avoid a +++HTML+++ output. I already have it by converting
the +++MD+++ with Pecas. I don't think someone is gonna read
25K words in a web browser, but you never know. It could work
for a quick look.
### DOCX
This output doesn't have anything special. I didn't customize
@ -371,13 +382,12 @@ put footnotes in the following situations:
they can “earn” objectivity.
I think the thesis needs more rewriting, I could have written
things in a more comprehensive way, but I was done---_writing_
things in a more comprehensive way, but I was done---writing
philosophy is not my thing, I prefer to speak or program (!)
it. That is why I took my time on the review process---ask my
tutor about that, +++LMFAO+++. It would have been easier for
me to just add in footnotes, but it would have been harder to
read that shit. Besides that, footnotes take more space than
rewriting.
me to just add footnotes, but it would have been harder to read
that shit. Besides that, footnotes take more space than rewriting.
So, with respect to the reader and in agreement with the text
extension of my university, I decided not to use footnotes.
@ -412,7 +422,7 @@ characters with spaces, words and three different page sizes:
by every 1,800 characters with spaces, by every 250 words and
an average of both---you can set other lengths for page sizes.
The +++MD+++ beautifier is `texti. For the moment it only works
The +++MD+++ beautifier is `texti`. For the moment it only works
well with paragraphs. It was good enough for me, my issue was
with the disparate length of lines---yeah, I don't use line wrap.
@ -571,13 +581,16 @@ inputs and outputs inside the repo:
│   ├─ [17] tesis.epub
│   └─ [18] tesis.mobi
├─ [19] generate-all
├─ [20] md
│   ├─ [21] add-bib
│   ├─ [22] tesis.md
│   └─ [23] tesis_with-bib.md
└─ [24] pdf
├─ [25] generate
└─ [26] tesis.pdf
├─ [20] html
│ ├─ [21] generate
│ └─ [22] tesis.html
├─ [23] md
│   ├─ [24] add-bib
│   ├─ [25] tesis.md
│   └─ [26] tesis_with-bib.md
└─ [27] pdf
├─ [28] generate
└─ [29] tesis.pdf
```
### Bibliography pathway
@ -603,12 +616,17 @@ on the engine!
The wrapper does the following steps:
1. It adds the bibliography [21] to the original +++MD+++ file [22],
leaving a new file [23] to act as input.
2. It compiles [25] the +++PDF+++ output [26].
3. It generates [13] the +++EPUB+++ [17] and +++MOBI+++ [18] according
1. It adds the bibliography [24] to the original +++MD+++ file [25],
leaving a new file [26] to act as input.
2. It generates [21] the +++HTML+++ output [22].
3. It compiles [28] the +++PDF+++ output [29].
4. It generates [13] the +++EPUB+++ [17] and +++MOBI+++ [18] according
to their metadata [16] and Pecas config file [15].
4. It exports [10] the +++MD+++ to +++DOCX+++ [11].
5. It exports [10] the +++MD+++ to +++DOCX+++ [11].
6. It moves the analytics to its correct directory.
7. It refreshes the modification date in the index [07].
8. It puts the rolling release hash in the index [07].
9. It puts the +++MD5+++ checksum of all outputs in the index [07].
And that's it. The process of developing a thesis as a automate
repository allows me to just worry about three things:
@ -657,22 +675,30 @@ license for its content and a copyleft license for its code.
Actually, it's the same licensing scheme of [this blog](https://perrotuerto.blog/content/html/en/_fork.html).
With Open and Free Publishing License (abbreviated +++LEAL+++,
that also means “loyal”) you are free to use, copy, reedit, modify,
share or sell any of this content under the following conditions:
that also means “loyal” in Spanish) you are free to use, copy,
reedit, modify, share or sell any of this content under the following
conditions:
* Anything produced with this content must be under some type of +++LEAL+++.
* All files---editable or final formats---must be publicly accessible.
* The content usage cannot imply defamation, exploitation or surveillance.
You could remove my name and put yours, it's permmited. You could
even modify the content and write that I +++LOVE+++ intellectual
property: there isn't a technical solution to avoid such defamation.
But +++MD5+++ checksum shows if the files were modify by others.
Even if the files differs by one bit, the +++MD5+++ checksum
is gonna be different.
Copyfarleft is the way---but not the solution---that suits our
context and our possibilities of freedom. Don't come here with
context and our possibilities of freedom. [Don't come here with
your liberal and individualistic notion of freedom---like the
dudes from Weblate that kicked this blog out because its content
license “is not free,” even though they say the code, but not
the content, should use a “free” license, like the fucking +++GPL+++
this blog has for its code. This type of liberal freedom doesn't
work in a place where no State or corporation can warrant us
a minimum set of individual freedoms, as it happens in Asia,
this blog has for its code]{#weblate}. This type of liberal freedom
doesn't work in a place where no State or corporation can warrant
us a minimum set of individual freedoms, as it happens in Asia,
Africa and the other America---Latin America and the America
that isn't portrayed in the “American Dream” adds.