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

Compilation to PDF and epub #112

Closed
jnavila opened this issue Feb 20, 2018 · 11 comments
Closed

Compilation to PDF and epub #112

jnavila opened this issue Feb 20, 2018 · 11 comments

Comments

@jnavila
Copy link
Member

jnavila commented Feb 20, 2018

Hi all,

I'm in the process of making an automatic publication of the book on git-scm.com, using asciidoctor and Travis-CI for generating the PDF and epub. That should solve #56 .

This rework requires to move files around, change how cross-refs are done and change build script. This is quite disruptive and would cause conflicts with ongoing changes.

Please ping me when the repo is idle, so that I can make the transition before you guys restart your work.

Thanks,

@jnavila
Copy link
Member Author

jnavila commented Mar 16, 2018

Ping @andres-mancera

@andres-mancera
Copy link
Member

@jnavila : Quick Question: Has this new flow for the automatic publication of the book been enabled for any language or even the original English version?

@jnavila
Copy link
Member Author

jnavila commented Mar 21, 2018

Yes, it has. You can see the result on https://git-scm.com/book . For all the translations with this workflow, there are the availability to download the books in pdf, epub and mobi files.
image

@andres-mancera
Copy link
Member

Ok, I don't have any pending pull request right now, so please go ahead and make the required changes. Let me know if you need anything from me. Thanks @jnavila 👍

@jnavila
Copy link
Member Author

jnavila commented Mar 22, 2018

Just a heads up to indicate that the book is not compiling right now. This is mostly due to remains of conflicts marks that weren't removed.

@andres-mancera
Copy link
Member

Is there some kind of log that I can take a look at so that we can fix the issues(s)?
Otherwise, we'll be trying to find a needle in a haystack!

@jnavila
Copy link
Member Author

jnavila commented Mar 22, 2018

Don't worry, I'm on it. The ugly thing about it is that the errors of compilation don't point to the place where the mistake was made, but where the parser can no longer cope with the errors. The branch should be ready before this week end.

@andres-mancera
Copy link
Member

Great, thanks a lot for your help @jnavila 😃

@jnavila jnavila closed this as completed Mar 28, 2018
@andres-mancera
Copy link
Member

@jnavila : After your changes, I see that the "contributors.asc" file now has a link to a file called "contributors.txt". However, I don't see that file anywhere. Where did the list of contributors go?

@jnavila
Copy link
Member Author

jnavila commented Aug 18, 2018

The file contributors.txt is now dynamically created by the Rakefile

progit2-es/Rakefile

Lines 46 to 47 in b665495

puts "Generating contributors list"
exec_or_raise("git shortlog -s --all| grep -v -E '(Straub|Chacon)' | cut -f 2- | column -c 120 > book/contributors.txt")

It is always up to date with the correct list of contributors. You can run the command line in order to generate it for yourself, without requiring the full ruby environment.

@andres-mancera
Copy link
Member

I see. Thanks @jnavila 👍

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

2 participants