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

Ebook version? #66

Open
satwikkansal opened this issue Jan 30, 2018 · 7 comments
Open

Ebook version? #66

satwikkansal opened this issue Jan 30, 2018 · 7 comments
Milestone

Comments

@satwikkansal
Copy link
Owner

Hey guys,

I was preparing a pdf for the collection, while a friend of mine recommended me to put in some extra effort to release an ebook version for the same.

I have absolutely no experience with this and I doubt if it'd be an overkill. That's why I've opened up this issue, maybe someone having prior experience with all this can help me in figuring out what to do and if it actually makes sense to do so 😅

@dirksteindorf
Copy link

Hi satwikkansal,

I would try converting your README.md with pandoc at first, just to see if the results are okay:
https://pandoc.org/getting-started.html
https://pandoc.org/demos.html
https://pandoc.org/epub.html

Pandoc support a huge list of formats, including pdf and epub, so that could help you a lot.
Maybe you just need to do some formatting and then be done with it, if you're lucky.

Code can be quite tricky in ebooks, because of the different display sizes of the readers. Maybe you could just stick to one size or one ebook reader at first. Amazons Kindle Textbook Creator could be helpful for this: https://www.amazon.com/gp/feature.html?docId=1002998671

I hope that helps a bit. :)

@satwikkansal
Copy link
Owner Author

Hey @dirksteindorf

Thanks for the suggestion. Let's give these tools a try! If it works well, we can share the pdf this way for the time being.

@satwikkansal
Copy link
Owner Author

satwikkansal commented Feb 1, 2018

I had another general query as well. I feel that books are supposed to be more formal, organized: following a proper format, and descriptive than wtfpython is right now (maybe I'm wrong believing that).

So if someone can help me figure out if this project is actually worth a book, and up to how much extent (according to them) should we work in formalizing the structure and content, then it'd make things easier to plan.

@dufferzafar
Copy link

dufferzafar commented Aug 11, 2018

I created this using Pandoc. Had to modify the Readme a bit to please Pandoc/LaTeX etc.

The output looks pretty decent to me. It has working table of contents and is only ~400 KB in size.

Download WTF Python.pdf

Command: pandoc -f gfm --pdf-engine=xelatex --template=jgm.tex -V geometry:margin=1.1in README.md -o WTF.pdf

@satwikkansal
Copy link
Owner Author

Hi @dufferzafar

Thank you so much for this, and yes, it looks pretty neat.

There's one minor issue, the hyperlinks in TOC aren't still working in some cases. Trying to figure our the reason why...

@satwikkansal
Copy link
Owner Author

Ah, got it. All the titles ending with non alphanuerice characters (like * and !) aren't properly functioning in TOC hyperlinks.

@satwikkansal
Copy link
Owner Author

I think for now, I can remove those characters at the end and generate the pdf. And I'll create an upstream issue for it, so that we can have a better approach later on.

@satwikkansal satwikkansal added this to the 3.0 milestone May 1, 2019
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

3 participants