Matt Mayerchak
My feedback
4 results found
-
50 votes
Hello All,
Thank you for reporting the issue to us.
We have fixed the issue in the latest version of InDesign, Id 15.0Please upgrade your InDesign application to the latest version to try out the fix.
If you face any problems with the new update, do let us know in the comments.
You may also follow the below given link for the list of all fixed issues in Id 15.0
https://helpx.adobe.com/indesign/kb/fixed-issues.html-InDesign Team
An error occurred while saving the comment An error occurred while saving the comment Matt Mayerchak
commented
When was it fixed? Has it been updated after CC2019 came out? At the moment, the static endnotes feature cannot be used because it strips the superscript formatting, making it impossible to find the endnote refs and apply a character style to them. I don't see a new InDesign update available.
Matt Mayerchak
supported this idea
·
An error occurred while saving the comment Matt Mayerchak
commented
I agree we need to be able to import Endnotes as static, at least until Adobe fixes the way they currently do not work. This is way worse than the way it was before they "improved" it. It is extremely rare that we would keep the endnotes threaded to the text frame. It just is not versatile enough as is. These features seem to be designed by people who have no understanding of how people actually work on documents in the real world.
-
110 votes
Dear All,
This feature is now available in latest InDesign CC version. Please upgrade to the latest release.
Thanks
Abhinav AgarwalAn error occurred while saving the comment Matt Mayerchak
commented
NOTES from first trial:
1) Why does the PDF have to be created from InDesign CC2019? I can't understand the technical reason for this and it's a HUGE drawback.
2) I did several markups over 3 pages of a 50+ page PDF. The ones that imported worked well - a few striketrhoughs and a few text replacments.
3) Several of the edits did not work - it said they could not be mapped. Why not? No rhyme or reason to which ones failed. If they are basic text edits done with the commenting tools, they had better ALL work or it's worthless. Editors will not accept 75% of edits being OK and the other 25% being lost. Adobe really needs to figure out why some don't work.
4) Annotations plugin from DTP tools adds a highlight to show where an edit has been made. (Jan put this in at my suggestion). It's extremely helpful because I can accept all edits for a whole page at a time, then go check them. Often the editor includes an extra word space, or removes a word space, or misses one charactrer or punctuation mark when striking out text.
5) I would STRONGLY encourage the Adobe team to use the Annotations plugin and see how it works, and emulate as much as they can about it (except the import annotations dialog, which is substandard and wonky). But, here are some features they should copy:
a) having indicators in the InDesign showing all the annotations locations BEFORE you accept them (because sometimes they come in wrong, which usually means you edited the InDesign file since the PDF was made);
b) highlighting the edits after they have been made until you choose to remove those;
c) the small comment dialog that shows the text of a comment, whether it's a text edit or a design comment - with these, at least we can still copy the text from a comment even when it was done as a sticky note, rather than having to copy it from Acrobat.
d) the ability to choose which page to start on - because you know some people omit pages from PDFs, or send partial pdfs to editors
e) the ability to work on a PDF saved as spreads. I know this is not how it should be done; but many designers give spread pdfs to clients because the clients are not smart enough to view the pdf as spreads in Acrobat, or print them out as spreads, so they are dummy-proofing their output. I tell designers that if they do this, make sure to give them a single-pages pdf for editing, but you cannot control the editors and they will edit the spreads pdf if it exists. With Annotations, this is not technically supposed to work, but it does!
I fully expect that, as they did with Endnotes, Adobe will include a half-baked version of this in the next release and it will make the whole process horrible for all who use it. Right now we have enough trouble getting people to understand the difference between using comments to annotate a PDF and editing the PDF directly. I have seen several projects where an editor spent many hours directly editing a PDF and then sent that to us to import. A complete waste of time but they simply do what seems obvious to them before asking anybody and Adobe makes it "intuitive" so there is no reason to think this is not a good idea. It would be nice if Adobe spent 5 minutes thinking about human nature and how people in the real world use their products before adding or removing tools, but as we have seen in many instances, such as the addition of the [+] overrides toggle that automatically adds blue highlighting and has freaked out many a designer, they spent very little time trying to understand their users. So, I have ZERO confidence that this feature will be worth using until at least 4 updates, if ever.
p.s. still waiting for live endnotes that work; until then I have to keep CC2017 running so I can import Word files that have footnotes and then bring them into CC2018. I know there is a script for that but it's easier to just import them correctly.
An error occurred while saving the comment Matt Mayerchak
commented
I use Annotations plugin from DTP Tools for this ALL THE TIME with many editors and it works well! If Adobe could build something like this into InDesign, so much the better.
I have never understood why people say you should work back to front using Annotations. Once you import the annotations into the document, they move with the text so it's not a problem at all to work from the front. You just don't want to edit the InDesign file before importing the comments. And, turning off preflight improves the success rate for importing comments.
-
5 votesMatt Mayerchak
shared this idea
·
-
60 votesMatt Mayerchak
shared this idea
·
I just tested importing static endnotes in CC2020 on a Word file that did not work in CC2019. i.e. when I imported in CC2019, the endnote refs lost their superscripts if I used local overrides only for the import setting. I am happy to report that in CC2020, the endnote refs now do come in as superscripted, so that I can find them and apply the character style to preserve them.
To do this in CC2019, I have to import using Style Mapping, and map the Endnote Refs style from word to my endnote refs char style in InDesign. While this works, I don't like using style mapping unless I'm working with an editor who deliberately uses styles in a way that we have worked out in advance. Too much junk comes in otherwise.