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

pquadrat

Members
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello. as I tested today with Publisher version 2.0, the left/right Master issue is still/again reproductable. My scenario: Adding a single page using the same Master before page 1. Result: Header of old page 1 (= new page 2) is deleted completely. Page 3 got a second title (from the Master) additional to the original one. Pages 4 and 5 are correct. 😕
  2. Sure, see attached. Because the images are refered but not included, I here add the images, too. All files should be in the same folder. Thank you in advance. Patrick Arcada_Tutorial_v1.afpub Arcada_Tutorial_v2.afpub
  3. Hello, I found a mismatch in the behaviour between Master page and referred pages in Publisher when using Photos and the Photo App for masking. I did the same in Version 1.10. there was no difference and the referred pages were correct. First, my workflow (I'm using german version; I hope, my translation of the menue ist correct). I add a landscape photo (including some sky) to a Master page (including a darker starry sky as a background for better contrast) and position it on the bottom (as a letter layout). I activate studio link to go to Photo App. In the Photo App, I select (with selction brush) only the bottom areas of the photo (for later deleting the sky) When selected, I go to (german) "Verfeinern", may be "refine" in the english version. In the dialogue, I select "new layer with mask" ("neue Ebene mit Maske") As a result, the Sky vanishes, the landscape results. I go back to Publisher App (Studio Link). Result: The Master page shows correctly the landscape without the sky. The referred pages show the complete photo inkludung the skay. As said, Version 1.10 of Affinity Publisher works correctly. I have a file designed with v.1.10 and one with v.2.0 and according to the sky on the referred pages (not the Master pages) they differ. I add Screenshots of the view of the Master and the referred pages, created with v1 and v2 of Affinity Publisher.
  4. I forgot: For binding, you may use a stapler or - as I did - a needle and yarn for classical thread stitching. It looks very nice and valuable, but needs some patience.
  5. I produced a simple booklet with Publisher today. General steps (I use the german version; maybe it is slightly differnet in English): Note, that you need a booklet with 4 or multiple of 4 pages. Print: with "File" > "Print". In the setup window use: Printer: PDF printer (a PDF printer e.g. Adobe, Kofax etc.) Button Properties: use Landscape format (mostly) "Layout" > "Model": "brochure" "Bleeds and marks": activate "incl. Bleed areas", "incl. Printer brands", "Cutting marks", "passer Marks" Store the file Print by using a duplex printer OR first by printing all odd number pages (1,3,5,...), turning around the pages (by taking note of the orientation and page sequece), followed by printing the even numbers (2,4,6, ...). For both, your printer needs to positionate exactly, because of the cutting marks. As @Old Bruce said: use a cutter, a cutter pad, lineal and your hands Sometimes, it's beneficial when using your hands and seeing the results.
  6. Dear Developers, Users & Fans of Affinity, I'm newly in Affinity products since v.1.9 but have been working several years within the context of Adobe products and other (C1 etc.). Using the Affinity products, I became some kind of a fan of them. Coming from the view of my work, I want to underline the need for syntactical XML import in Affinity Publisher, as in my company, we have established a Single Source Publishing Workflow based on Database and especially highly syntactical XML-Data, publishing into Web, other electronical Media up to Folders and Books since somewhat before 2010(!). There are many reasons for leaving the "Adobe Pathway" or proprietary other products like QuarkXPress. So, in (semi)professional context, import of syntactical XML is very important. Thanks and have a good day.
×
×
  • 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.