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
https://dave.autonoma.ca/blog/2019/08/06/typesetting-markdown-part-7/
This installment tackles a cost-benefit analysis problem comparing
electric to gasoline-powered vehicles, calls into R for amortization,
typesets math and a repayment schedule, continues to explore the
separation of content
This part of the series describes a way to produce and typeset dynamic
documents using R Markdown and ConTeXt.
https://dave.autonoma.ca/blog/2019/07/11/typesetting-markdown-part-6/
Comments or suggestions for improvement?
Thank you. I still don't really understand why can't you have a
"presentational" yaml file and a "content" yaml file (I do it like that...
I have a "variables.yaml" file for content and a "settings.yaml" file for
presentational stuff, and use a "template.context" file with all my mapped
variables
tfamily and \definefallbackfamily
>> (Pablo Rodriguez)
>>5. Re: crappy names in the fontloader (Hans Hagen)
>>6. problems with images, layers and crop marks (Henning Hraban Ramm)
>>7. Re: problems with images, layers and crop marks (Hans Hagen)
>>
--
>
> Message: 1
> Date: Sun, 7 Jul 2019 10:17:31 -0400 (EDT)
> From: Aditya Mahajan
> To: mailing list for ConTeXt users
> Subject: Re: [NTG-context] Typesetting Markdown – Part 5:
> Interpolation
> Message
Thanks again for the great ideas. The downside is that it comes with a lot
of extra ConTeXt setup code. My understanding is that the toc parameter to
pandoc only works when creating a standalone document. I think
\def\completecontent\empty is a bit more expressive of intent than
On Sun, 7 Jul 2019, Thangalin wrote:
Thank you Aditya.
The main.tex file is meant to be reusable for different document styles. By
removing \completecontent altogether from the main template, it would
preclude a different document from reusing the main.tex template with a
table of contents.
Thank you Aditya.
The main.tex file is meant to be reusable for different document styles. By
removing \completecontent altogether from the main template, it would
preclude a different document from reusing the main.tex template with a
table of contents. I'd like the template to be "reusable";
On Sat, 6 Jul 2019, Thangalin wrote:
Hello again!
This part of the series describes how to reference *interpolated* strings
inside Markdown documents.
https://dave.autonoma.ca/blog/2019/07/06/typesetting-markdown-part-5/
There's a section at the end about eliminating the table of contents
Hello again!
This part of the series describes how to reference *interpolated* strings
inside Markdown documents.
https://dave.autonoma.ca/blog/2019/07/06/typesetting-markdown-part-5/
There's a section at the end about eliminating the table of contents from a
reusable document template. I would
Hi all!
This part of the series describes a way to define colours, fonts, and
layout such that content is separated from presentation.
https://dave.autonoma.ca/blog/2019/06/23/typesetting-markdown-part-4/
Questions, corrections, and improvements are welcome.
On 17-06-19 19:31, Thangalin wrote:
>
> Definitely. Part 4 will be about themes.
great !
.F
pEpkey.asc
Description: application/pgp-keys
___
If your question is of interest to others as well, please add an entry
> Maybe some instructions as how to adjust/redefine the pandoc output?
Please elaborate.
> e.g. how to include different style templates for ConTeXt.
Definitely. Part 4 will be about themes.
Thank you!
___
If your
On 17-06-19 07:54, Thangalin wrote:
> Hi all!
>
> The third part of the series describes a way to perform continuous
> integration when writing Markdown that is typeset using ConTeXt.
>
> https://dave.autonoma.ca/blog/2019/06/16/typesetting-markdown-part-3/
>
> Suggestions for improvement are
Hi all!
The third part of the series describes a way to perform continuous
integration when writing Markdown that is typeset using ConTeXt.
https://dave.autonoma.ca/blog/2019/06/16/typesetting-markdown-part-3/
Suggestions for improvement are welcome.
Thank you.
David Nebauer writes:
> https://github.com/Witiko/markdown is forked from
> https://github.com/jgm/lunamark. Github user "jgm" is John MacFarlane,
> the creator of pandoc, and pandoc itself is hosted on github under
> "jgm" as well: https://github.com/jgm/pandoc.
>
> So, it seems a good bet that
>
> sense to check all these mappings onto context, for instance I think
> that pandoc uses \section and such while in fact it should use
> \startsectionlevel[title={}] ... \stopsectionlevel so that one can embed
> documents in other documents.
>
https://github.com/jgm/pandoc/issues/5539
Feel
https://github.com/Witiko/markdown is forked from https://github.com/jgm/lunamark. Github user
"jgm" is John MacFarlane, the creator of pandoc, and pandoc itself is hosted on github
under "jgm" as well: https://github.com/jgm/pandoc.
So, it seems a good bet that
On 5/30/2019 12:18 PM, Saša Janiška wrote:
Hans Hagen writes:
just test it and tell me what needs to be fixed / added
I'm looking at https://github.com/Witiko/markdown and wondering which
flavour of Markdown this package does support?
By reading https://github.com/Witiko/markdown/issues/25
Hans Hagen writes:
> just test it and tell me what needs to be fixed / added
I'm looking at https://github.com/Witiko/markdown and wondering which
flavour of Markdown this package does support?
By reading https://github.com/Witiko/markdown/issues/25 it could mean it
could be Pandoc's one, but
On 5/29/2019 11:54 PM, Thangalin wrote:
Hi all,
The second part describes how to create a PDF file from a Markdown file
using pandoc and ConTeXt:
https://dave.autonoma.ca/blog/2019/05/29/typesetting-markdown-part-2/
If anyone has suggestions to improve the ConTeXt-related portions,
please
Hi all,
The second part describes how to create a PDF file from a Markdown file
using pandoc and ConTeXt:
https://dave.autonoma.ca/blog/2019/05/29/typesetting-markdown-part-2/
If anyone has suggestions to improve the ConTeXt-related portions, please
pass them along.
I've considered using
On 5/25/19 9:54 PM, Thangalin wrote:
>[...]
> For the document language, Pandoc provides language variables:
>
> https://pandoc.org/MANUAL.html#language-variables
> [...]
> Intermixing languages is also possible, as per the above link.
As far as I can remember, neither of them were available when
> For Markdown --> ConTeXt usage, math is not my primary concern, but
> wonder what do you think about the Pandoc's "cons" as stated on
> pandoc-xhtml site, iow:
>
> * Main document language information.
> * Markup for language in text portions.
> * Any or elements markup.
>
For the document
On 5/24/19 5:37 AM, Thangalin wrote:
> Hi Gour,
>
> I added an abstract, an overview section with the plan, and an RSS feed:
>
> https://dave.autonoma.ca/blog/2019/05/22/typesetting-markdown-part-1/
>
> One of the reasons I chose Pandoc's Markdown is for its support of
> classes and annotations. I
Thangalin writes:
> I added an abstract, an overview section with the plan, and an RSS
> feed:
Thanks a lot - now it's much better seeing what is ahead of us. ;)
> One of the reasons I chose Pandoc's Markdown is for its support of
> classes and annotations.
I was not using Pandoc's markdown,
Hi Gour,
I added an abstract, an overview section with the plan, and an RSS feed:
https://dave.autonoma.ca/blog/2019/05/22/typesetting-markdown-part-1/
One of the reasons I chose Pandoc's Markdown is for its support of classes
and annotations. I looked into the pandoc-xhtml link and it looked
Thangalin writes:
> I'm thinking about writing a series of blog posts about how to typeset
> Markdown using ConTeXt. I've written the first part and am wondering
> if anyone would be interested in reading more:
I'm interested for the topic, but it would be nice, imho, if the Part-1
would
Am 23.05.19 um 07:18 schrieb Thangalin:
> Hi folks!
>
> I'm thinking about writing a series of blog posts about how to typeset
> Markdown using ConTeXt. I've written the first part and am wondering if
> anyone would be interested in reading more:
>
>
Hi folks!
I'm thinking about writing a series of blog posts about how to typeset
Markdown using ConTeXt. I've written the first part and am wondering if
anyone would be interested in reading more:
https://dave.autonoma.ca/blog/2019/05/22/typesetting-markdown-part-1/
Thank you!
41 matches
Mail list logo
