AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
The software version can be seen on the splash screen and the About dialog (in application menu, Affinity Publisher > About). UPDATING TO THIS VERSION (Free for existing customers) PDF Export - Images with a 1 bit mask could be output incorrectly (or not at all)Įarlier changes and fixes in 1.8 since 1.7 (including the new 1.8 features) are listed in some detail in this 1.8.1 update announcement. ![]() Fixed issue exporting caused by hyperlinks.IDML Import - crash fixes for specific documents ![]() IDML Import crash fixes with specific documents (Mac) Fixed crash typing into Font name selection UI Spelling not honouring the language set for the text frames when opening documentįix for ligatures being disabled in justified text Renaming hyperlinks in Hyperlink Panel can detach objects Hyperlink Panel wasn't displaying hyperlinks on Master pages ![]() Stability and performance improvements adding and deleting pagesįixed issue with sections being incorrectly deleted when pages deleted (Mac) Fixes for blurry icons on non-retina screensįixes for slow page operations - adding / deleting /moving etc (Mac) Fixed possible crash on File > New in Designer Persona (Mac) Changing preflight profile with no document open causes crash Stability and performance improvements for geometry operationsįix for collecting multiple instances of the same resource imageįixed issue with placed Artboard documents losing selected Artboard IDĪpplication (bought through MAS) will now run on Lion and Mountain Lion (again).New document panel - saves settings between uses New document panel - terminology and UI tweaks The changes in Affinity Publisher for macOS 1.8.2 (made since the last release Affinity Publisher on macOS 1.8.1) are as follows:įixed possible source of instability when enumerating fonts at startupįix for bleed not available in Photo Persona It is impossible to say if there are BIG changes in code and program architecture that the mentioned words in capital letters imply (perhaps just for me), but I hope I am wrong and we'll see fruits of the kinds of internal changes that have been made, which would make it possible to have, at some point (not necessarily along 2.x path) big (power) usability changes like scripting support or at least improved macro operations (and not just in Photo), improvements in PDF imports and exports, interchange file format supporting edits, improved search and replace with area limits and ability to save GREP definitions, CJK and RTL support, etc.We are pleased to announce an update for the macOS release of Affinity Publisher, version 1.8.2 Yes, there are important improvements, like this one, notes in Publisher, antialiasing in basic selections in Photo, global object selections, shape builder and warps in Designer, more robust Boolean operations in vector graphics in general, and a few other, well worth getting an upgrade (especially if working on multiple platforms). I have to disagree, here is one raw file development is quite different and it is better. in system requirements, but this is another story). Anyone expecting fundamental changes throughout the app trio will be sadly disappointed (there are fundamental changes, e.g. In addition to new features (like notes in Publisher) I have only seen cosmetic changes been made. I would be more than happy to proven wrong, but so far I have not seen any traces of radical changes or improvements between the major versions (at least on Windows platform, which I have tested more so far), to deserve the advertised terms REFINED and REDESIGNED. UPDATE: More generally, some users on this forum have implied that there are fundamental changes between 1.x and 2.x versions of Affinity apps. This means that notes included in IDML saves from InDesign are not so far translated to native Publisher notes (neither footnotes or endnotes). 1.x and 2.x, even if version 2.x now supports notes (as does IDML). IMO there are no changes in IDML support between Publisher v. I am not sure that I understood what you mean. I want to know if the code was moved untouched from V1, or if anyone has worked on it to fix/improve (in which case I'd check it out). ![]() IDML should have been sufficient for my needs.
0 Comments
Read More
Leave a Reply. |