Dennison
-
Posts
342 -
Joined
-
Last visited
Posts posted by Dennison
-
-
Hopefully it iwill be trivial to locate.
It's been around for at least two years as it has happened in previous books I was formatting.
-
copied from a pdf that was created from a Word file
-
Used the bottom centre handle
No - did not use the scaling button on the bottom right side - used Text Frame icon from Tool list and click-mouse-drag to margins
-
Too much text in Frame A so created an overflow Text Frame.
I created a new Text Frame and stretched it out to fit the page.
Then highlighted and selected Text Style - Normal
linked Frame A to Frame B
and moved up the bottom limit of Frame A to shift text to Frame B
-
I've had the same issue through multiple documents and multiple Afpub beta versions.
Latest incident:
Text overflows Text Frame A
create new Text Frame B on page 2
check Text Style is Regular (same as A)
link Frame A to Frame B
reduce size of Frame A so text flows into Frame B
Text in Frame A is 10 pt.
Text in Frame B is 2.4pt
If this is not a BUG then it must be following the most bizarre logic rule.
-
disappointing that after FOUR YEARS later and numerous calls there is still no way to find a hidden index - ie. an empty text frame that prevents an index being inserted.
In my latest book, ALL text frames were created new for the TOC and for the Index but still I cannot insert a new index. The document has no Character or Paragraph styles have word Index in them. So WHERE is the hidden index?
If I Update Index- then the manually edited TOC is replaced by an Index. But the TOC frames were NEW. And manually edited because of a BUG that inserts superscript characters into auto-generated TOCs.
AfPub is a great product but, please, after four years it's time to provide a way to solve this ongoing nightmare.
-
Thanks for confirming what I was suspecting.
Good idea- that's what I'll do.
-
Thanks. i'm still verifying but so far that's not the case.
TOC text styles were unchanged from previous book. I used the file and exact setting of the previous book for the layout of this translation of the same book and simply substituted (paste) the first language.
Procedure I followed:
Insert TOC in new text box
selected Chapter Heading (to give one example()
= superscripts introduced.
Checked Text Styles:
Chapter Heading style based on Main TOC: Entry
Superscript: No change
go to Main TOC: Entry
based on No Style (so no styling)
Superscript: No Change.
So in this example, where was the superscript introduced?
-
Created a new TOC in a book – every N letter and every number has been superscripted - see screenshot.
I can see no obvious reason for this occurring. The file and associated Text Styles are inherited from a previous edition that did not have this problem.
Any suggestions or solutions? (Manually correcting is not a workable solution as it would preclude updating).
Thanks
-
-
I may be having the same issue - an empty box with no handles, except that it cannot be moved. Not a Master Page item.
AfPub 2.3.0 (2096)
-
-
Thanks Mike. I will check if that's what Im inadvertently doing
-
I know I have posted about this before - than updating the Index causes the TOC at front of book to be replaced by the Index. And I've been told I'm adding some Index formatting.
But, after 13+ books all with Indexing, and taking great care with Indexing because I know it is glitchy, I'm still getting the same issue.
Only the TOC at the front of the book is affected - which strongly suggests to me that it is not random operator error. If it was Index formatting by accident it could be expected to show up each time randomly in different places in different books. It's always the same error.
Anyone else having this issue?
The workabout is to delete both the TOC and the Index. Complete the Index first and when certain there will be no changes, then insert the TOC and adjust the formatting as needed.
-
-
What am I doing wrong?
Table Text Style is set to Arial 10 point with 0 baseline.
But each box in a new table defaults to 8 point +3 baseline.
When the
Text Style is corrected and Saved OR the point size is changed in the toolbar, updating the Text Style reverts is to 8 point and +3 baseline.When I highlight 3 boxes, the baseline cannot be changed. But the baseline can be changed one box at a time.
Baseline Grid is unchecked in the Text Style edit.
Text Styles in general seem to have a mind of their own - some failing to update when changed and the update saved.
Any insights welcome.
-
All the text was formatted with Text Styles, so it's not a left over
Select the text, the font size is blank.
Click between letters the font size is 14 (as per Text Style.
Click between the Marker and first letter, the font size is 58.3
Select the first word and select 14 size font, the marker goes back to normal size.
It does seem like an aberration - though actually bigger markers makes them easier to find again.
-
Is anyone else starting to see GIANT Index Markers appearing what seems to be randomly?
Have I missed a setting somewhere?
Closing file and reopening does not change. Not all Markers.
I'm curious more than alarmed.
-
Thank you Sean for delving into this. I followed your vid and have cleared all the Index Markers - voila! Thank you so much!
IMHO this does open a potentially larger issue of how all this inadvertently Index formatting is getting repeatedly into every document.
1) operator error - maybe the first time, but not on book 12. I am fastidious about using the desired Text Style as I enter text. The look of the book is created as I enter text and images, not pre-designed. On my Text Styles dropdown, Index et al are well separated from the styles I use regularly, so I do not believe I am making multiple accidental clicks.
2) new Text Frames inherit invisible Text Style. I know the discussion about default Text Style in a new Text Frame has happened elsewhere on the Forum. At the moment, it is not possible to create a Default Text Frame style. As I understand, at the moment, a new Text Frame inherits whatever Style was last used in a new Frame. So a random mistake can be inadvertently copied across a document. My preference is to allow a choice of Text Frame - a default set up in Preferences for all new Text Frames OR inherit style one Frame to the next.
3) I've noticed multiple times in the Betas what seem to be random changes of Text Style. When I re-open a file, sometimes some text styles have changed. Can't demonstrate that because it's intermittent and random, but it happens from time to time - as in Text - Regular becoming Index Entry 1 etc.
Anyway, thank you to you and all the team for a great product.
-
My understanding is that one has to search each Index Character and Paragraph style one at a time. It's cumbersome and very slow and tedious.
I've had "phantom" indices appear in most of my book layouts, despite being super careful not to add any Index text styles, only Add Index Mark.
-
-
Thanks. First thing I did - been through this circus multiple times. Still will not allow a new index, and I am certain I did not use any index formatting anywhere else (I'm very very careful about this, knowing from past experience how much time gets wasted looking for invisible text!)
-
Yes, but the tasks are enjoyable using Affinity Designer and Publisher!
And keeps me out of trouble.
The only thing that really annoys me is the INDEX. I've just deleted the Index in a book - but AfPub won't allow a new Index because somewhere in a 288 page document there is an Index Character. BUT in that case, how were there TWO indices before (I just deleted one)?
The app badly needs a Go To Index button.
-
Thank YOU for your help and the great apps.
12 books in 36 editions in 5 languages! ++
Text is tiny at the top of next frame when frames are linked
in V2 Bugs found on Windows
Posted
Okay thank you.
None of the files were sourced from IDML.
I certainly have no memory of changing dpi from 72 to 300 - but it's certainly possible; however, new layouts are by default 300 dpi so I'm not sure why I might have changed it to 72 and then back again as all my files are for printed books.
Is there any date when these bugs might be corrected?