Latest trpl, trpl 2nd edition and rustonomicon sources. Dockerized all the things.

[abcdev]

In order to work with latest rustonomicon sources and trpl 2nd edition, I altered some things in the project. Some changes are cosmetic others are necessary (like working with a newer pandoc version).

Dockerized the application for easy access and execution.

[killercup]

Wow, just looking at the commits this looks very impressive. You seem to have spend a lot of time on this! Can you publish the PDF files that this produces?

(I currently don't have time to maintain this further. If what this produces is any good, I'd gladly nominate you the new maintainer of the project.)

[ohbadiah]

I ran into an error building the pdf for trpl2, but otherwise this worked great for me, and I'm now happily reading the second edition on my ereader. Let me know if it would be helpful for me to send the build artifacts in some way.

(Also - shouldn't these files be supplied by the project itself? I guess they don't want to stop on the toes of the publisher.)

[abcdev]

Thanks for the offer @killercup . But I'd like not to keep this in my hands as my rust skills are somewhat rusty. And I hope the official mdBook solution gets a proper EPUB option. I've send you the PDF files you asked for. As @ohbadiah mentioned the creation of the PDFs for the trpl second edition fails. It looks like there is a parsing error in "ch14-04-installing-binaries.md". I was not able to find the actual problem resulting in that error.

[dimonomid]

@abcdev , thanks a lot for that! Would it be possible to post those PDF files somewhere so that other people also can get them before issues get resolved? I'd love to see those PDFs!

[dimonomid]

Here are the errors I'm getting with generating PDFs:

Error producing PDF.                                                                     
! Undefined control sequence.                                                                                                                                  
l.1007 ...et/debug/hello\_cargo} (or *target\debug                                       
                                                                                          
[✓] A4.PDF   

I checked and apparently that comes from the file ch01-03-hello-cargo.md, there are a few lines with backslashes, like this:

This command creates an executable file in *target/debug/hello_cargo* (or
*target\debug\hello_cargo.exe* on Windows) rather than in your current
directory. You can run the executable with this command:

and apparently it isn't handled correctly when generating tex file:

This command creates an executable file in
\emph{target/debug/hello\_cargo} (or *target\debug\hello\_cargo.exe* on
Windows) rather than in your current directory. You can run the
executable with this command:

I'm not sure what's the real issue, but I just worked it around for me by replacing those backslashes with / in sources, and PDF was generated successfully! There was a bunch of warnings like this

[WARNING] Missing character: There is no ב in font [lmroman10-regular]:mapping=tex-text!                                                                       
[WARNING] Missing character: There is no ר in font [lmroman10-regular]:mapping=tex-text!                                                                       
[WARNING] Missing character: There is no י in font [lmroman10-regular]:mapping=tex-text!                                                                       
[WARNING] Missing character: There is no ת in font [lmroman10-regular]:mapping=tex-text!

But still, the PDF looks quite readable. Thanks again!

[dimonomid]

For the future readers who just want to get some PDFs, let me attach those:

trpl2-2018-06-02.a4.pdf
trpl2-2018-06-02.letter.pdf
trpl2-2018-06-02.epub.zip (zipped because Github refused to attach it otherwise by saying that it doesn't support that filetype)

[makramkd]

Hey guys, I know this PR is quite old, but wondering if it would be simpler to simply fetch the latest rustbook + nomicon from the website instead of storing it in the repo. It will be part of the running process, i.e cargo run ... will call out to rust-lang.org or whichever is appropriate (some branch of rustbook/nomicon on github release that is latest stable).

That way it will always be up to date. What do you guys think?

[h5rdly]

Would be great to have it on the website, I found this by prodding through github issues, it's a shame..