prd789
My feedback
35 results found
-
11 votesprd789
supported this idea
·
-
19 votes
To identify the cause of this issue, we had started our investigation with the aim to resolve it. However, we are unable to reproduce the issue inhouse and would need more information
• Are you using any Plug-in or non-supported/non unicode/non-OpenType fonts?
• Video recording of the crash?
Please share the information with us at sharewithID@adobe.com
—
Adobe InDesign Team
prd789
supported this idea
·
-
10 votesprd789
supported this idea
·
-
5 votesprd789
shared this idea
·
-
8 votesprd789
supported this idea
·
-
11 votes
This issue was fixed in one of the recent updates (18.2) of ID2023 release.
--
Adobe InDesign team
prd789
supported this idea
·
An error occurred while saving the comment -
8 votesprd789
supported this idea
·
-
836 votesprd789
supported this idea
·
-
7 votes
An error occurred while saving the comment prd789
commented
We've run across this problem as well in non-ME InDesign. It does seem related to font, but I'm wondering if it's not related to the fact that OTF fonts uses the width of the glyph 00A0 for non breaking space, whereas Type 1 fonts use the width of a regular space. If the font has a differing space for 00A0, then a non breaking space will not work as expected and the font is at fault. However, it seems another layer of interaction happens when World Ready composer is used. As noted in the bug, the non breaking space will behave in Paragraph Composer, but incorrect in World Ready. This should be fixed.
prd789
supported this idea
·
-
420 votesprd789
supported this idea
·
-
18 votesprd789
shared this idea
·
-
43 votes
Thank you for reporting the issue to us.
We are currently reviewing it.
InDesign Teamprd789
supported this idea
·
-
16 votes
The fix for this issue is now available in the latest update of InDesign – that is, InDesign 15.0.2.
Please update your InDesign application to get this fix.
—
Adobe InDesign teamprd789
supported this idea
·
-
2 votesprd789
supported this idea
·
-
10 votes
It is not possible to have unequal inset spacing and corners other than none as they can’t go together.
It is designed this way.—
InDesign teamprd789
supported this idea
·
-
15 votesprd789
shared this idea
·
-
22 votes10 comments · Adobe InDesign: Feature Requests » Cloud services (Typekit, CC Libraries etc) · Admin →
An error occurred while saving the comment prd789
commented
Adobe Fonts is causing issues with workflows that don't rely on Adobe Font versions as well -- it's giving preference to Adobe Font versions and ignoring what is in the Document fonts folder. This is a huge problem. There need to be some way to avoid this as well.
prd789
supported this idea
·
-
131 votesprd789
supported this idea
·
-
230 votes
Thank you all for the votes.
Can you help us understand the key problems that you face in the absence of ability to send an anchored image backwards?
What’s the current workaround that you have to follow?
What are the use cases wherein you need that the text appears specifically on top of inline anchored image?
This information will help us evaluate the functionality better.
prd789
supported this idea
·
-
564 votes
Thank you all for the feedback.
We have added this feature in our backlog. Will share more updates when we pick this up for implementation.
Thanks
Abhinav Agarwalprd789
supported this idea
·
I can repeat this behavior and it also results in odd indenting with the paragraph and the subsequent paragraphs with just a regular left indent on a paragraph with dropcaps.
Both examples had the exact same settings. Flush left drop cap paragraph followed by a paragraph with a first line indent.
I then added a .25" left indent to the dropcap paragraphs:
The first example shows what happens when the setting is checked on: The dropcap paragraph is indented to .5" and the non-dropcap paragraph first line indent is ignored.
The next example shows what happens with the setting is checked off: The dropcap paragraph is indented to the expected .25" and the non-dropcap paragraph first line indent is maintained.
Note that in the file with the screenshot, if I trigger a recompose with Honor Indents off, the top/on example resets to match the bottom/off example.