Sorry, I took your message for irony.
Should have read your blog posts to know better.
Hraban
> Am 28.04.2020 um 18:07 schrieb Henning Hraban Ramm :
>
> Don’t forget, what’s already included in ConTeXt:
>
> \usemodule[visual]
> \useMPlibrary[dum]
>
> \starttext
> \simplethesis
> \stoptext
>
Hi Jan,
> 1. Nameing and organizing the project, product and environments files. I
> am currently reorganising the files for my cooperative. I think that
> besides some nameing conventions it is more or less up to me how I
> organise our print work. Any recommendations welcome.
Download
Don’t forget, what’s already included in ConTeXt:
\usemodule[visual]
\useMPlibrary[dum]
\starttext
\simplethesis
\stoptext
> Am 28.04.2020 um 17:33 schrieb Thangalin :
>
> Jan-Erik, after you have installed all the required software (and
> fonts!) and unzipped the book.zip and themes.zip
Perfect, I will get in to it.
Many thanks and Best wishes, Janne
> 28 apr. 2020 kl. 17:33 skrev Thangalin :
>
> Jan-Erik, after you have installed all the required software (and
> fonts!) and unzipped the book.zip and themes.zip archives, you can
> build a book using:
>
> cd
Jan-Erik, after you have installed all the required software (and
fonts!) and unzipped the book.zip and themes.zip archives, you can
build a book using:
cd $HOME/dev/writing/book
./build -V -c -y -i jekyll-hyde -d standard-ebooks/jekyll-hyde \
-b
Is there a running example ? I’m not sure how to fill in the commandline
> 28 apr. 2020 kl. 09:33 skrev Henning Hraban Ramm :
>
> Yes, the naming is completely up to you.
>
> I use:
>
> project_something.tex
> env_something.tex
> prd_oneissue.tex
> c_onechapter.tex
>
> That’s also what my
Am 28.04.20 um 10:35 schrieb Saša Janiška:
> On Tue, 28 Apr 2020 08:32:57 +0200
> "Jan U. Hasecke" wrote:
>
>> 3. Being a writer I think that Markdown --> ConTeXt is the best way to
>> achieve what I want: easy writing and professional looking books.
>
> I've the same opinion!
>
>> Up to now
On Tue, 28 Apr 2020 08:32:57 +0200
"Jan U. Hasecke" wrote:
> 3. Being a writer I think that Markdown --> ConTeXt is the best way to
> achieve what I want: easy writing and professional looking books.
I've the same opinion!
> Up to now I used Pablos way via pandoc and XHTML described here:
>
> Am 28.04.2020 um 08:32 schrieb Jan U. Hasecke :
>
> 1. Nameing and organizing the project, product and environments files. I
> am currently reorganising the files for my cooperative. I think that
> besides some nameing conventions it is more or less up to me how I
> organise our print work.
Hi Dave,
Am 28.04.20 um 04:00 schrieb Thangalin:
> Hi folks!
>
> Second last part in the series. The project, product, component, and
> environment relations were a bit finicky. Those willing to point out
> improvements that can be made---Hans, Taco, Wolfgang, Aditya, and
> others---would be
Hi folks!
Second last part in the series. The project, product, component, and
environment relations were a bit finicky. Those willing to point out
improvements that can be made---Hans, Taco, Wolfgang, Aditya, and
others---would be very much appreciated.
Specifically, it seems that some project
11 matches
Mail list logo
