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

Grey text of the Cheastsheets is hard to read when printed #138

Open
jypeter opened this issue Sep 27, 2023 · 6 comments
Open

Grey text of the Cheastsheets is hard to read when printed #138

jypeter opened this issue Sep 27, 2023 · 6 comments

Comments

@jypeter
Copy link

jypeter commented Sep 27, 2023

Thanks a lot for the nice cheatsheets!

I have followed a link to this GH page to get a pdf version (for printing)

  • The 3 handouts (Beginner, Intermediate and Tips) are perfectly readable
  • Unfortunately, the 2-page Cheatsheets itself is harder to read, not so much because the text is smaller, but because the grey on white parts of the text are not contrasted enough when printed. Would it be possible to use only black text (and possibly use bold characters for the current black text)?
@rougier
Copy link
Member

rougier commented Oct 13, 2023

Thanks. Which part exactly are you referring to?

@jypeter
Copy link
Author

jypeter commented Oct 31, 2023

Maybe an example will help

As an example, I have put 3 jpg below, based on the cheatsheets.pdf and the beginner handout files

  • a jpg taken directly from a screenshot of the pdf open in Acrobat: quite readable!
  • a jpg from a picture of the printed pdf: the picture looks even worse than what the eye can see on the printed version. Note: it's printed on reasonably white paper (that is, not grey looking recycled paper), and a heavy duty professional printer. The actual printed page is white, not the dirty grey of the picture, but the printed grey text is hard to read
  • a jpg from a picture of the printed pdf of the beginner handout: same paper/printer and camera. Characters are bigger, but I think that the style used (black on light grey) is more readable (when printed)

Acrobat

mpl_cheatsheets_from_pdf

Printed

mpl_cheatsheets_from_printer_and_picture

Printed beginner handout

mpl_handout-beginner_from_printer_and_picture

@rougier
Copy link
Member

rougier commented Nov 16, 2023

Thanks, I see your point now. We could have a different set of colors with higher contrast for printed cheets or we could a post-processing on the PDF to enhance contrast. I imagine there are some tools to do that but I don't know them.

@story645
Copy link
Member

We could have a different set of colors with higher contrast for printed cheets

I think a "printed" stylesheet is the better route in terms of accessibility, cause we might also want a high contrast web version too.

@rougier
Copy link
Member

rougier commented Nov 16, 2023

So this means working on the cheatsheet.tex file and removing any harcoded color in favor of variables such that we can have a switch to choose one specific set of color. It's not too difficult to do but I'm a bit busy until mid december. If anyone want to give a try...

@story645
Copy link
Member

story645 commented Nov 17, 2023

. If anyone want to give a try...

I won't have time 'til December either, but if anyone else wants to take a stab, I've been doing this in a paper so I have a style file notation.sty with a whole bunch of definitions:

\definecolor{total}{HTML}{248EA6}
\definecolor{fiber}{HTML}{E30B5C}
\definecolor{base}{HTML}{7924AB}
\definecolor{section}{HTML}{03C04A}

and then use the following to parse my file to build a python dict to keep my colors in sync between latex and python

import re

sub = re.compile(r"\\definecolor\{(?P<name>.*)\}\{HTML\}\{(?P<color>.*)\}")

def build_colors(filepath = '../notation.sty'):
    colordict = {}
    with open(filepath) as f:
        for line in f.readlines():
            if groups := sub.match(line):
                colordict[groups.group('name')] = "#"+ groups.group('color')
    return colordict

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