A_B_C

Absolutely agree … anything that requires to select a page or hover over a page is insufficient … 🙁

Hi,
We really need a fixed visual clue in the Pages panel to check or search easily which Masper Pages are applied by pages.
For example, in a book I use 3 MP :
A - Blank MP (only the main text frames linked, for title, details, etc.) B - Chapter MP (main text frames with huge top margin for chapter title + pages numbers frame) C - Text (main text frames  + pages numbers frame + title/author frame) Once I flowed all the text using the Text MP (=> ± 300 pages), I apply the Chapter MP to each page containing the beginning of a chapter.
For now, all is OK, it's the first draw.
Next, I need to add/modify/edit the text: the flow is different, and I need to correct the applied  MP, since the Chapter MP and the Text MP didn't follow the new flow of text.
 
It's difficult to check easily where are applied the MP while scrolling through the Pages panel. I can enlarge the thumbnails, but scrolling won't be faster… Waiting for the helptip to show is a pain, and sometimes not accurate or fast.
 
Waiting for the tooltip…

 
Below, I can visually search for Chapter MP applied to plain text pages, but it's not easy, and it won't be as easy to find if there's no big visual differences in the pages (for example, only a different variable/text line at the top of the page: part + chapter title instead of author's name).

 
Another example where the MP are rightly positioned: why does the tooltip show first the right page MP's name, and second the left page MP's name ? I usually read from left to right, and expect the tooltip to show LMP and RMP's names.

 
Visual clues could be inside the pages or outside.
On MP "C", visual clues would show as nothing or "A" or "A+B", etc. if different MP are applied on it, but on the pages it would only display "C" (or "C+D", etc. if there are more than 1 MP applied to the page).

 

Thank you, Jon! 😀

I've logged this to see if we can do something to get it a bit more visible.
Thanks

Thanks for fixing Shift + Tab IDML import. Works fine. 😀

That one will make a lot of people much happier.

Status: Beta
Purpose: Stability and General Testing
Requirements: Purchased Affinity Publisher
Mac App Store: Not submitted
Download: Download
Auto-update: Not Available
---
Hi,
We are pleased to announce that a new Customer Beta of Affinity Publisher (1.8.0.549) is now available as a download from the link above.
As this is a 'Stability and General Testing' beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity where you may be adversely affected by the application failing, including the total loss of any documents. 
We hope you enjoy the beta, and as always, if you've got any problems installing or running up, please don't hesitate to post in this thread. 
Any problems actually using this version please make a new topic in this forum and we'll get back to you as soon as we can. Please feel free to leave general suggestions and comments in the Discussion Forum. 
Many thanks for your continued feedback.
---
Fixes and Updates
New Document Dialog
(Win) Implemented new New Document / Template dialog
(Mac) Miscellaneous fixes
General
Layers thumbnails now update when a global colour is changed
Convert to text frame now preserves corners
Fixed creation of unnecessary duplicates in Resource Manager / Collect...
Added 'Show in Explorer / Finder' to Resource Manager
Document Grid drawn incorrectly when switching between Master and Regular View
Fixed crash adding assets from afpub file
Assets imported via an afasset file aren't made visible if no categories currently exist
Can now search for missing fonts via Find and Replace
Fixes for Baseline Grid propagation from Master Pages
Preflight
Preflight check for missing glyphs
Text
Fixed crash in text composition. Recent regression
Fixed for Even / Odd Page Breaks
Fixes for Pinning Page UI
Column Rules now honour Text Wrap
Fixed Text Wrapping issues that could occur with large negative borders
Wrap settings saved in an objects style weren't correctly applied
Added more 'special characters' to the Bullets and Numbering character pick lists
Fixed Text Styles Panel preview for styles with a large 'Space Above'
'Word Joiner' and 'Zero Width Non-breaking Space' can now be entered with ToggleUnicode, and have their own "Show Special" representation.
Pasting text with Move Tool active now appends content to non-filler text rather than replacing
Warning now given when attempting to spell check text with no suitable dictionary available
Improved Title Exceptions granularity to never change certain words
Specific font incorrectly keeps italics activated
(Win) Drop Scale for Descenders option was missing
(Win) Previews on Typography Panel corrupted
Tables
Deleting row(s) in table caused alignment settings to reset
Table format > Frame stroke alignment is not remembered when changing the width
TOC
Pinned Frames now use the location of their pin to influence the order of TOC entries
(Win) TOC Panel was missing separator field
Index
Fix occasional crash opening Index Panel
Import
PDF Import: PDF Import now supports JBIG2 compression.
DOCX Import: DOCX Import now supports linked images
IDML Import: Shift+Tab (Right Indent Tab) not imported
IDML Import: Gutter values could be incorrect
Export / Print
PDF Export: Images in Embedded Documents weren't downsampling to correct DPI leading to unnecessarily high-res bitmaps.
JPEG Export: Include bleed was missing
Updated Help and Translations
---
To be notified about all future Mac beta updates, please follow this notification thread 
To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this thread

TRO CHOI DAN GIAN - FOLK GAME in TET
 
Tha Dieu

 
 
Nhay Day

 
Rong Ran Len Cay

KHAY MUT - Dried candied fruits
 

Download afdesign file
 
Mut Bi

 
 
Mut Sen

 
Mut Dua
 

Hot Dua

 
 
Theo Leo

 
 
Cuc Chuot
 
 

(This subforum is not really the right place for this, but I’d like to have it found where people might look for it.)

As most of you are aware, the Affinity apps can’t handle included fonts in PDFs, they always try to parse the PDF and do a good job about that, except they can’t use the embedded fonts but try to replace them with fonts installed/active on your system. Often you don’t have these fonts and must not replace them, e.g. if you get ads from a customer. There’s no possibility (yet) to “just place” a PDF as an image.
You could rasterize the PDF into a high resolution bitmap – but not with one of the Affinity apps, and if you wanted to use Photoshop, you wouldn’t use Affinity...
The best solution is to convert the text in curves. You can do that with Acrobat Pro, but I am here to avoid “Clay” apps. It’s easy with GhostScript on the command line:
gs -dNoOutputFonts -sDEVICE=pdfwrite -o Myfile_nofonts.pdf Myfile.pdf Or to convert all files in a folder:
for PDF in *.pdf; do gs -dNoOutputFonts -sDEVICE=pdfwrite -o "${PDF/.pdf/_nofonts.pdf}" "$PDF"; done You must first change into that folder, of course. And have GhostScript installed; you can get it via HomeBrew or MacPorts (there are also binary packages around I guess).
(EDIT: The quotes around $PDF are necessary if your file names contain spaces.)

You can’t avoid getting your hands dirty on the command line (Terminal.app). You can read on the websites of HomeBrew and MacPorts how to install them. Which one you use is a matter of taste, please don’t anyone start a flame war! I’m used to MacPorts; HomeBrew users please help with that.
You need Apple’s development environment Xcode, you can install it via AppStore (or make a free account on developer.apple.com and download it there, as MacPorts suggests). You’ll never start that app yourself, but it contains the necessary compilers etc. that let Ports or Brew build programs from sources.
Xcode is a huge download, after it’s completed you can install the necessary command line programs and confirm the license. Open Terminal.app and type/copy these lines into its window (don’t forget to hit Return after each line):
xcode-select --install xcodebuild -license Then you download the pkg/dmg for your macOS version from https://www.macports.org/install.php and install it.
This installs the basics for using MacPorts, but no programs that you can use. First update the list of ports (packages), again in Terminal:
sudo port -v selfupdate (You should run that every month or so if you want to stay up to date.)
“sudo” means “superuser do“, i.e. “execute as administrator”, you need to enter your account password to proceed.
(And it means the whole thing won’t work if you don’t have an admin account, e.g. in a company, then whine at your admin until they yield and install that stuff for you.)
If that worked, you’re set to finally install what you wanted:
sudo ports install ghostscript This will download the sources, compile them and install ghostscript in /opt/local/bin/. To check that, call
which gs That should answer with “/opt/local/bin/gs”. If it doesn’t, close your Terminal window, open a new one and try again. Still doesn’t work? Then you can call gs with the full path (i.e. “/opt/local/bin/gs”) or add the path to your PATH variable (that determines where bash, that’s the “shell” running in Terminal, looks for commands/programs):
echo "export PATH=/opt/local/bin:$PATH" >> ~/.bash_profile A lot of hassle for a single program, but MacPorts as well as HomeBrew offer a lot of tools and fun stuff, mostly ported from Linux or *BSD, that you might like. That’s a tad off topic here...
It’s probably easier to enter “ghostscript macos download” into your favourite search engine and choose one of the sites that offer free downloads. I don’t know which you can or should trust.

Yes, I would think so. 

Last I heard, the preliminary development work on an Affinity DAM had stopped completely so they could devote more resources to feature additions/refinements & bug fixes for the 3 existing apps. It is unclear if this means they have permanently shelved the project or they are waiting until the existing apps are more fully developed to resume work.

Here's my first thought: em space and most of the other "fancy" spaces are normally treated as a non-breaking spaces. It appears this non-breaking quality is related to determining how to count the number of words, such that "1 The" is considered the second word. I have mixed feelings on whether this should be the case or not.
For what it's worth, this behavior is not just in the beta, but also in 1.7.3.
In the case of your example, I think I would add the em space as an end character in the initial words setting. That is, unless your example was just simplified for the sake of demonstration. But I do notice that one can use both the max word count and end characters together, which is nice. Further, from a quick test, it seems you can use regular expressions in the end characters field, which rather opens up the possibilities. I had not noticed that before.

In one of the staff posts (but I think not any of those in the topics already linked to), I vaguely remember something being said about the native format already using compression algorithms that, while not producing the smallest possible file sizes, were close to the best available algorithms in that respect & offered a better balance between file size reduction & computational resources needed to compress or decompress the data.
Overall, I have the impression that everything was designed to maximize responsiveness while minimizing the computational load on the system, so even old low end systems like my iMac don't bog down so badly that it is impractical to work on large projects with them.

DAM is Digital Asset Management so a DAW could work Audio and MIDI files held by a real DAM, but could only be used to record me swearing while I work on difficult files with Affinity's products.

An actually useful DAM would also take into consideration the files generated by and used by a DAW (plus all the varied other media generators), and if it doesn't then it will be a waste of cash and disk space. I really don't want a proprietary file format either, xml.

A_B_C, perhaps you can compress it further outside the app (like in WinRAR, or with backup software).  That won't significantly compress it, but could help.
I would be comfortable with WinRAR, but Serif would have the tools to determine what data can be safely removed (for compression) and later completely recovered if needed.  (Not an easy design task)  More than likely, though, if they added some compression option, it would be at least partially destructive.

I’ve been using Logic since the days it was still developed by Emagic, so I consistently confound DAMs and DAWs … 

A DAM does not have to support that but it is a desirable feature, one that different apps support in different (& not always compatible) ways. Accordingly, the staff have mentioned that this is something they would like to support in AP for RAW files, like by reading & perhaps writing sidecar files. But that does not really address the overall issue of the size of native format files vs. what features an archival format would have to give up to implement exporting to it.

Nonetheless, the file sizes are still too large. I appreciate the loading speed and the unrivalled snappiness of Affinity Photo, but as long as we can’t create a reasonably small .aphoto file for archival purposes, the file format remains cumbersome to work with in a long-term perspective. This is a real issue that cannot be discussed away, in my opinion – as well as in my experience (from which my opinion is derived, obviously). What about an option of exporting to some kind of .afarchive format, for instance? 

Hi bboysupaman,
please have a look at my video linked below (Clipping_vs_Masking.mov).
In (A.) the pink rectangle (or rather square) gets clipped to the boundaries (path) of the blue triangle, and this is done by making the rectangle a child of the triangle in the layers list. This is called "layer clipping".
In (B.) the rectangle acts as a mask applied to the triangle, and this is done by dragging the thumbnail of the rectangle directly onto the thumbnail of the triangle in the layers list. (Note the differences between the blue highlight bars appearing while the list entries are dragged to their respective positions.) Now it is not the rectangle that gets clipped to the boundaries of the triangle, but the rectangle clips (or cuts) parts of the triangle. This is called "creating a vector mask".
Hope you get the difference …
Kind regards, Alex 
 

Clipping_vs_Masking.mov  

 

Status: Beta
Purpose: Stability and General Testing
Requirements: Purchased Affinity Publisher
Mac App Store: Not submitted
Download: Download
Auto-update: Not Available
---
Hi,
We are pleased to announce that a new Customer Beta of Affinity Publisher (1.8.0.535) is now available as a download from the link above.
As this is a 'Stability and General Testing' beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity where you may be adversely affected by the application failing, including the total loss of any documents. 
We hope you enjoy the beta, and as always, if you've got any problems installing or running up, please don't hesitate to post in this thread. 
Any problems actually using this version please make a new topic in this forum and we'll get back to you as soon as we can. Please feel free to leave general suggestions and comments in the Discussion Forum. 
Many thanks for your continued feedback.
---
Fixes and Updates
General
Fix for crash on startup when specific (broken) fonts are installed
Embedded Assets imported from opened files aren't always visible initially
Fixed sporadic crash switching from the Text Flow Tool to the Move Tool
Prevented opening of multiple copies of placed linked documents
Fix for documents not auto-updating when edited from inside the application
(Mac) Fixed crash Adding Pages from File
Page Management
Master Page text  could be duplicated when migrating masters
IME panel now available in detached Master Text Frames
IDML Import
Sporadic crash opening IDML with Drop Cap paragraph styles.
Use document profile when IDML contains an image profile of 'None'
Text Variables converted to plain text when importing IDML
Text
(Mac) Fix for crashing in the Text Style Editor (hopefully!)
Improved Title Exceptions granularity to never change certain words
Fixed text drag drop for Master Page text frames
Improved adjustment of last Table Row height / Column width 
Indexes
Words containing index marks could not always be found
Preflight
Added 'Warning' state to preflight status indicator
Additional Hyperlink checks
Overflow text check sometimes wasn't reported if the page frame was overflowing but the master frame wasn't
Ignore small images for non-proportional scaling warning
Export
Fixed PSD Export of Master Page content
Linked sRGB document not printing correctly when placed in a greyscale document
Updated Help and Translations
---
To be notified about all future Mac beta updates, please follow this notification thread 
To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this thread

Yes, I believe all problems described in this thread are solved now. Thank you again. There are a few others, but I created new threads for these. And these were already reported to the development team by @Gabe … 

Interesting usage of a Coolscan V ED, although I had used this Nikon scanner a lot in past times, I never had this FH-G1medical devices adapter for it, instead just the common slide and film adapters.