Skip to content

Matthew Williams

My feedback

10 results found

  1. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Matthew Williams commented  · 

    This is critical!

    I have been using the same template for years without this happening, and I can confirm that it now DOES happen even though the only change was the version of InDesign. I can send a file if that helps. In the meantime, here's a screenshot. The "7" should be a proportional lining numeral like the "3" is, but instead, it's being set as a proportional old style numeral.

    Thanks!

    Matthew Williams supported this idea  · 
  2. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Under Review  ·  amaarora responded

    Thanks for reporting the issue. We are reviewing it

    -InDesign Team

    An error occurred while saving the comment
    Matthew Williams commented  · 

    If it's any help locating the problem, it seems to be related to the recomposition engine. I've had fussy tables in I design for as long as I've been able to make tables in InDesign, but the file I'm fighting with now has all kinds of weirdness happening. Sometimes when I force recompose a page with a table on it, the page is blank after the table and the remaining text flows onto the next page. Sometimes I can get a table that spans two pages to behave if I make the text frame extra wide, but as soon as I resize the frame to the correct size, InDesign locks up. It seems like it's unable to decide whether or not to repeat the column heads on the second page. It could also be having trouble calculating whether or not the footnotes in the table will fit on the page.

    The recomposition engine has a number of problems that I've reported on; this seems to be just another.

  3. 12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Under Review  ·  amaarora responded

    Hi,
    Thanks for reporting the issue
    We are looking into it

    -InDesign Team

    Matthew Williams supported this idea  · 
    An error occurred while saving the comment
    Matthew Williams commented  · 

    Looks like this is still open, so hoping my case sheds some light. When I run a GREP search for any character between two tags, text between the tags that includes a footnote reference is missed by the find. I've attached a PDF showing what I mean and an InDesign file that you can test.

    I have tried adding ~F to the GREP find (i.e., "[.~F]+"), but that seems to corrupt the find entirely. Just searching for "<u>[.+]</u>" finds the string as long as it doesn't include a footnote reference. If I add ~F ("<u>[.~F]+</u>"), the find fails to locate any occurrences, even those without footnote references. If I then delete the ~F, the resulting find—which matches the original—continues to fail to find any occurrences. Retyping the original find (rather than just deleting ~F) allows the find to work again.

    I'm working on a Mac, OS 12.6.3, InDesign version 18.1 (reported as up to date in CC on 2/13/2023).

  4. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Matthew Williams shared this idea  · 
  5. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Matthew Williams shared this idea  · 
  6. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Matthew Williams shared this idea  · 
  7. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Matthew Williams shared this idea  · 
  8. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Matthew Williams shared this idea  · 
  9. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Matthew Williams shared this idea  · 
  10. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Matthew Williams shared this idea  · 

Feedback and Knowledge Base