My personal cure for that kind of thing is a very long, carefully groomed input file for the FindChangeByList script.  In Latin script it's comparatively easy to do this, as the decomposition of each ligature glyph should be unambiguous.  I haven't needed to change my input file since 2010, it seems.   Probably this substitution is something that the native PDF-to-INDD tool should be able to do, though.  ... View more

I think I see it now. There are a few problems with your Hebrew in Word, and one of them is leading to a really typical InDesign RTL problem.    Your bilingual test in Word is using a few glyphs inconsistently. I started trying to rekey a problem phrase, so I could post it here, and saw that your input text is using Latin-script punctuation where it should be using Hebrew characters. Looks like the writer working in Word could type geresh sometimes?      So, when a given Hebrew glyph (like an aleph) is marked with Hebrew language and "default" direction in InDesign, it will behave in a right-to-left fashion. Similarly, a given Latin-script glyph (say, an H) marked with English language and "default" direction will behave in a left-to-right fashion. However, there are plenty of glyphs which can behave bidirectionally - not just parentheses or typographer's quotes, but periods, or even space characters. So if they're marked with "default" direction, then they might need to reverse directionality according to what characters are around them.    So, if I were in your shoes, the first thing I'd do is ensure that all the glyphs that were supposed to be Hebrew glyphs actually were Hebrew. Then I'd look at ensuring that the spaces in between Hebrew words were marked as Hebrew, and were therefore default right-to-left spaces. Then I might use the keyboard to select the space right after the colon in "mankind: " or the period and the space after the period, and mark them as overt right-to-left or overt left-to-right characters. Alternately, I might scatter some directionality markers around the period and colon to force correct text direction.    But you'll be constantly fighting with text direction if one of the characters in your input text is sometimes a geresh with default RTL behavior, and sometimes a single quote mark that can have bidirectional behavior.    If you'd like more guidance on how to fix this kind of issue, I'd suggest that you actually post your Word file with that one snippet of text, and we can pull it apart forensically and figure out exactly what kinds of remediations are necessary to make it behave properly in InDesign.  ... View more

left to right text direction and even have paragraph styles for english and then charachter styles for hebrew   How about this? Set all text direction in all paragraph and character styles to "Default" and specify the language English on your paragraph style and Hebrew in your character style. Specifying left to right direction for the whole document will result in backwards Hebrew.   ... View more

Since my INDD file is so large, I saved it as IDML to clean it up. When I resaved the IDML as INDD, the condition had been applied to several pages following a word or sentence that was conditional. It did do it everywhere, just a few places.     While Bob is correct in the narrow sense - you don't techincally need to run through IDML in order to reduce file size - InDesign is not Functioning As Designed, I think, if it's changing how your conditions are applied when being run through IDML.    Can you share the document? Or can you create a stand-in document that recreates this issue? If it's a bug that can be recreated in a second document, then it's something that the InDesign development team is going to want to know about. If it's something unique about your 400-page document, which we cannot recreate in a separate document, then we might be able to figure out what went wrong with your document, but I doubt that it'd be worth a bug report.      ... View more

It has to be an Adobe issue   It might be, but it doesn't have to be.  Did you recently apply an update to InDesign? If not, then it's comparatively unlikely that it's an InDesign issue. If so, you should be able to roll back to your previous install and make the issue go away. That might prove that it was an Adobe issue, though.   However, there are some other places to look. If you look at Rob Day's post, you'll see that you can click through the InDesign printer dialog into the OS printer dialog. He's posting screenshots of what's going on in macOS, but my view from Windows looks quite similar.  Your preferences here can be reset without your input- Rob specifically points out that those settings could be reset by a print driver update. Have you applied an Epson update recently? But I'm guessing that you're on a Windows machine, like me, and those printer settings could have been reset by a Windows OS update. (Yesterday was Patch Tuesday, right?)   In either case, it's worth taking a look to see if those settings look familiar to you, or if they've been reset to defaults.  ... View more

There are actually a few threads here  reporting this issue, and similar issues with right to left languages, broadly speaking. You might try turning on the Legacy Character Shaping Engine in the Preferences - or turning it off, if it is already on. Another workaround that might get you something that you can export would be to make sure that the last character in every paragraph, and every story, is not an Arabic character. If you don't already know how, I can give you a find/change query that will append a space at the end of every paragraph. If that PDF exports correctly, then you have experienced the same bug that is reported here.     ... View more

Use File -> Package. Look at all of the options; packaging can induce InDesign to collect all the linked image files and include them in a Links folder, and to collect all the fonts you've used and include them in a Document Fonts folder.  The resultant folder, including INDD and (if you choose) PDF and IDML, should contain everything you'd need for your document to be portable.    If your collaborators are using an older version of InDesign, they can open the IDML, but note that there might be text reflow when it is opened up in an older version.  So if you can't guarantee that your collaborators are using the exact same version of InDesign as you are, then it's best to include a PDF as well, so they have a reference copy to check against. ... View more

That is most likely a paragraph rule. You can find it (and turn it off) in the Paragraph Rules section of the Paragraph Style. They're not selectable as graphical objects - like an underline, they're textual features. ... View more

Is this a problem with InDesign or could it be something in the way he made the changes to the pdf?   You said that you tried the exact same procedure with the exact same PDF on a different computer? And you had the same result there, correct? Abhishek suggested testing the same procedure with a different PDF; if this issue occurs with this PDF on another computer, but another PDF doesn't display this issue, then it's more likely that it's an issue with the PDF.    Can you share the potential-problem PDF here?  ... View more

So it may be something in the structure of a document created in the arabic version that persists even though you've uninstallled and reinstalled ID in English...   These settings are saved with the INDD. If you started a new INDD document in a MENA edition of InDesign, then you started with the tools defaulting to Middle-East-friendly settings. Imagine that you started a new Arabic document, and you drew a new text frame. That text frame had default Arabic language applied to the text, default RTL story direction in the Story panel, et cetera. Then you saved your INDD and closed it.    When you now open up your old INDD in your new English InDesign, the old settings for your text frame are still there - it's stil RTL story direction and Arabic language. However, your Text tool is also still defaulting to these settings, as the Text tool prefs were saved with your INDD. So if you open up that old INDD and immediately select your Text tool to make some new frames in your old INDD, they'll still have right-to-left story settings  and Arabic language applied.     [...] it was importing the MS word file into to a text frame with an object style of 'none' but which, by default, had a 'story option override' of 'story writing direction' / 'right to left'. This is in the 'English (international)' version which I thought shouldn't be possible.   The main differences between your new English install and your old Midde East/North Africa install are in the user interface and localization. Under the hood, it's basically the same app.  ... View more

Well, there's a few ways to go about it. First off, make sure that you have made a character style that applies a Hebrew font and Hebrew language: Then make a paragraph style for English, one that has a GREP Style that applies your Hebrew character style: The bit in the "To Text:" field is \p{Lo} which means "any letter that is not in Latin script." If you have any other scripts in your document (Arabic, Greek, Cyrillic, literally anything) then they will also be captured by \p{Lo}.   If you might have other writing systems, or if you need to tweak exactly which glyphs are caught and which ones aren't, we could build a more finicky GREP query that should only capture Hebrew-specific glyphs (also a few glyphs only used to write Yiddish😞 [\x{0590}-\x{05FF}|\x{FB1D}-\x{FB4F}]+     ... View more

Just a guess, here, but: is your screenshot showing .png or .jpg placed in InDesign, that could be recreated as a vector object? ... View more

My understanding was that you have access to older installs of Creative Cloud apps with an Enterprise license, but I have honestly never seen it in action. Take a look at https://helpx.adobe.com/enterprise/using/create-nul-packages.html and scroll down to "Older Versions" in step 6. That seems to match up with this statement regarding three (?!?!!) past versions for Enterprise users, instead of the n-1 versions that everyone else sees in our Creative Cloud desktop apps:   Adobe's documentation that I find with a web search isn't always current, or correct, so don't take the above as gospel. But if I'm in any way accurate here, trying to ask Adobe Customer Service to let you have access might be less successful than rolling your own installer pacakges (and keeping them safe forever).   However, I see you're thinking long-term, which is good if you are trying to build something infrastructural on InDesign Server. Adobe's current policy seems to be to remove older versions of applications, so building a product on a server app that you can never download again seems like a dicey proposition. Your server-app foundation will always be a moving target. So it is critical that you do what you are allowed to do, and always download installer packages, and save them forever.    Install process is automated, we can't control to keep 2023.   I think that there are preferences in the Admin Console (I am certain that there are in the desktop CC app) that control whether old versions are removed.  ... View more

Okay, Vinoth, that isn't in InDesign. We're supposed to be talking about Adobe InDesign, in here.  But:   I couldn't have told you that it was corrupted Tamil specifically just by looking at it, but it's clearly some kind of Unicode-encoded text that is being displayed as Latin-1. You posted it without commentary in this thread, which I'm going to take as permission to assume it's Tamil.  It looks like UTF-8 text looks when the encoding fails. (Also, when I gave up and asked Claude.ai if it could extract any meaningful text, it correctly identified it as Tamil without being given any hints.)   That Latin-1 mess then must have passed through some other encoding that didn't support one of the incorrectly rendered glyphs, causing one of those extended Latin glyphs to fail to be rendered.     Because of these dropped glyphs, there's no real way to rescue this text.  I'm not sure how VNI742926 sent this to you, but maybe you could call 'em up and ask them to resend through some other app, once which hopefully had robust Unicode support.  ... View more

This script applies a paragraph style called "Body Text" and then immediately clears all paragraph overrides. You can edit the style name on line 66, to customize this script for your preferred paragraph style. This script also clears paragraph-level formatting only; if you want it to clear character-level formatting as well, you can uncomment line 49.    // Apply Paragraph Style and Clear Overrides #target indesign function applyStyleAndClearOverrides(styleName) { // Check if InDesign is running and a document is open if (app.documents.length === 0) { alert("Please open a document first."); return; } var doc = app.activeDocument; // Check if there's a text selection if (app.selection.length === 0) { alert("Please select some text first."); return; } // Find the paragraph style var paragraphStyle = null; try { paragraphStyle = doc.paragraphStyles.itemByName(styleName); if (!paragraphStyle.isValid) { alert("Paragraph style '" + styleName + "' not found in this document."); return; } } catch (e) { alert("Error finding paragraph style: " + e.message); return; } // Apply the style to selected text try { for (var i = 0; i < app.selection.length; i++) { var selection = app.selection[i]; // Check if this selection item has text content if (selection.hasOwnProperty("parentStory")) { // Apply paragraph style selection.appliedParagraphStyle = paragraphStyle; // Clear paragraph overrides selection.clearOverrides(OverrideType.PARAGRAPH_ONLY); // Optionally clear character overrides as well // Uncomment the next line if you want to clear character overrides too // selection.clearOverrides(OverrideType.CHARACTER_ONLY); } } // Success message alert("Paragraph style '" + styleName + "' applied and overrides cleared successfully!"); } catch (e) { alert("Error applying style: " + e.message); } } // Main execution function main() { // Specify the paragraph style name here var styleName = "Body Text"; // Change this to your desired paragraph style name applyStyleAndClearOverrides(styleName); } // Run the script main();       ... View more

I can't endorse Derek's post hard enough. I suspect what you're trying to do is to configure InDesign so that you have to engage in less repetitious clicking, right? You have a default font choice for all your work, and you don't want InDesign to keep on suggesting Minon, because it's not your preferred default font you're going to be using for the majority of your projects.    The best way to avoid doing that repetitious work is not to try to configure InDesign's base font settings to your preferences. Instead, it's faster & safer to build on top of InDesign.  For example, if you foresee a frequent need to replace someone else's fonts with your own default font, a script like Peter Kahrel's font substitution script is a more reliable solution that is less likely to cause major challenges when working with someone else's files. If you'd like to read some descriptions from other seasoned InDesign users regarding why it's dangerous to modify the Basic Paragraph style, that won't be hard at all to find.   (Changing your default font in the Character panel with no documents open is an excellent way to customize your installation, and isn't relevant to problems caused by altering the default Basic Paragraph style, or to InDesign's hidden font defaults.) ... View more

I honestly haven't been reporting bugs related to paragraph shading. I can't stand the feature, it just breaks things all the time. I would use Paragraph Shading constantly if it didn't keep on dropping out when exported to interactive PDF. Or causing Lao tone marks to sit incorrectly. Or now, apparently, interfering with underlines?   @winfieldgirl the underline works just fine if you remove the paragraph shading. Clearly a bug with Paragraph Shading. I wasn't able to resolve the issue as per Bob's suggestion - applying the hyperlink with Nested Styles did nothing on my end. But maybe he knows something we don't?   Turns out there is already a bug report filed on this one! https://indesign.uservoice.com/forums/601021-adobe-indesign-feature-requests/suggestions/38814361-shading-and-underline-conflict.  I encourage you to make a Uservoice account and add your vote, as issues that recieve lots of votes are apparently more likely to see developer attention sooner.        ... View more

Wondering if I'd missed something obvious about your uploading two identical PDFs, I went back to review them, and saw something I'd missed in my initial eyeball review. My apologies; if I'd noticed that some of the links were underlined on the first line but not on the second, I don't think I would have stopped to ask you "but did you clear your overrides?" Like the underline missing on "reccomendations" here: That doesn't look like a case of haphazard local formatting at all, especially as there are multiple hyperlinks demonstrating the exact same behavior. Seems like you should absolutely send your document on a roundtrip through IDML.   If that doesn't work, I'd love a chance to look at the INDD before it goes through IDML. The roundtrip process removes the entire document history, and that history can sometimes provide helpful clues about how damaged documents were damaged in the first place.          ... View more

Did you perhaps send that InDesign file straight to Anubhav M? Because what I see attached to your "Sorry for the delay" message are two identical PDFs.   One generic troubleshooting step for "this document is behaving oddly" issues would be to export to IDML & open the IDML to see if that roundtrip fixed any corruption issues in the document. Have you already tried that? ... View more

It's hard to give you specific advice without knowing exactly what is going on in your document. That's probably why Anubhav asked you to share your InDesign document or a sample (not the PDF) so that they could check it.   Did you read Bob's response? Do you know how character styles work in InDesign? When you (or someone else?) made those hyperlinks, you should have seen that dialog that Bob posted a screenshot of. Making those hyperlinks should assign the "Hyperlink" character style to the text. If you select one of your hyperlinks, the "Hyperlink" character style should be highlighted in the Character Style panel. So the first thing to check is: do all of these hyperlinks have the Hyperlink style applied? If it has a plus symbol next to the name of the style, that means that local formatting has overridden the style, as in "someone came in and selected the text and unclicked the Underline button."   If all of your hyperlinks have the Hyperlinks style applied, and there aren't any overrides, then something might be wrong with your file or your install of InDesign.  ... View more

OK, maybe I jumped the gun; I really don't know if the issues in the Greek thread are related to yours or not.  ... View more

Hi Abhishek! Does this thread remind you of the other recent thread about keying accented Greek into InDesign?  It looks like exactly the same issue to me.   It's not hugely likely, but I wonder if these issues are related in any way to the "Use inline input for non-Latin text" preference.  I've honestly never touched it - I never really type anything at all directly into InDesign -  but it's my understanding from chatting with Japanese users that there are sometimes challenges when trying to key furigana into InDesign, because there's some problem switching back and forth between keying kanji directly into InDesign versus choosing ruby from the little popup window that is part of the macOS JP input method.    @mpkadobe isn't that exactly what you are trying to do with the ABC-Extended keyboard? Hold down a key in InDesign, and get the macOS little popup window that lets you select your accented glyph? Do you ever have to typeset furigana or otherwise select glyphs from a popup generated by the macOS JP keyboard - and does that work as expected? ... View more

ID-Extra's Hyperlink Pro, which breaks the URLs for me through a combination of adding discretionary line breaks throughout the URL, as well as setting the Language (which controls Hyphenation) to "No Language"   I'm sure that Ariel had a good reason for doing it that way, but I personally think it's wrong. If there is any chance that it will go through a screenreader (literally any PDF, these days), it should have a Language applied, so that it can be read aloud.  Automating discretionary line breaks (or ZWSP or whatever) is a great idea, though. Not going to @ Ariel to bug him about it, though.    My own method relies on manual glyph insertion to break URLs by hand upon review, but once again, that might not work for you, just as it doesn't work for me when I'm doing something high-volume with multiple target formats. In those cases, I use the method that Willi is posting about, including carefully grooming one's GREP query that applies the No Break character style, excluding specific glyphs where you'd want it to break.    But regardless of all that, I contend that setting the Language to No Language should not change the glyph. Are there reasons it should?   I'd say so, although I don't have any justification whatsoever for this behavior in this particular font. For instance, if I'm working in a Devanagari font, there are glyphs that have the same Unicode ID that render differently, sometimes with radically different glyph shaping, when marked as Hindi vs Marathi vs Nepali. This is a totally normal feature of the OpenType featureset. So the idea that language settings in the app should have the ability to modify glyph shapes is to me an obvious Of Course They Should Be Able To.    But when I go to Adobe Fonts and install Scala Pro myself, I don't think that my install and my font are behaving the way you describe.  I find that, when I have no stylistic sets turned on, the "Default Figure Style" as well as both Proportional and Tabular Oldstyle cause the numeral 1 to be substituted with that oldstyle smallcaps-I-lookin' glyph (hereinafter "oldstyle 1"). The only case where Stylistic Sets alter my numeral 1 is when I have either default or oldstyle numerals applied - meaning that the oldstyle 1 is displayed - and turn on Stylistic Set 1, which replaces it with an oldstyle halfheight proportional numeral. It looks weird when I've overtly selected Tabular Oldstyle figures, and the stylistic set replaces my numeral ones with numerals that are half-height, but are proportional instead of tablular.    I cannot get the language setting to affect these numerals at all.   Can you maybe post some step by step instructions so I can try to reproduce your issue?  No matter my choices in numeral style or in stylistic set, changing the applied language changes nothing in the text. This makes me wonder if we're using the same version of the font, if we're using the same version of InDesign. I'm testing version 8 from Adobe Fonts on InDesign 19.5.4.  ... View more

As I replied to Kasyan's post, if you type slowly, everything is ok. But when you type a bit faster, it happens.   Weird! That seems to imply a problem with how rapidly InDesign (or maaaaaaaybe macOS) is handling your keyboard input. Do you and your colleagues all use identical hardware, or are there differences? Are you running on Apple Silicon, or Intel? How much RAM do you have installed? Do you need to use Rosetta?    Your commentary regarding how slow InDesign ran in Safe Mode now makes more sense to me; you were trying to tell us that performance matters for this issue, and it's worse when InDesign is running slowly.    (Lastly, my apologies for showing how little I know about how Greek is keyed - turns out that 100% of my Greek translators are trying to be Serious Scholars who are just doing this whole commercial translation thing as a side gig that distracts them from their Serious Scholarship.) ... View more

But, if you change the hyphenation to "No Language",   Hyphenation is a setting that you can turn on and off. It's a paragraph-wide setting, which you can find in the Paragraph Style, or in the flyout menu of the Paragraph Panel. Language is a character setting, that you can set in a Character Style, or a Paragraph Style, or locally with the language dropdown in the Character panel, or in the Tools panel, or probably five other spaces. Point being is that there are different settings for "is hyphenation on or off?" and "what language is this?" and you're misusing the Language dropdown when, if you want to turn off hyphenation, there's a setting that controls that.     But! What if you want all of the paragrpah to hyphenate, except for the URL? One strategy is to do exactly what Willi suggests - you make a Character Style that has the No Break property turned on. Willi's method is a good one - to have No Break apply to particular kinds of glyphs, the ones where your URL would break, and apply them throughout the document with a GREP Style. That's not my personal method - I prefer to have a URL Character Style, just like InDesign does by default when you're defining a new URL, and add the No Break setting to the entire URL. That way, anytime my URL doesn't fit in my text frame, it shows as an overset, and I can eyeball it and decide myself where to let the line break happen. I typically use Willi's method when I know I'm facing a long document with a large number of links, so many that automating the process would be a better use of my time than than making three thousand careful decisions about exactly where I want my URL to break.  ... View more

When I have a paragraph that is Mostly Hebrew (or Arabic, or for that matter any language that is not written in Latin script) with a few English words here and there, then I usually make a Hebrew paragraph style, and an English character style. In the opposite case - Mostly Hebrew/Arabic/etc with a smattering of English - I make a Hebrew paragraph style with an English character style.   It is usually fastest to make a GREP Style inside the Paragraph Style to automate applying the character style. It can get tricky, depending on the content. So e.g. a character style that specified my preferred English font and English language to all of the characters in the English alphabet would work - so long as there were no parentheses, or other bidirectional punctuation, to complicate matters. I can describe some generic cases and post some  GREP query examples, if that would be helpful.     ... View more

Hello Nikos, I have some questions about your issue, and also how your issue is described. Please don't take this the wrong way - I really do want to see your issue resolved - but did you create this bug report with ChatGPT or some other AI agent? I've seen a few "bug reports" with exactly this format, and they all tend to have problems that can make the issue described harder to solve, in the end.    For example, Abhishek has already pointed out that you can't perform this test with Minon Pro:   • Unicode base characters plus combining diacritical marks — Result: Text with combining marks renders correctly without duplicated accents.   Can you maybe try it with a broader array of fonts? That might help to exclude "problems with a particular font file" as a cause of your issue. Because:   Confirmed issue is not related to font files or macOS keyboard input but seems related to how InDesign processes precomposed accented Greek characters.   You may have seen this behavior, but there's no evidence here that actually confirms this claim. I think that maybe your AI assistant is being "confidently wrong" here?    I restarted in safe mode, and tried to launch ID 2024, but it was worse! It was very slow, very laggy, and the typing problem was a disaster!!  I didn't even try to create a new user...! My iMac runs with 2TB SSD disk and 32 GB of ram, so I don'y think it's a performance issue!   It's my understanding that laggy behavior in Safe Mode on macOS happens because no drivers are loaded, so that everything is being handled by the CPU without help from the GPU. But testing your fonts when booted into Safe Mode demonstrates that your problem isn't being caused by any of those things that are not loaded during Safe Mode. If you'd tried it with a new user and it worked fine, you'd know that the problem was caused by something you'd installed in your user account.   That is probably still worth trying (trying it with a new user account), because we still have no idea why this problem is happening to you. It's not happening to Kasyan, who is also using macOS and the same 19.5 version of InDesign. Are you both using the standard Greek polytonic keyboard that comes with macOS? And using it as described here? I personally find it unlikely that the key repeat rate could affect your text input in any way at all (!??!?!), but if Kasyan said "you should check your keyboard input settings" I'd personally look there first.    I'd also look into what kinds of tools you and your fellow users have installed in common, as you've mentioned that your colleagues have experienced this issue. Do we have any reports of this issue from outside of your workplace? If not, the problem is more likely to be found in something that all of you have installed (that I wouldn't expect to find on Kasyan's workstation).  ... View more

There are other differences, but I don't think that they would get in the way of your doing French layout. Each locale of InDesign has its own set of languages in the Language dropdown, so e.g. my install has Arabic and Hebrew, which your French one doesn't, and your Chinese install wouldn't either. But I'm 99% certain that French is available in every version of InDesign, without regard to locale, so you should be okay to just go on using whatever version you have installed (assuming you don't find the extraneous CJK toolset getting in your way).  ... View more