-
Posts
908 -
Joined
Everything posted by Pyanepsion
-
PDF-Export: single DinA4-page gets additional 0,1 mm
Pyanepsion replied to SKAot's topic in V2 Bugs found on Windows
I do not reproduce this malfunction by using only the Property menu. The problem does occur when you go to the Page Area tool (4dimage). Note: 🟥The error seems to stem from the insufficient number of decimal digits used for the conversion from inch to cm. 8.2700" × 2.54 = 21,056 cm~210,06 mm. 11.6937" × 2.54 = 29,7019 cm~297,02 mm 🟩To correct from an inch value, use: 8.267716" × 2.54 = 21,0001 cm~210,00 mm 11,692913" × 2.54 = 29,6999 cm~29,70 mm -
[Suggestion]Asterisks in footnotes
Pyanepsion replied to joe_l's topic in Feedback for the Affinity V2 Suite of Products
Hello, @joe_l Oh yes. According to the typographical rules, the note call Single asterisk*, Double asterisk** and Triple asterisk*** are indeed been omitted. However, this note call suffers from a very big problem****. It is only intended***** for a maximum of 3 note calls******, beyond which it becomes totally******* unreadable*******. Don't you think? In any case, in quality typography, its use is prohibited if there are more than 3 notes. *Single asterisk. **Single asterisk doubled. ***Single asterisk tripled. ****Single asterisk quadrupled. *****Single asterisk quintupled. ******Single asterisk hexatupled. *******Single asterisk heptatupled. ********Single asterisk octotupled. 😉PS. There is an error in my note calls. -
Hello, @Michael Hofmann, I apologize for my delay in replying to you. To better understand my answer, please: check ‘Text/Sonderzeichen einblenden’, uncheck ‘Vorschaumodus’ and check ‘Magnetische Ausrichtung’. Delete unnecessary text styles with ‘Text/Texsile/Nicht verwendete Stile Löschen’. Then compare your version with the new modified version (I coloured in grey the text frames). Picture 1: To do this properly, the text frames should go all the way to the borders. Notice that in the second frame the end of the paragraph and the end of the line do not coincide, which can lead to difficulties in printing. In the third and fourth frame, the end of the paragraph is even outside the text frames. Image 2: The text frames do not extend to the inner limits of the page (blue lines). This can lead to difficulties if the text becomes more important. If the text on the next page is to start at the top of the page, replace the end of paragraph character with a page break. There is a line break on page 4. The text frames for the page numbers on the master page should take up the full width to avoid the risk of overflow if the number of pages increases. Image 3: Same as above, and the text frame on page 7 does not go all the way to the top of the border. The image does not fit well to the edge and the wrapping could cause difficulties if the image needs to be moved. Image 4: As before and on page 9, there is a superfluous text frame. It is not clear what the pins are for. Image 5: As before, and if it is a book and not a binder, the middle part of the card will be hidden by the fold. The map caption at the bottom should be centred and to better achieve this, the text frame should run to the inner edges of the page. Image 6: Same as above, and there is an extra text frame (red). I don’t know the rules of German typography, but as German printers were the best I imagine it must be at least as strict as French typography. This one says that note calls must be before punctuation and separated from the preceding text by a thin space (Unicode code U+2009). Line breaks are not at the correct character size. This can cause inter-paragraph difficulties at the printing stage. If any of my answers are not very clear, do not hesitate to ask questions.
-
Very slow with delay
Pyanepsion replied to suntrop's topic in Feedback for the Affinity V2 Suite of Products
@kamelus The image of the devoured cake is abnormal, even if it is a Grimlins! Is it possible to see an Affinity file with the images recreating this phenomenon? -
Very slow with delay
Pyanepsion replied to suntrop's topic in Feedback for the Affinity V2 Suite of Products
So we are talking about 3 different malfunctions, perhaps of the same origin, detected on 2 types of Mac and 1 type of PC. The DC9V one is apparently known by Affinity. I am on my fourth book in version 2. I have never noticed this slowdown (my configuration is indicated in signature) hence, if everything is up to date (hardware, motherboard, graphics card, and other drivers), the suggestions about possible other software, often useless, running in the background. What about it? -
Data Merge(V2) pulling wrong field
Pyanepsion replied to Jerome W's topic in V2 Bugs found on Windows
Hi, @Jerome W, In order to be able to reproduce the phenomenon, could you provide an AFPUB file and the corresponding XLSX file that shows this malfunction? -
Very slow with delay
Pyanepsion replied to suntrop's topic in Feedback for the Affinity V2 Suite of Products
The operating system is therefore correct. It remains to check the other questions (files and others programs), including the one asked by Garrettm30. -
Very slow with delay
Pyanepsion replied to suntrop's topic in Feedback for the Affinity V2 Suite of Products
Hello, @DC9V, Same question: what is your hardware configuration and operating system version? -
Very slow with delay
Pyanepsion replied to suntrop's topic in Feedback for the Affinity V2 Suite of Products
I don’t know the Mac, but looking at the 2016 macOS description, it looks like your hardware is macOS 10.12 so-called Sierra which would therefore fall short of the minimum technical specifications. The minimal Mac would be a macOS 10.15 says Catalina. https://affinity.serif.com/fr/publisher/full-feature-list/ -
Leading causes text NOT to center vertically!
Pyanepsion replied to Vosje's topic in V2 Bugs found on Windows
I confirm the poor alignment on the bottom of the form. bottom.mp4 -
Very slow with delay
Pyanepsion replied to suntrop's topic in Feedback for the Affinity V2 Suite of Products
Hello, @suntrop, I suspect that your hardware is incompatible, or that some other software is running in the background. What is your hardware and operating system configuration? Are the operating system and drivers up to date? Are you using hardware acceleration? If so, what happens when you uncheck it, turn off your computer, and reboot? Does this slowdown occur on a v1 or v2 file? If it is a v1 file, save it as a v2 file, exit, wait a moment, then restart the software. What is happening? Are you using an antivirus program other than the operating system? Another utility of some kind? What happens if you disable them? If the problem persists, can you show a video or provide an AFPUB file? -
No export of some linked raster images
Pyanepsion replied to Pyanepsion's topic in V2 Bugs found on Windows
Each PDF export of the book takes a good quarter of an hour. I think this is more of a problem with the export of Affinity Publisher to PDF, because very often after this export Affinity Publisher is frozen. I don’t know why, but the PDF file produced this morning by Affinity Publisher was displayed correctly three times in a row with the raster version of the desert on the map, whereas until now only the vector versions were displayed on the PDF from Affinity Publisher. Here are the settings used. -
lenteur et plantage sur Publisher
Pyanepsion replied to Florence Perrissez's topic in V2 Bugs found on Windows
Bonjour, @Florence Perrissez, Avez-vous éteint, attendu quelques secondes et redémarré votre ordinateur après le décochage de l’accélération matérielle ? S’il s’agit d’un fichier de la version 1, l’avez-vous enregistré en version 2 puis quitté le logiciel avant de rouvrir un peu plus tard le fichier ? Cela dit, un bogue a été signalé et répertorié par l’assistance technique. L’ouverture de plusieurs fichiers dans Affinity Publisher provoque parfois des plantages, par exemple si l’on ouvre le fichier du livre et le fichier de la couverture. D’autres problèmes ont été signalés dans Affinity Publisher et Affinity Designer sur l’ouverture unique d’un très gros fichier, surtout s’il contient de nombreux fichiers liés. -
No export of some linked raster images
Pyanepsion replied to Pyanepsion's topic in V2 Bugs found on Windows
The entire map is combined in a single Affinity Designer file. This Affinity Designer file is linked twice in Affinity Publisher. The left half appears on page 8 of the book, and the right half appears on page 9. I made several tests and kept them in the Desert object. A shadow effect has been added on the desert. These appear all the time in the Affinity Publisher PDF export The first doublet is a simple vector outline fill of the desert. The second doublet is a linked vector drawing containing many objects. These do not usually appear in the Affinity Publisher PDF export The third doublet is a linked raster image. The fourth doublet is the same linked raster image in a linked Affinity Photo file. -
The Fields window does not manage any style, neither paragraph nor character. This is not its function. Its purpose is to contain variables which can be used in a text object (for example a text frame, etc.). For example, this variable could be the number of a page. In this text object, you can of course apply any style to its contents. The Data Merge Manager window extends this functionality to any data from a spreadsheet.
-
No export of some linked raster images
Pyanepsion replied to Pyanepsion's topic in V2 Bugs found on Windows
(I can only provide the files in confidence to the Affinity team.) The map drawn in Affinity Designer contains a huge amount of linked Affinity Designer files. Each linked Affinity Designer file contains hundreds to thousands of vector objects. The map also contains a raster image as a background. At this point, PDF exports with Affinity Designer and Affinity Publisher are working fine. A desert was missing. I quickly created an outline of the desert by hand and filled it with a raster image of the desert. The image appears perfectly in Affinity Designer and all exports work. I then link the map to two pages in Affinity Publisher. It appears perfectly in Affinity Publisher but not in PDF. This bug is not always reproducible. I also tried processing the image in Affinity Photo and importing the AFPHOTO file. The image does not appear either. Sometimes, however, the raster image of the desert or its transformation with Affinity Photo can be found in the PDF export of Affinity Publisher. -
Hello, @Michael Hofmann, What is interesting about your file is that it does not follow the usual rules of DTP. This makes it possible to detect bugs that appear in particular circumstances. Take a look: adding or removing a line in the main body of the text sometimes causes footnotes to disappear incongruously! footnote-line.mp4 Also attached is a very partial correction of the file. There should be only one continuous text frame from the beginning to the end of your book. Captions should be in the text on the line. Images should be positioned in front of the text with a wrap. Note calls should be located before punctuation. Notes should not be bolded. All paragraphs should end with a line break or paragraph end. Als aus version 2.afpub
-
Hello everyone, I wanted to create a world map to insert in Affinity Publisher. I first created each of the elements (trees, topography, etc.) totally in vector in Affinity Designer. I then linked these AFDESIGN images several times into another master AFDESIGN file, and then added a background raster image, and a small JPG desert raster image in a weird vector shape created in Affinity Designer. The map is finished. Exporting the PDF file displays a correct PDF file with Affinity Designer, noted with Affiity Publisher. The small linked desert raster image does not display in Affinity Publisher.
-
Disgusting pricing
Pyanepsion replied to luki1412's topic in Feedback for the Affinity V2 Suite of Products
Hello, @thomasp. The launch offer is actually cheaper than the price of the old version. But, if the new version does not bring you anything, you are not obliged to pay to continue using the old product you bought. That’s why I never rent software anymore (why should one always buy the new version of a product?) Having said that, I believe that in order to take advantage of the many new features of version 2, you should not consider version 2 as a simple improvement of version 1, but as a new product (it is much more powerful and faster) that you should consider as such and it is necessary to go through training again.
