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

Mooxo

Members
  • Posts

    53
  • Joined

  • Last visited

Reputation Activity

  1. Thanks
    Mooxo got a reaction from Ash in Data merge allows fields to set URLs, File locations, Emails and Anchors   
    This is phenomenal - thank you! I've just tried it and it works a treat. Very intuitive, and super flexible. You guys never cease to impress with the work you do on this wonderful suite of tools. Thank you again.
  2. Like
    Mooxo got a reaction from Petar Petrenko in Data merge allows fields to set URLs, File locations, Emails and Anchors   
    Yes, exactly that. As a concrete example: if you were generating an exercise book with questions and answers (or a quiz book, or similar), you could have all the answers in one data file merge file, including anchors, and all the questions in another data file, including links to the answer anchors. That way when you generate the final file, each question could link to the relevant answer later in the document. 
  3. Thanks
    Mooxo got a reaction from walt.farrell in Possible bug: Rasterize layer / master page   
    Here you go. 
    1. SVG file (embedded). The layer can be hidden, resized, opacity changed, deleted, etc.

    2. Rasterised the SVG. The layer can no longer be hidden, resized, opacity changed, or deleted.

  4. Like
    Mooxo got a reaction from MikeTO in Possible bug: Rasterize layer / master page   
    Yes, partial workaround. But you cannot hide the layer, change its opacity, resize it, or edit it in any other way. So you have to be sure your image is exactly as you want before rasterising, or delete it and start over.
  5. Like
    Mooxo got a reaction from walt.farrell in [1.9.0.902] Merge - Character encoding problem ?   
    This morning I tried both these methods on my original numbers file, and both worked perfectly. So that was one file with an accented character added to the header row, and one file with no extra accented characters, but output from numbers as 'Western (ISO Latin 1)'.
    Thanks again to everyone who responded.
  6. Like
    Mooxo got a reaction from Lukas G. in [1.9.0.902] Merge - Character encoding problem ?   
    This morning I tried both these methods on my original numbers file, and both worked perfectly. So that was one file with an accented character added to the header row, and one file with no extra accented characters, but output from numbers as 'Western (ISO Latin 1)'.
    Thanks again to everyone who responded.
  7. Thanks
    Mooxo got a reaction from Jon P in 1.9.1.967 - Error on PDF export   
    Okay, thanks. As I say, I was able to export it okay from 1.9.0 so it was more about logging the bug.
  8. Thanks
    Mooxo got a reaction from Jon P in Publisher 1.9.0 crashes opening file   
    I just wanted to update this thread to say that the most recent beta (1.9.1.967) has fixed the problem for me — I’m now able to open both the files that were crashing before. Thank you!
    The beta has introduced a new bug for me, but I’ll post that in the beta thread (pdf export related).
  9. Thanks
    Mooxo got a reaction from Patrick Connor in 1.9.1.967 - Error on PDF export   
    This beta has fixed the file opening bug that I reported in the Bugs forum. However, both this beta and the previous one are causing me problems with PDF export...
    Mac OS Catalina 10.15.5 running on a Macbook Air (model id 6,1).
    No external devices other than permanently attached SSD.
    My problematic document is 209 pages, imported from IDML, reformatted, and saved as regular afpub. Other documents I have tried have worked ok.
    When I try to export to PDF I get an error: “An error occurred while exporting to: <filename>”.
    The error happens wherever I try to export the file on the system, be it local drive or icloud.
    I can export pages 1-21 without problem. Any page from 22 onwards that I try fails. Exporting 1-22 fails. Exporting 22 or 23 on its own fails, etc. There is nothing I can see that is different about pages 22 and on — they are a continuation of the same text flow using the same master pages, fonts, etc.
    Preflight shows only spelling warnings.
    If I set it to export text as curves, the error remains.
    If I set it to disable  advanced features, the error remains.
    The only way I can get it to export is to set it to ‘rasterize everything’ (though this makes an unacceptably large file).
    I have done the PDF logging thing and the error at the end of the file reads:
    [Last exception 1113 in PDF_rect]["Number parameter 'y' has bad value '-215723171361689126693305940258774955854831264025790984366933353005963925736340364766740324843394693930763637765777116666640215904422765062065054010734467522159667853218497575660516896304869827726833649588347945387400948462600982054168988953002738186639960' (maybe not initialized)"]
    I’ve no idea if that’s useful. I’m happy to provide the log file and the document, if it helps.
    NOTE: This only affects the beta version. If I open the file in the non-beta 1.9 release, the export works perfectly.
     
×
×
  • 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.