Open sssoz opened 4 years ago
I think this is likely best solved by using the chrome view to make a downloadable version, and then providing that. What do you think @sssoz? Lazy... but it'll work.
@JosephMcArthur Do you mean we manually generate each post and upload it as the corresponding PDF for each post? Seems like more work.
Yeah, I guess it is but it seemed like doing this was a pain for you so I didn't want you to have to worry given the limited time (and, likely, pay off given the % of people using them).
Joseph McArthur Assistant Director: Right to Research Coalition ( http://righttoresearch.org ) Director / Founder: Open Access Button ( http://openaccessbutton.org ) Twitter: @Mcarthur_Joe ( https://twitter.com/Mcarthur_Joe ) Skype: joseph_mcarthur
On Fri, Aug 21, 2020 at 11:36 PM, Sophy < notifications@github.com > wrote:
@ JosephMcArthur ( https://github.com/JosephMcArthur ) Do you mean we manually generate each post and upload it as the corresponding PDF for each post? Seems like more work.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub ( https://github.com/sparcopen/infrastructure/issues/76#issuecomment-678543816 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/ABFZMZ6O4G35YR7BZCNIDLTSB3ZHVANCNFSM4OBTI4SA ).
A random thought. If we're unhappy with how these get printed and think it'll be a pain, it may be best just to hid the buttons on safari / firefox so that folks get a good UX... even if it's not a complete one.
[ ] Print on MacOS Safari:
<header>
has its own cover page; the rest of the text is in a narrow column which doesn’t look too awful[ ] Print on MacO Firefox: a lot of white space around
<header>
; blank pageMacOS-Chrome.pdf
MacOS-Safari.pdf
MacOS-Firefox.pdf