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

change all smart quotes, worth a thorough review #118

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Conversation

ofZach
Copy link
Contributor

@ofZach ofZach commented Mar 22, 2015

rich diff might help to make this easier to see.

I basically did a find an replace on all smart single quotes. I figure it will help us standardize things and we can use a javascript / other approach to displaying smart quotes.

@ofZach
Copy link
Contributor Author

ofZach commented Mar 22, 2015

if we merge this, will other PRs by @synesthete get clobbered? I'm happy also to do this after his PRs are merged, since this is a pretty easy to do change and I'd rather not mess with all the great copy editing....

@mikewesthad
Copy link
Member

Nice - thanks for adding the curly quote removal. 44f3b46 caught some things that would definitely have broken pandoc.

Yeah it seems like it would be safer to get @synesthete's PRs into the chapters first.

@ofZach
Copy link
Contributor Author

ofZach commented Mar 22, 2015

ok I emailed authors individually to take a look, and I'm happy to run the same steps again (it's pretty simple to do / check) once more of the PRs are merged.

@mikewesthad
Copy link
Member

great - thanks for doing that

@tpltnt
Copy link
Collaborator

tpltnt commented Apr 22, 2015

I merge all of @synesthete PRs, will took a look at this issue now.

@edap
Copy link
Member

edap commented Oct 25, 2018

Hello @tpltnt @bilderbuchi, what's the status on this PR? is it obsolete and can be closed or does it need more work?

@bilderbuchi
Copy link
Member

I honestly have no idea...

@edap
Copy link
Member

edap commented Oct 26, 2018

;) @tpltnt @ofZach @mikewesthad do you think it make sense to close it? It has ~3 years and I doubt we will have time to check the conflict files 1 by 1, probably some of these things went fixed in other PRs. What do you think?

@mikewesthad
Copy link
Member

@edap Seems to me that we could close this PR and someone could open a new one after rerunning the sed / find & replace to get rid off curly quotes?

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

Successfully merging this pull request may close these issues.

None yet

5 participants