ReinhardK

For me publishing is all about typography and setting beautiful text, whether that's artistic display type or vast amounts of body text. Here are some things I'd like to see Publisher get at some point (but maybe it's just me so I'm interested in people's comments):
1. Font info: In the Font selector show as much information about each font as practical (ideally let the user configure which attributes are shown), and provide a "get info" function to display all available details. Attributes of interest would include licensing flags (embeddable, etc.) existence of Kerning pairs, OpenType features of interest, western language support, CJKV support, etc.
2. Basic Font management: I'd like to be able to organize fonts into groups (potentially having one font in multiple groups). I'd like to be able to attach some notes text to a font that would be viewable as a tooltip say, or an attribute in the font info described above.
3. Optical Kerning support: I've always been a fan of Optical Kerning in InDesign as it eliminates a significant problem when exploring for interesting and special purpose fonts, and the ability to leverage the insane number of free fonts (of wildly varying quantity of course) that exist today, some/many/most/virtually all of which do not include kerning pairs. I suspect many font designers take the attitude that "kerning is a pain in the butt and people can just turn on optical kerning in InDesign so really there's no problem if you don't do the work to create them". In playing with Publisher I've been disappointed to find out just how many fonts I like will be problematic in Publisher due to lack of kerning support. The Affinity response so far is:
"We provide kerning based on tables in the font file. As these are pretty well supported by fonts, doing anything more isn't a priority at the moment."
( https://forum.affinity.serif.com/index.php?/topic/65653-tooltip-fix-and-optical-margin-align/&tab=comments#comment-342380 )
which is disappointing. I hope they'll consider it in the future.

hi, could you please add support for X-Rite Colorchecker Passport?

it was initially asked in this thread:

thank you,
Reinhard

hi, could you please add support for X-Rite Colorchecker Passport?

it was initially asked in this thread:

thank you,
Reinhard

hi, could you please add support for X-Rite Colorchecker Passport?

it was initially asked in this thread:

thank you,
Reinhard

Any news on this topic? This is a deal breaker for me if I cannot use Color Checker Passport with Affinity Photo - I mean come on, why are we stuck with using Photoshop, it's 2018! Please Affinity... free us from the bondage.

@Tick and others in this thread
Welcome to the Serif Affinity forums.
I can see that this is disappointing that we have not managed to integrate with the Colorchecker Passport. X-Rite have chosen to bundle us with their hardware, knowing this to be the case, but I would hope that the programmers will address this thread soon, or make a clear suggestion how best to proceed.
@James Ritson can you shed any light on this thread?

Importing, using/moving/rotating/scaling, rendering and rastering .obj files (and in general 3D objects created in Maya or similar). This's the only real reason I can't leave Photoshop behind in favor of AffinityPhoto as of now. Thanks.

I want to be able to snap control handles to any object or to the grid. It would be great, if those control handles act the same as every other object when it comes to snapping.
That way, I could draw very precise curves, because I can simply lay out helping objects to define spaces and specific angles to snap to with the frontal handles of a node.
 
See the screenshot. 
It would be nice if that blue control handle of the selected node would snap to the red rectangle.

I'm using Affinity Designer to create SVG icons for a website. And I'm using PostCSS and the plugin "postcss-inline-svg" to use those SVG files and apply CSS to them.
 
The problem is, that Affinity applies background colors like this:
<path d="..." style="fill: #123456;"/> The style attribute has the highest priority in CSS though. That means I can't apply extra CSS rules to it. If I remove the style attribute or replace it with this:
<path d="..." fill="#123456"/> ...it works fine.
 
 
Can you add an option to use `fill="#123456"` instead of `style="fill: #123456;"` when exporting SVG? That'd be great.
Currently I have to do it manually.
 
Thank you.

Hey fredalva,
Welcome to the Affinity Forums :)

I've seen this requested a few times and think it's a great idea but I'm not aware of any plans to implement this. I've passed this over to the development team. Thanks!

Can speed website design build by adding export as html5/css3.Something like export kit running on photoshop.

Also it would be great to have ArionFX or similar plugin on a live layer, so it could be used non-destructively.
Is there any workaround for that? 

+1 for ArionFX in 32 bit mode - it would be great to have that option.

Hi,
it seems to be a problem with this beta of Photo. All filters of Nik Collection work fine with a 16 bits image. Its correct with the mac beta 1.5.0.10 and under Windows, its correct with other bitmap editors like Photoshop CS6.
 

 
ColorEfex with the Mac beta version.

Just downloaded the beta and I was wondering what plugins will work? Also will any Photoshop Extensions work?

This is great stuff! Two questions. 
1. With the exr workflow, will you be supporting exr multichannel files? 
2. How do you get on the beta? 
 
Cheers. 

+1

+1 for me as well, but guys i don't want infinity designer team to be limited by what the market already offers.
please be as creative as you want, bring what non has done.
create a tracing tool that when we look at it we should say "this is how tracing should have been" and please let us now approximately when you guys are coming up with such an option because it's a critical functionality for many of us i think.