grunnvms

Same with me, no more problems !

Google has introduced JPEGLI, a new better type of JPEG that seems to be compatible with existing JPEG decoders. It seems to improve the quality of the JPEG images, and at the same time give a 35% better compression. It's also 10 bit, instead of 8 bit.
It's an open source library, so Serif could use it without license problems.
Could it be useful to implement JPEGLI in Affinity Photo etc. ?

Google has introduced JPEGLI, a new better type of JPEG that seems to be compatible with existing JPEG decoders. It seems to improve the quality of the JPEG images, and at the same time give a 35% better compression. It's also 10 bit, instead of 8 bit.
It's an open source library, so Serif could use it without license problems.
Could it be useful to implement JPEGLI in Affinity Photo etc. ?

Google has introduced JPEGLI, a new better type of JPEG that seems to be compatible with existing JPEG decoders. It seems to improve the quality of the JPEG images, and at the same time give a 35% better compression. It's also 10 bit, instead of 8 bit.
It's an open source library, so Serif could use it without license problems.
Could it be useful to implement JPEGLI in Affinity Photo etc. ?

I agree. Just like pdf, Open Document Format is an official ISO standard, while DocX is a propiarty standard. In fact, you can set MS Word to produce .odt files as standard. Governments may require Open Office documents as standard form.

I agree. Just like pdf, Open Document Format is an official ISO standard, while DocX is a propiarty standard. In fact, you can set MS Word to produce .odt files as standard. Governments may require Open Office documents as standard form.

I agree. Just like pdf, Open Document Format is an official ISO standard, while DocX is a propiarty standard. In fact, you can set MS Word to produce .odt files as standard. Governments may require Open Office documents as standard form.

Hi Walt,
No problem.
These are the three files, and I made no adjustments in Affinity Photo to make them 1:1 comparable. 
Affinity test.afphoto Affinity test AP.tiff Affinity test CO.tif

I've added all the metric sizes and more inch sizes as well, so now I have a complete list of paper sizes. 

I've added all the metric sizes and more inch sizes as well, so now I have a complete list of paper sizes. 

Every A size is rounded to the next millimeter, so 148,5 mm is wrong.

Yes, but then the ratio differs. 210/300 = 0,7 and 150/210 = 0,714
The whole idea of the A, B, C, and even D series paper is that the ratio between the sides is always the same with every sheet size.

The A0 sheet of paper is the base, its size is 841 x 1189 mm. There are 16 sheets of A4 in one sheet of A0, so the short size of an A4 is in theory 841/4 = 210,25 mm, rounded down to 210 mm, and the long side is 1189/4 = 297,25 mm, rounded down to 297 mm. Really not that difficult. 

Every A size is rounded to the next millimeter, so 148,5 mm is wrong.

Actually, many people care!  if you want to be able to resize a design/publications etc and keep the same ratio, then it makes perfect sense! 
"This ratio has the unique property that when cut or folded in half widthways, the halves also have the same aspect ratio. Each ISO paper size is one half of the area of the next larger size in the same series.": https://en.wikipedia.org/wiki/ISO_216
 

Exactly, that is the problem. The metric paper sizes are close to, but not the same as the inch paper sizes. 

That's a long time ago  😁
I think the problem was due to fonts. I'm at 1.10 now, no problems what so ever.
Thanks for all your work !!

You did not state how much memory your systems has, and how much Designer is using. It may well be that your system is swapping to disk because it doesn't have enough RAM. Adding more RAM may help, you can never have too much RAM.

You had that from me as well.
So after I send you all that information, I copied the font files from my personal directories to the standard windows font directory (install for all users), removed the registry entries for those personal fonts, and deleted them in the personal directories. I then rebuilt the font cache.
After this the standard 1.8 photo worked fine.

No, I don't.
So far I did the following:
I selected all fonts in the C:\Users\<username>\AppData\Local\Microsoft\Windows\Fonts\ directory, and then right-clicked on "install for all users". With the registry editor , I removed all font entries (except default of course) from “HKCU\Software\Microsoft\Windows NT\CurrentVersion\Fonts”. Rebooted the PC. Deleted all fonts in the C:\Users\<username>\AppData\Local\Microsoft\Windows\Fonts\ directory. Now all the fonts are where they belong.
Next step was to rebuild the font cache.
With services.msc , stop and disable the "Windows Font Cache Service" , and the "Windows Presentation Foundation Font Cache 3.0.0.0".  (right click - properties) Reboot the PC Make sure you can see Hidden Files and Folders in Explorer ! Go to C:\Windows\ServiceProfiles\LocalService\AppData\Local Delete all .dat files starting with Fontcache Open the Fontcache directory Delete everything in that directory, including the Fonts directory. With services.msc , set the start property of the  "Windows Font Cache Service" to automatic and start the service. With services.msc , set the start property of the "Windows Presentation Foundation Font Cache 3.0.0.0" to manual. There's only one mystery left.
In C:\Users\<username>\AppData\Local\ there is a fontconfig directory, with a cache directory, and all kind of cache files. Haven't figured out what they are used for.

I also got the "setup failed" message, and I immediately had a hunch what the problem was, since I'm familiar with the same problem with LibreOffice.
After the de-installation of the old version of Publisher, the directory Program Files\Affinity\Publisher Public Beta is left in a kind of locked state.
You will have to reboot the PC, and then the directory is gone (or perhaps unlocked, didn't check).