MikeW

@MikeW,
Thanks for the reply.
I found a solution to my problem.
The solution:
Enter the following formula in Excel.
=IF(NUMBER(A3:A12);SUM(A3:A12);"")
and not instead of the total
I don't know if the formula is translated correctly into English.
The German formula is (=IF(ANZAHL(A3:A12);SUMME(A3:A12);"")
 
Cheers

No, there's no function to hide zeros...
A couple things. One is just to F/R in Excel.
Another is to treat the zeros as blank text using the formula that sums the values. Something like:
=""&VLOOKUP(A3,C:D,2,FALSE)
Adjust as needed for your sum formula. The important bit are the empty quotation marks and the ampersand at the beginning of the formula. I haven't tested against APub.
A note. While Excel can hide zeros, they are still there. Which is why APub is displaying them.

And does the requested "transform embedded fonts into paths" have these features?

"Faucet's Last Bath".
The faucet is fully designed in Affinity Designer, than animated in 2d using Moho Pro and than finished in 3d in Blender.
 
last-bath-marked-720plow-24fps.mp4    
  

I did not suggest extracting the font. I was talking about the client providing the font files to the Affinity user.
And yes, you could download them yourself, but if the client provides them you may have a better shot of having a matching version.

This.
The scripting devs are going to have to dedicate a significant amount of time towards documentation. We can't expect our docs team to document the ins and outs of an API (technically multiple APIs), it's simply not fair or realistic. Besides, we'd have to tell them what to write, which would mean pretty much writing the documentation anyway. Sure, they'll be able to present it in a way that looks good and integrated with the normal app documentation, but the devs are going to have to provide much of the content.
We're planning to use one of the many available documentation tools to do most of actual generation for us. The current favourite is Doxygen, largely because most of us have had at least some exposure to it.
Please remember too that the scripting team sometimes has to do bits of work away from scripting development. As the dev who wrote the DWG/DXF importer (and now exporter - see here 🙂), I tend to be the one tasked with its fixes and improvements. The same goes for Move and Shape Data Entry. Everyone in dev could put in those fixes, but it makes so much more sense if I do them because I'm most familiar with the code and should be able to do the work faster. The members of the scripting team do spend most of their time doing scripting work, but it's not 100%.

I think we have exchanged some thoughts earlier about degree of usefulness of IDML serving as a kind of an exchange format between different layout apps (considering how it is currently implemented e.g. in QXP and VivaDesigner), but I certainly agree with you that these kinds of "incompatibility" concerns are silly.
IMO, speculations of "proprietary" or "nondisclosure" issues related to IDML are equally nonsensical. I am not sure how Adobe handles downgrading of features so that "new", post CS4-features get at some level included, but I have understood that IDML specs basically do not get upgraded because the idea is that layouts saved in IDML format, including ones saved in latest CC versions, can be opened also in CS4. If something is not "understood" by earlier versions, it is just skipped/ignored, .
As for reasons of current non-availability of (over a decade old) IDML specs on Adobe dev network (while IDML tools and cookbook are still available), we can only make guesses, but anyone googling IDML File Format specs gets the needed documentation as second and third find entry on Github and CreativePro (not particularly dark internet)... IDML file format itself is nothing more than zipped XML = plain text, so anybody can see how ID features are expressed in mark up. If Serif can convert that to native Affinity objects there is nothing in the technology that stops them doing it in the other direction. 

It's likely Wishes Pro would have issues in the ME version of InDesign as well in this regard (or the hack for using ME features in a western version of ID). There is no GUI means of accessing these OT Features--though it can be done via scripting. Because a western ID version these ME features are off by default, there isn't an apparent issue in them.
At least all the above to the best of my recollection.

https://stock.adobe.com/images/christmas-blue-background/57437645?prev_url=detail
Shutterstock, etc., also list it.
Even places where similar eps files are located, if there is evident transparency, those eps files are either merely containers having an embedded jpeg or embedded AI file. Just the way it is.
So if the file came from Adobe or another pay-site, it is a commercial product and shouldn't be freely shared. However, if you search the forum, there are samples here where people have uploaded such files that fail in Affinity (and other) applications that open faithfully in AI.
btw, I used Tineye for a reverse image search on the OP's jpeg upload to find sources. Adobe was just the first hit.

QXP 2024 can now export to .idml
Viva Designer can import/open .indd files, and keeps up with changes to the format. The more complicated a design, there will be issues, but it will open.
Neither, like APub, deal with all .idml properties in a 1:1 faithful way with InDesign. Some do better with a particular .idml file than the others and vica versa.

QXP 2024 can now export to .idml
Viva Designer can import/open .indd files, and keeps up with changes to the format. The more complicated a design, there will be issues, but it will open.
Neither, like APub, deal with all .idml properties in a 1:1 faithful way with InDesign. Some do better with a particular .idml file than the others and vica versa.

Frames are not "Affinity Resources", in the same way as computer screens are not Resources for displaying images exported from Affinity Photo or Designer. 
Yup

Can't you first check and see what other people do/are commonly posting here into this "Resources" forum category, is it so difficult to understand? - Mostly (re)usable Affinity software related & based things (reusable brushes, assets, styles, templates ...) created with and for the Affinity products. What you did post here instead (...again irrelevant as often before in other forum sections) doesn't really meet this forum section criteria!
It doesn't matter here whether you use Tesco, Ikea, JYSK or whatever picture frame service to frame your drawings in. It's pretty irrelevant for this Affinity forum section, as others BTW already told you before above! -- So that's the reason why such postings like yours here are removed from this forum section, as it's more section unrelated content fill, similar to and like some unwanted forum spam.

QXP 2024 can now export to .idml
Viva Designer can import/open .indd files, and keeps up with changes to the format. The more complicated a design, there will be issues, but it will open.
Neither, like APub, deal with all .idml properties in a 1:1 faithful way with InDesign. Some do better with a particular .idml file than the others and vica versa.

QXP 2024 can now export to .idml
Viva Designer can import/open .indd files, and keeps up with changes to the format. The more complicated a design, there will be issues, but it will open.
Neither, like APub, deal with all .idml properties in a 1:1 faithful way with InDesign. Some do better with a particular .idml file than the others and vica versa.

This one was covered in table tennis bat rubber and the text on the top plate was also red.

It's only On or Off, as far as I know. But if you really needed to enable/disable it on a more granular basis you could always use a Character Text Style assigned to specific pairs of characters.

It's less work to keep up with the changes once compatible to whatever degree it really is. 
Harder, but not much difference to figuring what needs to be to make .idml compatible as it changes for APub.

A quick one keeping things simple, a few conical gradients etc. Might tidy things up if I decide I like it.
 
 
 
 
 

Decided to do this without blurs again whilst trying to keep it realistic. It made some things trickier but saved the time in not having to set a million blurs. Used AD v2 for the warped text.
 

I did submit this directly and it'll be fixed in the next update.

For me, I needed to Show Rulers, right-click at the top-left Ruler intersection, choose Inches from there, then go into Document Setup, change dpi. Then units can be changed again--dpi, measurement units.
It's a very stupid, maybe even convoluted, process.

I believe the DPI settings that you entered is the reason your images have higher DPI on export. You used the presets. Based on what I read, the application was simply doing what you told it to do. I believe, you do have the ability to change this for your banner requirment.
I downloaded your pdf with the stars graphic each having 148 DPI as described in your setup and successfully exported it to PDF x1a, X3 and 1.7.  with all of the images maintaining thier 148 DPI. None of the images DPI changed because of the settings I used. Is this the result you are looking for? 
 

I have logged this with our developers

@Konrad1  The problem is the Aquire font. Wadda mess.
Multi-mapping is when a glyph is mapped to more than one Unicode code point.
This can quite often cause problems for applications with those fonts.
Adobe strongly recommends against multi-mapping.
Google Fonts does not allow multi-mapping at all in their fonts.
It is a dumb idea to do it.
It appears this free version of the font was created by deleting the extended glyphs,
and then multi-mapping the deleted glyphs code points to the base glyph.
For example the capital A glyph has 14 code points mapped to it.
That is beyond stupid.
And it uses ranges of code points in addition to single code points.
Many applications will choke on that.
This "free" font is basically unusable.
It may work in some situations, but not cross-platform, and not in many applications.
Could not find the commercial version to take a look at it and see if it too is a mess,
but, regardless, I would not trust anything made by this "font designer."