Critic Markup to appear in file outputs
One of the reasons I upgraded to v2 was that it had some Critic Markup support. Though I had hoped for the support would carry into the file outputs (generating PDFs are my main file outputs).
Assuming the "Markup" tab is showing, then I'd have hoped for the PDF output to have strikethrough where {--deletions--} are present, a different colour where {++additions++} are present, highlighting where {==highlights==} are present, and a comment marker that shows the text when moused-over where {>>comments<<} are present.
I understand that there is no universal agreed rendering for critic markup, but this basic form worked well in Word and the like for years. I suspect it's possible to specify all of this in CSS, if I only I knew how the critic markup was being treated under the hood.
Would this be possible? Thanks.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Brett on 20 Oct, 2013 02:34 PM
I'm still working on the output options for CriticMarkup. I'd like to have whatever tab is currently selected determine the output, and yes, if the Markup tab is showing I'd like the export to include all of the niceties. HTML export will include rollovers for comments, etc. I should have this in an update soon.
2 Posted by jonathan on 20 Oct, 2013 02:56 PM
Thanks — that sounds great, Brett. Looking forward to the update.
3 Posted by Till on 27 Feb, 2014 11:57 PM
I'd like to second this.
Would be cool to have :)
4 Posted by adamrice on 25 Apr, 2014 02:59 PM
This is of interest to me too.
My eventual goal is to use mmd files internally and export to a client-friendly format (which is MS Word, for better or worse (it's for worse)) when I send a document off. I do need to be able to include comments in my files. Right now, Marked2 is including the text of the "MARKUP / ORIGINAL / EDITED" controls in the exported Word file, which can't be right. It also omits comment text and highlights.
There's also a difference of approach between Critic Markup comments and Word comments: CM comments are inserted at a point in the file; Word comments are attached to a range of text. It might be possible to export to the Word approach when observing a highlight + comment combination
5 Posted by schrodingerstem... on 20 Nov, 2014 01:55 AM
Any update on this Brett? I'm thinking I need to stop using CM for anything exported as HTML because stripping the CM out before export is pretty tedious.
Support Staff 6 Posted by Brett on 21 Nov, 2014 12:05 AM
Sorry, I let this one slip. I just took an hour and rewrote the whole CriticMarkup handler in all of the export functions, should be much more satisfactory now. Also includes a dropdown that lets you choose which version to output (markup, original, edited) with persistent storage of the preference.
Should be out soon, need to get the rest of these fixes out, too.
7 Posted by schrodingerstem... on 21 Nov, 2014 12:41 AM
Errzome! I like your answer waaaay more than ditching CM!
8 Posted by ddwheel on 28 Sep, 2016 03:31 PM
I've run into an issue regarding this… When exporting CriticMarkup to a PDF, the comment marks appear, but the comment text doesn't seem to exist (opening the PDF in Preview and showing all notes/highlights in the side panel results in an empty panel). Additions, deletions, substitutions, and highlights are all exported, but comments seem to get lost. Any reason for this on my end? I'm running Marked 2.5.6 on macOS 10.12.0.
Support Staff 9 Posted by Brett on 28 Sep, 2016 05:31 PM
Marked PDF output is essentially a Print-to-PDF of the rendered output.
Adding legitimate annotations to that isn't possible. It might be
feasible to have them display inline, but clickable comments aren't
currently feasible.
-Brett
10 Posted by ddwheel on 23 Mar, 2017 03:46 PM
Just had a thought regarding this: IS there a way to toggle comment export in PDF the way you toggle printed URLs for PDF export? That might be the easiest way to work something like that. At the moment, I've created a preprocessor for a pandoc/LaTeX workflow to get this working… but I'd prefer to work through it in Marked (despite my odd demands, I find myself bending over backward to get them to work through Marked because it's such a nice app!).
Support Staff 11 Posted by Brett on 23 Mar, 2017 04:46 PM
I can look into a hack for that, but it would be more difficult than the url replacements.