Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LaTeX support #151

Closed
maxheld83 opened this issue Apr 24, 2014 · 7 comments
Closed

LaTeX support #151

maxheld83 opened this issue Apr 24, 2014 · 7 comments

Comments

@maxheld83
Copy link

As I mentioned in #134 I (and I think a lot of other scholars) have been waiting for something like gitbook to come along for a very long time.
This might just be one of the missing pieces to the puzzle of online scientific publishing.
PDFs, no matter how well structured and meta-data-ed always felt a little awkard online, with people having to download them and all.

Still, academic publishing as over decades (nay, centuries) developed many helpful conventions (theorem numbering, glossaries, acronyms, – you name it) that don't sit easily with markdown.

Fortunately, we have one markup language that has implemented all of these things already: LaTeX.
Of course, much of the typesetting genius (and baggage) of TeX becomes redundant once you publish to a static website.
But still, the conventions have all been implemented, and people know who to write in this markup (not to mention legacy projects).

So here's my (long-winded) question: any chance gitbook might evolve to be a front-end to LaTeX, too? Maybe via Pandoc?

Am I making sense?

@yonkeltron
Copy link

I thought I had been following what you were saying until you mentioned gitbook becoming a front-end for LaTeX. Do you mean the graphical editor?

I would love if we could get LaTeX support in gitbook! Can you even imagine the ability to swap out Markdown files for .tex files!? Total game changer. I wonder if we could somehow tap into luatex and get an intermediate format suitable for feeding through some processor to get less terrible HTML output (not that I don't have a historically-soft spot in my heart for the likes of tth). Does this constitute part of a larger discussion?

In any case, +1 for LaTeX support of some sort in gitbook.

@maxheld83
Copy link
Author

@yonkeltron sorry I wasn't being clear (I'm not a developer and sometimes a bit hazy about terminology); no I didn't mean as a graphical editor (I think the various editors out there are doing a fine job) – I meant as a way to publish a LaTeX source online.

@znmeb
Copy link

znmeb commented Jan 16, 2015

There are already WYSIWYG front-ends for LaTeX, LyX and TeXmacs. I personally use LyX. LyX can export XHTML, which you can probably push into Pandoc to get Markdown, though I haven't tried it.

There is also the RStudio/RMarkdown/knitr/pandoc toolchain for making HTML and PDFs; it can render to Markdown in just about all of the dialects via Pandoc options.

So there are lots of hacks that might work, but I'd try LyX export to XHTML first if you want to publish LaTeX to the web.

@SamyPesse SamyPesse mentioned this issue Jan 22, 2015
35 tasks
@aepstein
Copy link

aepstein commented Apr 9, 2015

Pandoc + HTML is good, but AsciiDoc + docbook seems like a much better route to generate high quality books (richer feature set, orientation towards publication). By using Asciidoc for the gitbook, I was able to compile a nice LaTeX-based PDF this way and the results looked very good for my needs:

#!/bin/bash
perl -p -e 's/\d+\.\s+link:(.+).adoc\[.+\]/$1.adoc/g' SUMMARY.adoc > summary
echo "" > compiled.adoc;
for file in $(cat summary);
do cat "$file" >> compiled.adoc;
printf "\n\n" >> compiled.adoc;
done;
asciidoctor -b docbook compiled.adoc -d book;
dblatex compiled.xml --param toc.section.depth=1 \
  --param insert.xref.page.number=yes \
  --param table.in.float=0;

Any thoughts about that?

@qinix
Copy link

qinix commented Sep 12, 2016

+1 for LaTeX support

@znmeb
Copy link

znmeb commented Sep 13, 2016

The good folks at RStudio now have Bookdown ... you write in R Markdown and get a website in a GitBook-like styling, Bootstrap styling or their own "Tufte HTML" styling. PDFs are done via pandoc and the system LaTeX, although for best results you want to use XeLaTeX.

@urosjarc
Copy link

gitbook-plugin-build


npm release
Travis
Coverage Status
Dependency Status
Codebeat badge
Docs Status
Join the chat

Extends gitbook build system with pandoc converter.

Patreon User
Twitter User


Description

GPP (gitbook-plugin-build) extends gitbook
build system with pandoc converter. Pandoc is your
swiss-army knife when it comes to coverting files. GPP use pandoc
build system to convert and compile your book in variety of formats:

  • TeX formats: LaTeX, ConTeXt, LaTeX Beamer slides
  • HTML formats: XHTML, HTML5, and HTML slide shows using Slidy, reveal.js, Slideous, S5, or DZSlides.
  • Word processor formats: Microsoft Word docx, OpenOffice/LibreOffice ODT, OpenDocument XML
  • Ebooks: EPUB version 2 or 3, FictionBook2
  • Documentation formats: DocBook, TEI Simple, GNU TexInfo, Groff man pages, Haddock markup
  • Page layout formats: InDesign ICML
  • Outline formats: OPML
  • PDF via LaTeX
  • Lightweight markup formats: Markdown (including CommonMark), reStructuredText, AsciiDoc, MediaWiki markup, DokuWiki markup, Emacs Org-Mode, Textile

Writing books with this plugin will be peace of cake. And here cake is not a lie!


Homepage

For more informations please visit projects official homepage.

https://urosjarc.github.io/gitbook-plugin-build


License

Copyright © 2016 Uroš Jarc

MIT License

Nyar233 pushed a commit to Nyar233/gitbook that referenced this issue May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants