Blogging in LaTeX.doc -> latex preserving fontHow can I convert the tables and math in a latex document to one of the markup languages supported by github's wiki?Converting Markdown to LaTeX, in LaTeXDoes a LaTeX to Kramdown converter exist?LaTeX to Markdown converterMarkdown-like tool for converting “human” text to reasonable LaTeX code?Converting PreTeXt to LaTeX
How can I store milk for long periods of time?
Punishment in pacifist society
Could these polynomials be identified?
Using font to highlight a god's speech in dialogue
Calculate Landau's function
Are there consequences for not filing a DMCA (any country)
Why do we need explainable AI?
How can I portray a character with no fear of death, without them sounding utterly bored?
Should we run PBKDF2 for every plaintext to be protected or should we run PBKDF2 only once?
What is the maximal acceptable delay between pilot's input and flight control surface actuation?
What are the electrical characteristics of a PC gameport?
Replace a motion-sensor/timer with simple single pole switch
Divide Numbers by 0
Can users with the same $HOME have separate bash histories?
If the government illegally doesn't ask for article 50 extension, can parliament do it instead?
New coworker has strange workplace requirements - how should I deal with them?
Turn off Google Chrome's Notification for "Flash Player will no longer be supported after December 2020."
Can a country avoid prosecution for crimes against humanity by denying it happened?
How could reincarnation magic be limited to prevent overuse?
How would a disabled person earn their living in a medieval-type town?
How do you manage to study and have a balance in your life at the same time?
Why didn't Thatcher give Hong Kong to Taiwan?
Colored grid with coordinates on all sides?
Datasets of Large Molecules
Blogging in LaTeX
.doc -> latex preserving fontHow can I convert the tables and math in a latex document to one of the markup languages supported by github's wiki?Converting Markdown to LaTeX, in LaTeXDoes a LaTeX to Kramdown converter exist?LaTeX to Markdown converterMarkdown-like tool for converting “human” text to reasonable LaTeX code?Converting PreTeXt to LaTeX
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
It seems to me that all (static) blogging frameworks, e.g. Jekyll and Hugo use Markdown as format for blog posts. But according to
Hartl’s Tenth Rule of Typesetting
Any sufficiently complicated
typesetting system contains an ad hoc, informally specified,
bug-ridden, slow implementation of half of LATEX.
(http://manual.softcover.io/book/softcover_markdown)
Markdown (plus it's numerous extensions) is not a good format in comparison to LaTeX (especially when it comes to long-term stability). So are there any static blogging frameworks out there which use LaTeX as format for blog posts? Or are there any LaTeX to markdown converter which could be used in conjunction with common static blogging frameworks?
conversion markdown blog
asked 8 hours ago
asmaierasmaier
1,4412 gold badges11 silver badges6 bronze badges
add a comment |
It seems to me that all (static) blogging frameworks, e.g. Jekyll and Hugo use Markdown as format for blog posts. But according to
Hartl’s Tenth Rule of Typesetting
Any sufficiently complicated
typesetting system contains an ad hoc, informally specified,
bug-ridden, slow implementation of half of LATEX.
(http://manual.softcover.io/book/softcover_markdown)
Markdown (plus it's numerous extensions) is not a good format in comparison to LaTeX (especially when it comes to long-term stability). So are there any static blogging frameworks out there which use LaTeX as format for blog posts? Or are there any LaTeX to markdown converter which could be used in conjunction with common static blogging frameworks?
conversion markdown blog
asked 8 hours ago
asmaierasmaier
1,4412 gold badges11 silver badges6 bronze badges
add a comment |
It seems to me that all (static) blogging frameworks, e.g. Jekyll and Hugo use Markdown as format for blog posts. But according to
Hartl’s Tenth Rule of Typesetting
Any sufficiently complicated
typesetting system contains an ad hoc, informally specified,
bug-ridden, slow implementation of half of LATEX.
(http://manual.softcover.io/book/softcover_markdown)
Markdown (plus it's numerous extensions) is not a good format in comparison to LaTeX (especially when it comes to long-term stability). So are there any static blogging frameworks out there which use LaTeX as format for blog posts? Or are there any LaTeX to markdown converter which could be used in conjunction with common static blogging frameworks?
conversion markdown blog
asked 8 hours ago
asmaierasmaier
1,4412 gold badges11 silver badges6 bronze badges
It seems to me that all (static) blogging frameworks, e.g. Jekyll and Hugo use Markdown as format for blog posts. But according to
Hartl’s Tenth Rule of Typesetting
Any sufficiently complicated
typesetting system contains an ad hoc, informally specified,
bug-ridden, slow implementation of half of LATEX.
(http://manual.softcover.io/book/softcover_markdown)
Markdown (plus it's numerous extensions) is not a good format in comparison to LaTeX (especially when it comes to long-term stability). So are there any static blogging frameworks out there which use LaTeX as format for blog posts? Or are there any LaTeX to markdown converter which could be used in conjunction with common static blogging frameworks?
conversion markdown blog
conversion markdown blog
asked 8 hours ago
asmaierasmaier
1,4412 gold badges11 silver badges6 bronze badges
asked 8 hours ago
asmaierasmaier
1,4412 gold badges11 silver badges6 bronze badges
asked 8 hours ago
asmaierasmaier
1,4412 gold badges11 silver badges6 bronze badges
asked 8 hours ago
asmaierasmaier
1,4412 gold badges11 silver badges6 bronze badges
asked 8 hours ago
asmaierasmaier
1,4412 gold badges11 silver badges6 bronze badges
1,4412 gold badges11 silver badges6 bronze badges
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You can utilize the fact that Markdown also supports HTML, so to support LaTeX in static site generators you just need to convert LaTeX to HTML. It is then necessary to extract just the contents of the <body> element and add an YAML header, just like in the Markdown file. make4ht can do this automatically.
In my planned blog, I have the following directory structure:
texposts/
.make4ht
first_post/
hello.tex
second_post
world.tex
build/
www/
There are three top level directories, texposts for LaTeX documents, build where HTML files to be processed are saved and www, which is populated by the static site generator.
The .make4ht file is a special configuration file for make4ht:
local outdir = os.getenv "kodymirus_root" or "out"
local domfilter = require "make4ht-domfilter"
-- remove the maketitle environment from the HTML file, title will be inserted in the template
local domprocess = domfilterfunction(dom)
local maketitles = dom:query_selector(".maketitle")
for _, el in ipairs(maketitles) do
print "removing maketitle"
el:remove_node()
end
return dom
end
filter_settings "staticsite"
site_root = outdir,
map =
[".css$"] = "css/"
,
header =
layout="post",
date = function(parameters)
return os.date("!%Y-%m-%d %T", parameters.time)
end
Make:enable_extension "common_domfilters"
if mode=="draft" then
Make:htlatex
elseif mode=="publish" then
-- Make:htlatex
Make:match("html$", domprocess)
Make:enable_extension "tidy"
Make:enable_extension "staticsite"
Make:htlatex
else
Make:htlatex
Make:htlatex
Make:htlatex
end
It is a Lua script which drives the conversion from LaTeX to HTML. There are few interesting things:
local outdir = os.getenv "kodymirus_root" or "out"
This reads an environmental variable set in my .bashrc that contains path to the build directory.
filter_settings "staticsite"
This contains settings for the staticsite extension:
site_root = outdir,
set the output directory
map =
[".css$"] = "css/"
,
move the generated files that match the regular expression to a specified directory. This example moves CSS files to the css subdirectory in the build dir.
header =
In the header we can set additional fields for the YAML header.
elseif mode=="publish" then
-- Make:htlatex
Make:match("html$", domprocess)
Make:enable_extension "tidy"
Make:enable_extension "staticsite"
Make:htlatex
make4ht supports so called modes. These modes can be selected on the command line using the -m option. By default, this configuration file will create a standalone HTML file. Only when the post is done, you can execute the publish mode, which enables the staticsite extension and publishes the document to the build dir.
To publish the document execute the following command in the texposts/first directory:
make4ht -um publish hello.tex
Here is an example TeX file:
documentclassarticle
titleBlogging with LaTeX
authorMichal
begindocument
maketitle
tableofcontents
sectionIntroduction
textitpříliš žluťoučký
printbibliography
enddocument
And this is the generated document:
---
layout: 'post'
updated: 1524600200
styles:
- '2018-04-18-blogging-with-latex.css'
meta:
- content: 'HTML Tidy for HTML5 for Linux version 5.4.0'
name: 'generator'
- charset: 'utf-8'
- content: 'TeX4ht (http://www.tug.org/tex4ht/)'
name: 'generator'
- content: 'width=device-width,initial-scale=1'
name: 'viewport'
- content: '2018-04-18-blogging-with-latex.tex'
name: 'src'
title: 'Blogging with LaTeX'
date: '2018-04-18 20:31:14'
time: 1524083474
---
<h3 class='likesectionHead'><a id='x1-1000'></a>Contents</h3>
<div class='tableofcontents'><span class='sectionToc'>1 <a id='QQ2-1-2' href='#x1-20001'>Introduction</a></span></div>
<!-- l. 17 -->
<p class='noindent'></p>
<h3 class='sectionHead'><span class='titlemark'>1</span> <a id='x1-20001'></a>Introduction</h3>
<!-- l. 19 -->
<p class='noindent'><span class='rm-lmri-10'>příliš žluťoučký</span></p>
answered 7 hours ago
michal.h21michal.h21
33.5k4 gold badges49 silver badges115 bronze badges
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "85"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f506578%2fblogging-in-latex%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can utilize the fact that Markdown also supports HTML, so to support LaTeX in static site generators you just need to convert LaTeX to HTML. It is then necessary to extract just the contents of the <body> element and add an YAML header, just like in the Markdown file. make4ht can do this automatically.
In my planned blog, I have the following directory structure:
texposts/
.make4ht
first_post/
hello.tex
second_post
world.tex
build/
www/
There are three top level directories, texposts for LaTeX documents, build where HTML files to be processed are saved and www, which is populated by the static site generator.
The .make4ht file is a special configuration file for make4ht:
local outdir = os.getenv "kodymirus_root" or "out"
local domfilter = require "make4ht-domfilter"
-- remove the maketitle environment from the HTML file, title will be inserted in the template
local domprocess = domfilterfunction(dom)
local maketitles = dom:query_selector(".maketitle")
for _, el in ipairs(maketitles) do
print "removing maketitle"
el:remove_node()
end
return dom
end
filter_settings "staticsite"
site_root = outdir,
map =
[".css$"] = "css/"
,
header =
layout="post",
date = function(parameters)
return os.date("!%Y-%m-%d %T", parameters.time)
end
Make:enable_extension "common_domfilters"
if mode=="draft" then
Make:htlatex
elseif mode=="publish" then
-- Make:htlatex
Make:match("html$", domprocess)
Make:enable_extension "tidy"
Make:enable_extension "staticsite"
Make:htlatex
else
Make:htlatex
Make:htlatex
Make:htlatex
end
It is a Lua script which drives the conversion from LaTeX to HTML. There are few interesting things:
local outdir = os.getenv "kodymirus_root" or "out"
This reads an environmental variable set in my .bashrc that contains path to the build directory.
filter_settings "staticsite"
This contains settings for the staticsite extension:
site_root = outdir,
set the output directory
map =
[".css$"] = "css/"
,
move the generated files that match the regular expression to a specified directory. This example moves CSS files to the css subdirectory in the build dir.
header =
In the header we can set additional fields for the YAML header.
elseif mode=="publish" then
-- Make:htlatex
Make:match("html$", domprocess)
Make:enable_extension "tidy"
Make:enable_extension "staticsite"
Make:htlatex
make4ht supports so called modes. These modes can be selected on the command line using the -m option. By default, this configuration file will create a standalone HTML file. Only when the post is done, you can execute the publish mode, which enables the staticsite extension and publishes the document to the build dir.
To publish the document execute the following command in the texposts/first directory:
make4ht -um publish hello.tex
Here is an example TeX file:
documentclassarticle
titleBlogging with LaTeX
authorMichal
begindocument
maketitle
tableofcontents
sectionIntroduction
textitpříliš žluťoučký
printbibliography
enddocument
And this is the generated document:
---
layout: 'post'
updated: 1524600200
styles:
- '2018-04-18-blogging-with-latex.css'
meta:
- content: 'HTML Tidy for HTML5 for Linux version 5.4.0'
name: 'generator'
- charset: 'utf-8'
- content: 'TeX4ht (http://www.tug.org/tex4ht/)'
name: 'generator'
- content: 'width=device-width,initial-scale=1'
name: 'viewport'
- content: '2018-04-18-blogging-with-latex.tex'
name: 'src'
title: 'Blogging with LaTeX'
date: '2018-04-18 20:31:14'
time: 1524083474
---
<h3 class='likesectionHead'><a id='x1-1000'></a>Contents</h3>
<div class='tableofcontents'><span class='sectionToc'>1 <a id='QQ2-1-2' href='#x1-20001'>Introduction</a></span></div>
<!-- l. 17 -->
<p class='noindent'></p>
<h3 class='sectionHead'><span class='titlemark'>1</span> <a id='x1-20001'></a>Introduction</h3>
<!-- l. 19 -->
<p class='noindent'><span class='rm-lmri-10'>příliš žluťoučký</span></p>
answered 7 hours ago
michal.h21michal.h21
33.5k4 gold badges49 silver badges115 bronze badges
add a comment |
You can utilize the fact that Markdown also supports HTML, so to support LaTeX in static site generators you just need to convert LaTeX to HTML. It is then necessary to extract just the contents of the <body> element and add an YAML header, just like in the Markdown file. make4ht can do this automatically.
In my planned blog, I have the following directory structure:
texposts/
.make4ht
first_post/
hello.tex
second_post
world.tex
build/
www/
There are three top level directories, texposts for LaTeX documents, build where HTML files to be processed are saved and www, which is populated by the static site generator.
The .make4ht file is a special configuration file for make4ht:
local outdir = os.getenv "kodymirus_root" or "out"
local domfilter = require "make4ht-domfilter"
-- remove the maketitle environment from the HTML file, title will be inserted in the template
local domprocess = domfilterfunction(dom)
local maketitles = dom:query_selector(".maketitle")
for _, el in ipairs(maketitles) do
print "removing maketitle"
el:remove_node()
end
return dom
end
filter_settings "staticsite"
site_root = outdir,
map =
[".css$"] = "css/"
,
header =
layout="post",
date = function(parameters)
return os.date("!%Y-%m-%d %T", parameters.time)
end
Make:enable_extension "common_domfilters"
if mode=="draft" then
Make:htlatex
elseif mode=="publish" then
-- Make:htlatex
Make:match("html$", domprocess)
Make:enable_extension "tidy"
Make:enable_extension "staticsite"
Make:htlatex
else
Make:htlatex
Make:htlatex
Make:htlatex
end
It is a Lua script which drives the conversion from LaTeX to HTML. There are few interesting things:
local outdir = os.getenv "kodymirus_root" or "out"
This reads an environmental variable set in my .bashrc that contains path to the build directory.
filter_settings "staticsite"
This contains settings for the staticsite extension:
site_root = outdir,
set the output directory
map =
[".css$"] = "css/"
,
move the generated files that match the regular expression to a specified directory. This example moves CSS files to the css subdirectory in the build dir.
header =
In the header we can set additional fields for the YAML header.
elseif mode=="publish" then
-- Make:htlatex
Make:match("html$", domprocess)
Make:enable_extension "tidy"
Make:enable_extension "staticsite"
Make:htlatex
make4ht supports so called modes. These modes can be selected on the command line using the -m option. By default, this configuration file will create a standalone HTML file. Only when the post is done, you can execute the publish mode, which enables the staticsite extension and publishes the document to the build dir.
To publish the document execute the following command in the texposts/first directory:
make4ht -um publish hello.tex
Here is an example TeX file:
documentclassarticle
titleBlogging with LaTeX
authorMichal
begindocument
maketitle
tableofcontents
sectionIntroduction
textitpříliš žluťoučký
printbibliography
enddocument
And this is the generated document:
---
layout: 'post'
updated: 1524600200
styles:
- '2018-04-18-blogging-with-latex.css'
meta:
- content: 'HTML Tidy for HTML5 for Linux version 5.4.0'
name: 'generator'
- charset: 'utf-8'
- content: 'TeX4ht (http://www.tug.org/tex4ht/)'
name: 'generator'
- content: 'width=device-width,initial-scale=1'
name: 'viewport'
- content: '2018-04-18-blogging-with-latex.tex'
name: 'src'
title: 'Blogging with LaTeX'
date: '2018-04-18 20:31:14'
time: 1524083474
---
<h3 class='likesectionHead'><a id='x1-1000'></a>Contents</h3>
<div class='tableofcontents'><span class='sectionToc'>1 <a id='QQ2-1-2' href='#x1-20001'>Introduction</a></span></div>
<!-- l. 17 -->
<p class='noindent'></p>
<h3 class='sectionHead'><span class='titlemark'>1</span> <a id='x1-20001'></a>Introduction</h3>
<!-- l. 19 -->
<p class='noindent'><span class='rm-lmri-10'>příliš žluťoučký</span></p>
answered 7 hours ago
michal.h21michal.h21
33.5k4 gold badges49 silver badges115 bronze badges
add a comment |
You can utilize the fact that Markdown also supports HTML, so to support LaTeX in static site generators you just need to convert LaTeX to HTML. It is then necessary to extract just the contents of the <body> element and add an YAML header, just like in the Markdown file. make4ht can do this automatically.
In my planned blog, I have the following directory structure:
texposts/
.make4ht
first_post/
hello.tex
second_post
world.tex
build/
www/
There are three top level directories, texposts for LaTeX documents, build where HTML files to be processed are saved and www, which is populated by the static site generator.
The .make4ht file is a special configuration file for make4ht:
local outdir = os.getenv "kodymirus_root" or "out"
local domfilter = require "make4ht-domfilter"
-- remove the maketitle environment from the HTML file, title will be inserted in the template
local domprocess = domfilterfunction(dom)
local maketitles = dom:query_selector(".maketitle")
for _, el in ipairs(maketitles) do
print "removing maketitle"
el:remove_node()
end
return dom
end
filter_settings "staticsite"
site_root = outdir,
map =
[".css$"] = "css/"
,
header =
layout="post",
date = function(parameters)
return os.date("!%Y-%m-%d %T", parameters.time)
end
Make:enable_extension "common_domfilters"
if mode=="draft" then
Make:htlatex
elseif mode=="publish" then
-- Make:htlatex
Make:match("html$", domprocess)
Make:enable_extension "tidy"
Make:enable_extension "staticsite"
Make:htlatex
else
Make:htlatex
Make:htlatex
Make:htlatex
end
It is a Lua script which drives the conversion from LaTeX to HTML. There are few interesting things:
local outdir = os.getenv "kodymirus_root" or "out"
This reads an environmental variable set in my .bashrc that contains path to the build directory.
filter_settings "staticsite"
This contains settings for the staticsite extension:
site_root = outdir,
set the output directory
map =
[".css$"] = "css/"
,
move the generated files that match the regular expression to a specified directory. This example moves CSS files to the css subdirectory in the build dir.
header =
In the header we can set additional fields for the YAML header.
elseif mode=="publish" then
-- Make:htlatex
Make:match("html$", domprocess)
Make:enable_extension "tidy"
Make:enable_extension "staticsite"
Make:htlatex
make4ht supports so called modes. These modes can be selected on the command line using the -m option. By default, this configuration file will create a standalone HTML file. Only when the post is done, you can execute the publish mode, which enables the staticsite extension and publishes the document to the build dir.
To publish the document execute the following command in the texposts/first directory:
make4ht -um publish hello.tex
Here is an example TeX file:
documentclassarticle
titleBlogging with LaTeX
authorMichal
begindocument
maketitle
tableofcontents
sectionIntroduction
textitpříliš žluťoučký
printbibliography
enddocument
And this is the generated document:
---
layout: 'post'
updated: 1524600200
styles:
- '2018-04-18-blogging-with-latex.css'
meta:
- content: 'HTML Tidy for HTML5 for Linux version 5.4.0'
name: 'generator'
- charset: 'utf-8'
- content: 'TeX4ht (http://www.tug.org/tex4ht/)'
name: 'generator'
- content: 'width=device-width,initial-scale=1'
name: 'viewport'
- content: '2018-04-18-blogging-with-latex.tex'
name: 'src'
title: 'Blogging with LaTeX'
date: '2018-04-18 20:31:14'
time: 1524083474
---
<h3 class='likesectionHead'><a id='x1-1000'></a>Contents</h3>
<div class='tableofcontents'><span class='sectionToc'>1 <a id='QQ2-1-2' href='#x1-20001'>Introduction</a></span></div>
<!-- l. 17 -->
<p class='noindent'></p>
<h3 class='sectionHead'><span class='titlemark'>1</span> <a id='x1-20001'></a>Introduction</h3>
<!-- l. 19 -->
<p class='noindent'><span class='rm-lmri-10'>příliš žluťoučký</span></p>
answered 7 hours ago
michal.h21michal.h21
33.5k4 gold badges49 silver badges115 bronze badges
You can utilize the fact that Markdown also supports HTML, so to support LaTeX in static site generators you just need to convert LaTeX to HTML. It is then necessary to extract just the contents of the <body> element and add an YAML header, just like in the Markdown file. make4ht can do this automatically.
In my planned blog, I have the following directory structure:
texposts/
.make4ht
first_post/
hello.tex
second_post
world.tex
build/
www/
There are three top level directories, texposts for LaTeX documents, build where HTML files to be processed are saved and www, which is populated by the static site generator.
The .make4ht file is a special configuration file for make4ht:
local outdir = os.getenv "kodymirus_root" or "out"
local domfilter = require "make4ht-domfilter"
-- remove the maketitle environment from the HTML file, title will be inserted in the template
local domprocess = domfilterfunction(dom)
local maketitles = dom:query_selector(".maketitle")
for _, el in ipairs(maketitles) do
print "removing maketitle"
el:remove_node()
end
return dom
end
filter_settings "staticsite"
site_root = outdir,
map =
[".css$"] = "css/"
,
header =
layout="post",
date = function(parameters)
return os.date("!%Y-%m-%d %T", parameters.time)
end
Make:enable_extension "common_domfilters"
if mode=="draft" then
Make:htlatex
elseif mode=="publish" then
-- Make:htlatex
Make:match("html$", domprocess)
Make:enable_extension "tidy"
Make:enable_extension "staticsite"
Make:htlatex
else
Make:htlatex
Make:htlatex
Make:htlatex
end
It is a Lua script which drives the conversion from LaTeX to HTML. There are few interesting things:
local outdir = os.getenv "kodymirus_root" or "out"
This reads an environmental variable set in my .bashrc that contains path to the build directory.
filter_settings "staticsite"
This contains settings for the staticsite extension:
site_root = outdir,
set the output directory
map =
[".css$"] = "css/"
,
move the generated files that match the regular expression to a specified directory. This example moves CSS files to the css subdirectory in the build dir.
header =
In the header we can set additional fields for the YAML header.
elseif mode=="publish" then
-- Make:htlatex
Make:match("html$", domprocess)
Make:enable_extension "tidy"
Make:enable_extension "staticsite"
Make:htlatex
make4ht supports so called modes. These modes can be selected on the command line using the -m option. By default, this configuration file will create a standalone HTML file. Only when the post is done, you can execute the publish mode, which enables the staticsite extension and publishes the document to the build dir.
To publish the document execute the following command in the texposts/first directory:
make4ht -um publish hello.tex
Here is an example TeX file:
documentclassarticle
titleBlogging with LaTeX
authorMichal
begindocument
maketitle
tableofcontents
sectionIntroduction
textitpříliš žluťoučký
printbibliography
enddocument
And this is the generated document:
---
layout: 'post'
updated: 1524600200
styles:
- '2018-04-18-blogging-with-latex.css'
meta:
- content: 'HTML Tidy for HTML5 for Linux version 5.4.0'
name: 'generator'
- charset: 'utf-8'
- content: 'TeX4ht (http://www.tug.org/tex4ht/)'
name: 'generator'
- content: 'width=device-width,initial-scale=1'
name: 'viewport'
- content: '2018-04-18-blogging-with-latex.tex'
name: 'src'
title: 'Blogging with LaTeX'
date: '2018-04-18 20:31:14'
time: 1524083474
---
<h3 class='likesectionHead'><a id='x1-1000'></a>Contents</h3>
<div class='tableofcontents'><span class='sectionToc'>1 <a id='QQ2-1-2' href='#x1-20001'>Introduction</a></span></div>
<!-- l. 17 -->
<p class='noindent'></p>
<h3 class='sectionHead'><span class='titlemark'>1</span> <a id='x1-20001'></a>Introduction</h3>
<!-- l. 19 -->
<p class='noindent'><span class='rm-lmri-10'>příliš žluťoučký</span></p>
answered 7 hours ago
michal.h21michal.h21
33.5k4 gold badges49 silver badges115 bronze badges
answered 7 hours ago
michal.h21michal.h21
33.5k4 gold badges49 silver badges115 bronze badges
answered 7 hours ago
michal.h21michal.h21
33.5k4 gold badges49 silver badges115 bronze badges
answered 7 hours ago
michal.h21michal.h21
33.5k4 gold badges49 silver badges115 bronze badges
33.5k4 gold badges49 silver badges115 bronze badges
add a comment |
add a comment |
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f506578%2fblogging-in-latex%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
