Jump to content
You must now use your email address to sign in [click for more info] ×

mwdiers

Members
  • Posts

    25
  • Joined

  • Last visited

Everything posted by mwdiers

  1. When I add a paragraph decoration, and set a negative indent amount, for example, -0p10, the negative amount is set as expected, however, the amount immediately changes to a positive amount once I tab or click out of the Indent text box. The negative indent is properly retained in the document despite the "false positive" in the indent text box. However, if I click into the indent text box again and hit enter, or use the up and down arrows to adjust the amount, the stroke moves to a positive position. This behavior may explain a related behavior: Documents from previous versions of Publisher open with a positive Indent when previously it was set as negative. If I correct it to negative, and resave the document, the negative amount is retained visually, with the "false positive" remaining in the Indent text box.
  2. Just replying here as well. I could not reproduce the issue even in my own book. On a later launch of Publisher, it is working fine. If I am able to consistently reproduce the issue and can document the steps, I will reply here again.
  3. And now, of course, it's working as expected, even with my document. Sigh. No idea why it didn't work before, since there is nothing special about Paragraph references. Until you explained the above, I didn't realize that choosing a paragraph is just a shortcut for creating an anchor. Thank you for your help.
  4. Thank you for that. That's an odd location for it. "Show Anchors" doesn't scream "Interactive" to me. But I guess I'm thinking of them from the perspective of a printed book, not internal PDF links.
  5. Once an anchor is created, there does not appear to be any way to display the location of that anchor in the text itself. In InDesign, there is a special character type for anchors. Such an option should also be present in Publisher.
  6. I'm working on converting a large InDesign book to Publisher. The Cross-References feature was the last piece I needed to move entirely to Publisher. I was pleased to discover that cross-references work properly across chapters in a book. I was afraid that would be overlooked. In the book I am working on, there are a large number of cross-references to footnotes, and the reference includes both a page and note number thusly: "p. <page number>, n. <note number>." The only working option at present to refer to these is by Paragraph. However, the paragraphs do not show the note number in the "Insert-Cross References" dialog box, so even if I filter on my "Footnote" style, it's a pain to find the correct note. Therefore, I am suggesting that "Note" be added as a link-to type, such that it displays the current note number in the Insert Cross-Reference dialog box. If that is not feasible, alternately, please make it possible to use a named anchor in a note. At present, when using the "Anchor" type, and the anchor is in a note, the "Note Number" field does not work. It always displays "0". Page Number does work correctly. I believe this is a bug, and I reported this in the bugs forum already. I would prefer that Anchors work correctly with notes, because some of my footnotes span more than one page, and sometimes the reference should point to a place in the note on a later page. The only workaround for this is to combine two cross references. One for the page number using an anchor reference, and one for the note number using a paragraph reference. Not ideal.
  7. If an anchor is placed in a Footnote, and a cross reference is created for that anchor, the "Note Number" variable returns "0" instead of the footnote number. It works correctly if a Paragraph cross-reference is used instead. However, it would be much better if the paragraph references showed the note number in the insert cross reference dialog box. For a document with a large number of cross references, it can be hard to find the correct one, even when filtering by my footnote style.
  8. I am attempting to import a book project I currently have in InDesign. I am running into multiple issues with the formatting of footnotes. Part of this problem appears to be units that are being interpreted incorrectly. Aside from the fact that the InDesign footnotes are not imported (which I assume is simply not yet supported): Footnote rule length is being interpreted incorrectly. A 1 in rule ends up being slightly shorter than 0.25". "Gap between" creates an entire line between footnotes even at 1 pt. I cannot set a gap between footnotes less than an entire line. When creating a new "in note body" number style from the "New..." option in the "Number Style" dropdown , the units are being interpreted incorrectly. A character size of 10pt is extremely tiny. When I re-edit this same style in the "Text Styles" panel, and change it to something else, and back to 10pt, the size is corrected. Thereafter, if I edit that same style from the Number Style dropdown, it works as expected. When I start with a new Publisher document, and copy-and-paste in the body text from the IDML import, none of these problems occur. I have attached the IDML file that exhibits this issue. I will proceed by using the IDML imports just to copy-paste the formatted text. Chapter 1.idml
  9. Must be some corner case, or perhaps macOS version dependent, because I have neither of these issues. I can restore the minimized app, and PDF exports show previews.
  10. Thank you for fixing the paragraph decoration bug where when you open an older version document, the line appears in the wrong location until you reset the position parameter. I didn't report this bug, but it's nice to see it fixed.
  11. When attempting to resize a photo, and activating the linked aspect ratio toggle (the button on the toolbar between document/canvas and unit selectors), the ratio is ignored. Changing either the width or the height slider has no effect on the other dimension. The only way I have found to proportionately resize a photo is by doing math. Also, changing the units to something other than pixels has no effect. The sliders remain in pixels. You can, however, bring up the number entry box, and change the units in the box, as a workaround. Also, why are there two places to enter DPI? On the toolbar and on the slider.
  12. I'm very happy we got book support. I just wish that it was enough to abandon InDesign for a major project I am working on. The one key feature I need is Cross-references, that it, forward and back references that can span multiple book sections, and automatically update page number and/or note numbers within the text to refer to those references. We already have Anchors and Hyperlinks. That gets us most of the way there. Now we need to tie it to fields with a specific format to refer to those Anchors. We need to be able to define a template for these references, so that we can insert page and/or note numbers (in the case the Anchor appears in a foot/end note). And it needs to work across different documents in the same book. Don't get me wrong. This is still great progress. But I long for the day I can abandon InDesign.
  13. For the last few versions of Affinity Publisher, I am getting a consistent crash when I open the Export dialog box. This happens whenever Publisher has been sitting idle for some period of time, usually minimized. When I maximize it and then attempt to export a PDF, this is when the crash occurs. Crash log is attached. I can then restart Publisher, and export works without crashing. The crash only occurs when Publisher has been idle for a while. I am currently using 1.10.4, on macOS 12.2, an a Macbook Pro 16" M1 Max. affinity_publisher_crashlog.txt
  14. This is still a problem as of Publisher 1.10.4. In my case, I copy and pasted a couple of text frames from a different Publisher document. The source and target document are the same DPI, i.e., 600 DPI, set at document creation. When I link to a new or empty text frame on the next page, the flowed text shrinks by 50%, which I imagine represents a DPI issue, the default of 300, vs 600. The only fix I have found is to create the text frames from scratch, and only copy-and-paste the frame content.
  15. Cross references are a must. Forward and backward references are necessary to refer to automatically insert figure and page numbers. But we also need footnotes and endnotes. The anchor point for the forward-backward references also needs to be placeable in footnotes and endnotes. Basically, Publisher is useless for book publishing without these features, except for the most simplistic books. Books are, in fact, the only thing I keep InDesign around for. But for Publisher to be used as a robust book-editing solution, we probably need more, such as the ability to combine publisher files together into a single book with all page numbering and cross references intact and working. Or perhaps Affinity has better ideas for how this could be handled. InDesign's book system can be rather fragile.
  16. It is understandable that embedded fonts will always be a problem in a placed PDF, since the only practical option with a placed PDF is to render all fonts as curves. And that, of course, will thicken the font strokes, as hinting does not translate to beziers.
  17. Interesting. That's actually a relief, as I have distributed a few of these supposedly bad files to people already. Those screenshots came from Publisher after placing both PDFs into a new Publisher document. So Publisher is technically the PDF viewer. So, as Walt pointed out, I guess the issue is with importing PDFs with subset fonts and ligatures, NOT with the creation of the PDFs in the first place. As this is a known bug, I trust it will be addressed in due time.
  18. By the way, this file demonstrates that Publisher follows the OpenType specification really well. As well as InDesign. The Caeciliae font is generally not usable on most word processors because they don't follow the metrics accurately enough, or cannot handle multi-character glyphs. I used to create these chant pieces in InDesign, and had zero issues doing it in Publisher (other than the export issue, that is).
  19. This is on: Affinity Publisher Beta 1.8.4.663 macOS 10.15.5 2019 16" Macbook Pro. See the two attachments. When exporting a PDF, fonts which use multi-character compositions are not properly subset. These are fonts which require two or more characters to be entered to type a single glyph. In the two attached PDFs, the font in question is Caeciliae, which is a Gregorian chant notation font. Most of the glyphs in this font require multi-character composition. Since I have the font installed on my system, the issue is not evident until I try to embed these PDFs into another Affinity document. See the screenshots which demonstrate the issue as I am seeing it. PN-English-No Subset Fonts.pdf PN-English-Subset fonts.pdf
  20. This is a known issue and is fixed in the beta. The problem is specific to Mac Catalina. Exported PDFs have their fonts converted to outlines. Here is the current Publisher beta which fixes the problem:
  21. IDML import has so far worked way better than I expected. I know it won't ever be perfect, but I'm sure it will continue to improve. To that end: tab stops are not translating correctly. Not exactly sure what is going on, but the resulting tab stops have no relation to the originals in InDesign, and have to be redone after import.
  22. Now that 1.8 is out, the last piece in the puzzle keeping me away from Publisher has been removed. It now has IDML import that actually works (well, there are glitches, but it basically works). It will take me a long time to fully transition from Adobe, but I will do so. Footnotes, Endnotes, and a Cross-reference system is critical for me as well, and I will still have to use InDesign for book publishing for that reason. But I will use Publisher for everything else, if nothing more so that I can break it, file bug reports, and help to make it an even better product. As the CIO of a large printing company who pays out literally hundreds of thousands of $ to Adobe every year, I am dedicated to the overthrow of the Adobe Empire. Affinity is the only viable alternative to the unholy Adobe trinity.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.