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

Already on GitHub? Sign in to your account

Print friendly #56

Closed
vdeparday opened this Issue Mar 21, 2013 · 20 comments

Comments

Projects
None yet
9 participants

The PDFs are currently available as Google docs but these will get outdated as pull requests come in. So, it looks like:

  • A script should be available in the repo to generate the PDFs (using pandoc?)
  • The generated PDFs should have links to them on the website
  • Ideally, the PDFs should be generated after each pull request
Contributor

lxbarth commented Mar 21, 2013

I suggest we only need:

  • print-friendy pages that have all chapters of a guide on one page
  • then use "print to PDF" for generating a PDF

Agreed, simpler is better :) and with a clear link to the print-friendly page the result should be the same for the end-users.

Contributor

jueyang commented Mar 21, 2013

Yeah, it should be easy to add a "view-chapters" link and have all the chapters on one page.

Work in progress here under the all-chapters branch

https://github.com/hotosm/learnosm/tree/all-chapters

Contributor

lxbarth commented Mar 21, 2013

@jueyang - I like this a lot.

  • We should make the link to all chapters look different than a chapter entry - maybe a link under the grey box
  • Images are broken. It seems that markdownify in {{post.content | markdownify}} is not resolving any liquid variables like site.baseurl. I'd be fine with just using absolute paths instead of site.baseurl in image URLs to circumvent this.
  • Print friendly style sheet is needed

jaakkoh commented Oct 23, 2014

This would be great. .. But in the mean time: How should created prints be provided for publishing at LearnOSM.org? @xamanu just created a Spanish PDF of the Spanish Github translation. How should that be offered for publishing? (Detailed) Pull request or a clear language request with a link to the PDF?

Contributor

lxbarth commented Oct 24, 2014

@jaakkoh - why would others not just generate the PDF themselves?

Contributor

lxbarth commented Oct 24, 2014

All that's needed is a print friendly stylesheet. That's the cheapest to maintain in the long run.

jaakkoh commented Oct 24, 2014

Yes. In the long run. But in the long run we'll all be dead too...
Seriously speaking, the current situation, which will apply to foreseeable future (.. until someone actually creates that print friendly stylesheet) is that it is not print friendly.
When Xavier created the French PDF in spring 2013 it took him an evening to get all things tweaked. When @xamanu created Spanish PDF it took him a few hours. .. I don't think that there are many people who will end up doing that.
So, getting the tweaked ready PDFs even if they are not the most up-to-date versions would be good until there actually is a printer friendly stylesheet.

Contributor

maning commented Oct 26, 2014

FYI, here's the conversion script we did using pandoc. https://github.com/essc/learnosmtopdf
See sample output here: https://docs.google.com/file/d/0B-2WZQ1DwK_xN2R4RE1HWDI2Q2M/edit

This is not as easy as just printing from the browsers (too many pandoc dependencies), but we once setup, it is very straightforward to update the docs from learnosm repo (git pull && make).

@jaakkoh I think there is a first print friendly css that was put together (at least for the beginner content) during the initial discussion. If you click on the all chapters link in the left menu (http://learnosm.org/en/editing/id-editor/) and then use Print Pdf in the browser. Does that work for you?

jaakkoh commented Nov 6, 2014

Thanks @vdeparday . Unfortunately it doesn't. That is, I can print but it looks horrible and there's e.g. no TOC of any kind as illustrated below.

image

For an example of how it should look (more or less) like pls see the linked PDF of LearnOSM Spanish version pimped up by @xamanu
https://www.dropbox.com/s/2ubxh1pypwlumxz/learnOSM-es.pdf?dl=0

Contributor

Nick-Tallguy commented Dec 21, 2014

I think we need info from the actual users on this - who wants it, for what, and how often.
I've been experimenting with editing tools for markdown, for instance Uberwriter, which can produce an export in .odf format, but it doesn't include the images. But images can then be added & resulting document formatted to suite the individuals needs. Nevertheless, this takes time, and I have no wish to do this every time we correct or update this, only to find that it is rarely used.
Personally if I wanted a .pdf so I could read on my phone when without signal, I would accept the print to file from my web browser.

As I said, think we need to send a message to HOT establishing who wants it, why, and how often.

jaakkoh commented Dec 22, 2014

Right. I was assuming that creating a proper print style would be be more
than insignificant amount of work and so for that it would be especially
good to understand what (different) need(s) there are regarding this
feature.

The "typical" use case I'm thinking about and what I've seen or/and had is
a plain traditional print to letter or A4 for actually printing on paper.
Of my exposure this has been

  1. a HOT field project need once (Northern Haiti '13, French version to 60
    trainees, 15 trainers, resolved by Xavier making the print version in OO in
    his night shift)
  2. a hum/dev sector OSM + HOT training session (in collaboration with
    Unicef, Atlantic coast of Nicaragua, Spanish version, created by @xamanu in
    OO/LibreOffice)
  3. mapping parties & handing out prints to n00bs.
  4. my own needs

I would assume that if a traditional print would be created it would serve
the needs of other print uses too (offline, what not). Especially if on top
of A4/Letter PDF there would also be a .odf version, which would make it
easier to create eg different versions for different print sizes.

Sent from my mobile device.
On Dec 20, 2014 7:45 PM, "Nick Allen (OSM = Tallguy)" <
notifications@github.com> wrote:

I think we need info from the actual users on this - who wants it, for
what, and how often.

I've been experimenting with editing tools for markdown, for instance
Uberwriter, which can produce an export in .odf format, but it doesn't
include the images. But images can then be added & resulting document
formatted to suite the individuals needs. Nevertheless, this takes time,
and I have no wish to do this every time we correct or update this, only to
find that it is rarely used.

Personally if I wanted a .pdf so I could read on my phone when without
signal, I would accept the print to file from my web browser.

As I said, think we need to send a message to HOT establishing who wants
it, why, and how often.


Reply to this email directly or view it on GitHub
#56 (comment).

Contributor

Nick-Tallguy commented Dec 23, 2014

I've created a quick .odt document as a test - in my shared dropbox just to see if this would be okay. https://www.dropbox.com/s/fq3grmolw352zws/Introduction.odt?dl=0

It took me about 1/2 an hour to produce (have to individually add the images). Could be quicker with practice. This may be the better option if it is acceptable to all - gives you the opportunity to combine chapters and create TOC as needed. Can then be printed as wanted.

Contributor

Nick-Tallguy commented Feb 6, 2015

See #319 - the .odt documents was created using pandoc, although I did reformat the .odt to incorporate other sections and tidy up, including a TOC, before producing the .pdf

Feedback welcome please

The comment & download link is at the head of http://learnosm.org/en/coordination/remote/

@althio althio referenced this issue in hotosm/hotosm-project-ideas Feb 12, 2015

Open

Develop Jekyll Plugins to Improve LearnOSM.org #11

Contributor

Nick-Tallguy commented Jul 6, 2015

Following on from a move of various topics within the headings, I've produced an .odt & .pdf version of each of the topics now within the beginners guide, in all of the languages, and created links for downloading them. The .odt was produced using pandoc, and only briefly edited (remove some surplus headings for other chapters) before producing the .pdf
My thought is, provide each individually, and the 'trainer' or whoever has the need can amalgamate the .odt document using whichever sections they feel are relevant, and format it as they wish. Adding a TOC and re-sizing the images to suit their needs as they go.

It's not perfect, but I think it is deliverable by me at the moment.

I'll work on the other sections as the need arises - if you need one, let me know & I'll produce it.

Nick-Tallguy added a commit that referenced this issue Jul 23, 2015

Merge pull request #56 from Anwaario/patch-20
Interim Guide for Glossary - UK
Contributor

d3netxer commented Feb 7, 2016

is there anyway to have the LearnOSM logo appear in the print view? I briefly took a look at this but couldn't figure out how to do this yet. I see the print.css file

Contributor

Nick-Tallguy commented Feb 7, 2016

Hi @d3netxer I've started putting the logo manually into the .odt when I produce or update a document. As you've rightly realised there are a lot that don't have the logo in them. If you fancied adding a few & updating them, that would be great, otherwise they wait for me to get the time to do them.

Contributor

d3netxer commented Feb 8, 2016

I haven't looked at your .odt workflow, but in this thread I'm referring to when someone clicks print in their browser, not the PDFs that are linked to on individual pages.

Contributor

Nick-Tallguy commented Jun 17, 2017

Closing. It would be good if some clever person could automate this. In the meantime I'm using pandoc and manually tidying the result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment