Anonymous
My feedback
8 results found
-
317 votes65 comments · Adobe InDesign: Feature Requests » Cloud services (Typekit, CC Libraries etc) · Admin →
Thanks for making this request. In order to understand the use-case more better I have a few questions:
1. Whats the role of the different people working collaboratively on the same file. Are they always only designers or are other personas also involved.
2. What is the use-case here, some parts of this request suggest an Editorial collaboration whereas others suggest collaboration amongst different designers. I am trying to separate these 2 requests out.
3. What are the different kind of files (brochures, books, magazines etc) for which this is required.
4. Does it need to be a web based service, or having the user be able to collaborate on one shared file using InDesign or InCopy on the Desktop will work? What is the advantage you feel over a web-service over the desktop app?
5. How do you workaround this need today? What are the most important problems with…An error occurred while saving the comment -
87 votes
An error occurred while saving the comment Anonymous
commented
I'm noticing that if I change my Document Settings and uncheck Facing Pages, it will let me update my review link from spreads to pages. Not ideal since my master doc has alternating treatments for left- and right-hand pages, but the client is happier to be able to print and review than try to squint to make edits with the page numbers on the correct side of the pages.
It's super annoying to ask my clients to work around this tool that I'm suggesting they use with me, but all we can do is just cross our fingers that InDesign gets some real engineering work on this tool that's so frequently brought to our attention. It's not a novel tool, but I'm guessing integrating it with the InDesign platform must be creating a lot of hurdles. When it works correctly, integrating reviews and comments with InDesign has saved me so much time, but unfortunately that's not a consistent nor a common occurence.
Come through, Adobe!
-
64 votes
The fix for this issue is available in the latest InDesign release 16.2.1
Please update to this latest version to get the fix.—
Adobe InDesign teamAn error occurred while saving the comment Anonymous
commented
For one, I wish this forum supported subthreads, because a lot of these comments are going unanswered and I can't respond to them through a subthread or by tagging them.
When trying to understand what was meant by "Build 15", it took me about 10 minutes to discuss this with my partner, who is an engineer, who was also stumped by the terminology. When I read the past three sets of release notes, I realized that when Ravi is saying "Build 15", he means 16.0.2.15, not Version 15 from months ago. He's technically correct in using the term, but "version" vs. "build" is a little ambiguous for us designers.
Of course, when you go to the Prerelease website, you can't click on a link that directs you to the download within Creative Cloud, so that's fun. Here are the steps, but full disclosure, these instructions are just to TRY the fix; the suggested workaround DID NOT WORK for me.
1. Sign up for the InDesign Prerelease program: https://www.adobeprerelease.com/#home_available_programs_top_container.
2. Click "Join" on the InDesign area. There are about four listings associated with InDesign so be sure not to select the Server, SDK, or Developer ones or you'll be lost.
3. Click the permissions link to "read" the licensing agreement and check that you'll follow the guidelines.
4. Sign out of Creative Cloud on your device and close the app. Sign back in.
5. Prerelease" should now appear under "Beta apps" within your Creative Cloud app. However, don't click "Install" unless you have one of the brand-new Macs with the M3 chip. Click the three dots next to the button and you can select "Other Versions". The one he's suggesting is 16.2. Unfortunately, we can't choose between 16.2.0.15 or 16.2.0.20.
——————————————
As I clarified earlier, it did not work for me. I downloaded 16.2, opened my doc, and had the identical issues I had before: no mapping of highlighted or crossed-out text, only pins. It's the same issue on my browser, except the icons there don't even indicate if I'm missing a highlight or crossed-out text.
Even if I could l see them in just my browser for now, it would be annoying, but still usable. Instead of being able to warn my client and several other people on her team that are reviewing this large catalog, I will need to go back and confirm which line/word they were referring to in each instance. There are hundreds of comments and countless highlights throughout.
This just added potentially hours to their review process and likely another day to our turnaround time. The same likely applies to others in this thread.
I'm all for users opting to give feedback on new builds, but we really shouldn't have to go through all this in order to retrieve a feature that was already there. Share for Review is relatively new, but with so few features, keeping the ones we have should be a minimum requirement.
Please, prioritize this fix as soon as your team can.
An error occurred while saving the comment Anonymous
commented
For one, I wish this would forum supported subthreads, because a lot of these comments are going unanswered and I can't respond to them through a subthread or by tagging them.
When trying to understand what was meant by "Build 15", it took me about 10 minutes to discuss this with my partner, who is an engineer, who was also stumped by the terminology. When I read the past three sets of release notes, I realized that when Ravi is saying "Build 15", he means 16.0.2.15, not Version 15 from months ago. He's technically correct in using the term, but "version" vs. "build" is a little ambiguous for us designers.
Of course, when you go to the Prerelease website, you can't click on a link that directs you to the download within Creative Cloud, so that's fun. Here are the steps, but full disclosure, these instructions are just to TRY the fix; the suggested workaround DID NOT WORK for me.
1. Sign up for the InDesign Prerelease program: https://www.adobeprerelease.com/#home_available_programs_top_container.
2. Click "Join" on the InDesign area. There are about four listings associated with InDesign so be sure not to select the Server, SDK, or Developer ones or you'll be lost.
3. Click the permissions link to "read" the licensing agreement and check that you'll follow the guidelines.
4. Sign out of Creative Cloud on your device and close the app. Sign back in.
5. Prerelease" should now appear under "Beta apps" within your Creative Cloud app. However, don't click "Install" unless you have one of the brand-new Macs with the M3 chip. Click the three dots next to the button and you can select "Other Versions". The one he's suggesting is 16.2. Unfortunately, we can't choose between 16.2.0.15 or 16.2.0.20.
——————————————
As I clarified earlier, it did not work for me. I downloaded 16.2, opened my doc, and had the identical issues I had before: no mapping of highlighted or crossed-out text, only pins. It's the same issue on my browser, except the icons there don't even indicate if I'm missing a highlight or crossed-out text.
Even if I could l see them in just my browser for now, it would be annoying, but still usable. Instead of being able to warn my client and several other people on her team that are reviewing this large catalog, I will need to go back and confirm which line/word they were referring to in each instance. There are hundreds of comments and countless highlights throughout.
This just added potentially hours to their review process and likely another day to our turnaround time. The same likely applies to others in this thread.
I'm all for users opting to give feedback on new builds, but we really shouldn't have to go through all this in order to retrieve a feature that was already there. Share for Review is relatively new, but with so few features, keeping the ones we have should be a minimum requirement.
Please, prioritize this fix as soon as your team can.
-
37 votesAnonymous
supported this idea
·
-
8 votesAnonymous
supported this idea
·
-
Share for Review comments link to incorrect spreads on web viewer after reordering pages in InDesign
6 votesAn error occurred while saving the comment Anonymous
commented
Yes, this makes reviewing a nightmare. Even if you delete pages last, it makes it impossible to review resolved changes to ensure all have been corrected. The PDF comments interface is WAY more advanced than this. We're okay losing the comment if we're deleting a page, but the comments need to stay with their respective pages, not serve as just a layer over a now-shuffled layout.
-
7 votesAnonymous
supported this idea
·
-
27 votesAnonymous
supported this idea
·
Where are we at on this? Share for Review is ridiculous for trying to manage a whole team's comments on a large document, no one can neatly see the comments that are just for them, and the markup tools aren't consistent for all users. For instance, my client made edits with the pencil and shape tools, and after an update suddenly I can't see anything, despite any view mode in InDesign, changing browsers, swapping to a PC, swapping to another Mac with an OS one version behind, etc. The client had to completely redo their comments for a 100+ page doc, and I was embarrassed that I had even recommended this tool the app keeps pushing.
Figma has collaborative projects and their app is free! Adobe is not cheap, and this lag in innovation is eating up valuable production time where content editors are having to fiddle with comments and designers are left to translate or enter them in one by one. Even Import PDF comments is flawed because it requires the user to be absolutely perfect with their changes (no trailing spaces, for example). We need something integrated that is easy for clients to use. Most of us are working with people that don't have Adobe experience and we can't dedicate hours to go train them on InCopy, especially since most of us designers have never needed to use that side of the editing process.
The reason a web app is so important is that content edits and responses to content questions need to be accessible on the go. Someone shouldn't have to download an app on their phone or be on their computer to approve a comment or say "hold on this edit for now", for example.