Pyanepsion

Hello, @Pauls All files are 400 dpi, CMYK/8, U.S. Web Coated (SWOP)v2. I can provide the alphabet files used as an example above if the private data does not appear in Affinity Designer and Affinity Photo, otherwise I will provide the files for the book that caused the problem, but privately.

Hello, @Severi, cesure.mp4 The purpose of hyphenation is to get text aligned on the left and right of the column by cutting the words according to the rules of typography (which vary by language). The purpose of justification is to adjust the spacing between words and between letters to achieve the same effect of alignment on the left and right. When the column is narrow and the words are long, justification is not very suitable. It is better to centre the text, or to align it with an iron left, or to align it with an iron right, or to set the hyphenation rules either according to the usual rules of the language, or by inserting a manual soft hyphenation.

Hi, everybody, Is there a place in Affinity Designer (same in Affinity Photo) where the Creator name of the file is stored as in Affinity Publisher? If so, how do you change it?

Hello, @avclubvids, The best method. Just go to the Layer tab of the page and uncheck the group of objects you do not want to appear. When your page is finished, don't forget to remove the unnecessary objects. Good method. You can also create several pages and put each one in a section, with renumbering, and the following section, that you show or hide on export. You can also duplicate the page version 2 and place the versions 1 and 3 on the work board.

Beta 2.0.3.1670. That’s 26 Affinity Designer files. All these files are organized and linked in another Affinity Designer file. Export the result in PNG format. Place the PNG or AFDESIGN file or both in Affinity Publisher. Export as a PDF. CMYK in version 1.7. The storage capacity of the PDF varies considerably when the appearance is the same: PNG linked = 923 703 bytes AFDSIGN linked = 3 115 702 bytes PNG +AFDESIGN linked = 3 650 200 bytes Consequence The more objects there are in any of the Affinity Designer files in the base files, the larger the PDF produced by Affinity Publisher from the Affinity Designer files. When the PDF file produced by Affinity Publisher becomes larger than it should be because of too many Affinity Designer objects, it eventually exceeds the printer's capacity. For example, I had twice placed the same Affinity Designer file in Affinity Publisher, which itself contained dozens of Affinity Designer files, each containing hundreds to thousands of objects. The PDF export created a 156 MB file that systematically failed the preflight at the printer after about 1.5 hours. I replaced the AFDESIGN file in Affinity Publisher with its own PNG export. The PDF was reduced to 22.3 MB and the calculation time was reduced to a few minutes without crashing.

Good point. Bravo, @Pauls. I had checked ‘graphic, cropping and bleed area’ in Adobe Acrobat a few days ago to check for A4 page size inaccuracies. So I’ve been trying for 4 hours to get around a malfunction that doesn’t exist. 😁

Version 2.0.0, 2.0.3 and beta 2.0.3.1670. A green colored marker has been added in the PDF export to indicate the edge of the page when using bleed. It prohibits the publication of works until this malfunction is corrected. Remarks. I noticed the appearance of this bug on all versions just after updating version 2.0.0 to 2.0.3 on a computer with Windows 11. On another machine with Windows 10 where I did not install the 2.0.3 update, but where there is the beta version, the green border does not appear. Other clarification. I have repaired then reinitialized then uninstalled Affinity version 2.0.3 then reinstalled Affinity version 2.0.0 without success. Other clarification. I duplicated the Windows 11 work-in-progress folder that displayed the green page border on the Windows 10 computer above. No border is displayed on this Windows 10 computer that has not received the 2.0.3 update. Added: despite appearances (noticed just after updating Affinity Publisher 2.0.3 in the morning and then Windows 11 in the early afternoon), as Pauls says and a little further down, the problem was actually due to a setting that was added in Adobe Acrobat a few days ago. Affinity Publisher PDF page-limits.afpub

Here are today's files. 54a75717-3e51-4102-9d33-75a2cf503e3f.dmp 361c7e19-9437-411c-9bc1-0ee9d7bfe6fc.dmp 7ed97211-a2bd-4eb4-8e6a-a61523f5e89f.dmp 28ac99d2-5e8a-4de6-9536-3a2e141306fb.dmp 8059a164-0e31-4160-ba85-b610753346eb.dmp

Yes. The phenomenon happened several times this morning, but by the time I tried to create the video intermission, it didn't happen again.

Beta 2.0.3.1670. I copy the text of the template from a page of the document and not from the template. I create a new document. This causes a premature exit of the software. style-decoration-remplissage.afpub

Beta 2.0.3.1670. This is a regression from the public version 2.0.0. The filling of the bottom of the text does not go down to the end of the text. style-decoration-remplissage.afpub

The Maintype software mentioned above will be able to flag and remove duplicate font families and fonts.

Attention: it is necessary that the user has the right to do so. This is not always the case. Very often, only an extract of the collection is provided free of charge and with various authorisations. On Windows, Yu Gothic and Yu Mincho are excerpts provided free of charge for Windows users. According to the reference software MainType from the company High-Logic: On Windows, Yu Gothic is a True Type TTC collection that includes 9 fonts divided into the following 4 files: YuGothL.ttc: Yu Gothic Light, Yu Gotghic UI Light; YuGothR.ttc: Yu Gothic Regular, Yu Gothic UI Semilight; YugothM.ttc: Yu Gothic Medium, Yu Gothic UI Regular; YuGothB.ttc: Yu Gothic Bold, Yu Gothic UI Bold, Yu Gothic UI Semibold. On Windows, Yu Mincho is a set of True Type TTF fonts that includes 3 fonts distributed in the following 3 files: yuminl.ttf: Yu Mincho Light; yumin.ttf: Yu Mincho Regular; yumindb.ttf: Yu Mincho Demibold.

I did not find any regression either. It's just that the consequences are disastrous, because the values displayed in Affinity Publisher don't correspond to those calculated, and they are difficult to detect on simple rereading when they are buried in a lot of other figures. Not for the end customer.

Hello, @DWright, I don't know why, but as of December 5, the PDF export is now correct, whereas until December 5, all exports published in the previous days never displayed the JPG raster image of a desert.

Hello, @4dimage, Yes, this is a problem in almost all languages that do not follow the same writing format as the English language. According to the International Bureau of Weights and Measures, as well as the International Organization for Standardization, the only accepted decimal separators are the point and the comma according to the choice of the regional localization used (e.g. the point in English, and the comma in French). Where numeric input devices (e.g. keypads) are given a full stop or comma, this punctuation must be understood as a decimal separator and converted according to the format specified in the regional format file (e.g. the full stop will be converted to a comma in the French regional format of France, and the comma will be converted to a full stop in the English regional format of the UK).

The solution would be for Affinity Publisher to allow you to create your own mapping tables for notes and note calls. This would also solve the other exotic mappings that we sometimes encounter and which then take so much time to implement. You should ask for this in the Feature Request section of Affinity Publisher, and link to it here in your new thread.

The behaviour seems normal on my computer on both Windows 10 and Windows 11, and everything appears to be correct.

It turns out that the bug has still not been completely fixed. It's a bit like building a nice car where everything works but you forgot to make the ignition key. Without usable PDFs, all the work done on the TTC is useless. This old format is now usable everywhere except in the Affinity suite. For those interested: FileFormat and Microsoft.

Beta 2.0.3.1670. I have created a page containing some Angsana fonts. This is a collection containing 8 free Microsoft fonts: AngsanaUPC in Regular, Italic, Bold, Bold Italic, and Angsana New in Regular, Italic, Bold, Bold Italic. 🟩All export formats work correctly except for some PDFs, all previews work correctly, everything works correctly on the screen, everything works correctly in printing. 🟩PDF (Flatten), PDFX (1a:2003) are correct. These two formats are hardly ever used in in the printing industry anymore. 🟥No other PDF exports are correct and they usually display one or 2 of the 4 AngsanaUPC fonts. It is therefore impossible to publish a digital or print book with an Opentype collection. AngsanaUPC.afpub angsana.ttc

If the original Excel file works correctly, but the Libre Office Calc Excel export 2 does not, and the Open Office Calc export 2 does not, it means that these two free suites are buggy. (But… Since the Mac version of Affinity Publisher knows how to fix these bugs in these two free suites, it would be nice if the Windows version did too. However, in my humble opinion, this is another report.)

@anto, It does seem that Libre Office Calc (is it the same with Open Office Calc?) can pretty much load an Excel file, but it doesn't know how to convert that original XLSX file to... change nothing, and then it produces a corrupted file. Affinity Publisher is not responsible for the malfunction of Libre|Open Office Calc. The Excel file I provided was created from Microsoft Office Professional 2021 and loads correctly. 😃That's good! We can concentrate on solving the 3 formulas above.

Beta 2.0.3.1670. In Excel: The Origine sheet shows the values and Excel formulas used vertically; the Fusion sheet is used for input. In Affinity Publisher: To get the formula in Excel, click in Excel on the value in the Excel value column. In the Excel Number Format bar, go to the Custom menu, and copy the type. excel-data.mp4 The numeric formula 0 should produce the value 12 for the entry 12,345, but it produces the value 12,345. The monetary formula _-* # ##0.00 €_-;-* # ##0.00 €_-;_-* "-"? €_-;_-@_- produces a space in front of the number that should not appear in Affinity Publisher. The personal time formula [h] "h" mm "min" ss "s";@ should produce the value 296 h 16 min 48 s, but it produces the value 8 h 16 min 48 s. source.xlsx Excel.afpub

Beta 2.0.3.1670. In the French version, there are 5 spelling mistakes in the activation window of the beta version. This spoils the pleasure of the discovery and makes us fear the worst. 1. The French language distinguishes between masculine and feminine unlike the English language. When an adjective agrees with a word that can be both masculine and feminine (you), it must use the neuter gender, i.e. the masculine (e.g. son), or be written once in the masculine and once in the feminine (son and daughter) or an epicene word, i.e. both masculine and feminine (child). See : Académie française. 2. The exclamation mark must be separated from the word that precedes it by an unbreakable space. If the interface does not allow a non-breaking space, it can be replaced by a normal space. 3. To separate two parts of a sentence, we don’t use a hyphen (-), but a semi-cadratine dash (–) or a cadratine dash (—). Do not write: Merci d’avoir acheté Affinity Designer 2 — vous êtes prêt(e) ! But we will write: Merci d’avoir acheté Affinity Designer 2 — votre logiciel est prêt ! 4. Words are written in full. Do not write: Lancer l'appli But we will write: Lancer l’application 5. Les articles ont un sens en français. Do not write: Activation de licence But we will write: Activation de la licence

If the original claim was about the price of the upgrade, it's clear that this was just a red herring. The real reason is not to have realized the gulf of difference between the free software Gimp, InkScape, and probably Scribus and LibreOffice compared to Affinity Suite version 1 and Microsoft Office 2021. Therefore, it seems ridiculous to me, Hanay, to want to upgrade to version 2 despite the many improvements to existing features and the unheard of amount of new features. You will never get your money's worth, unlike a free solution...