Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

Dave Harris

  • Posts

  • Joined

  • Last visited

About Dave Harris

Profile Information

  • Gender
  • Location
    : Nottingham, UK
  • Member Title
    Bright-eyed and fluffy

Recent Profile Visitors

4,725 profile views
  1. As it happens, we do currently support simple kern pairs in the 'kern' table, but only the cross-platform version 0 variant. Optima uses version 1, which is Apple-specific. We'll add support for that in a future release.
  2. Have you looked at Languages section in the Character panel? The Typography script and Typography language fields? Do they not work for you?
  3. The reason for converting to capitals at draw time is so it can be switched on or off by text styles. For example, you might want a header style to be in ALL CAPS. Text styles shouldn't change the underlying text. It shouldn't cause any problems because OpenType features are applied to the ALL CAPS representation, and not to the underlying characters. As others have said, if you do want to change the underlying characters you can use the menu options that do that. It makes no difference to the result, because both methods use the same capitals conversion. (Which in this case maps U+00DF to U+0053 U+0053 and not to U+1E9E.)
  4. Actually, Affinity will apply the stylistic set after converting to capitals. The issue is that the capital conversion does not produce U+1E9E. It produces a pair of S (U+0053) instead. The stylistic set does not affect these. It's unfortunate that this result is not what you want, but I'm not convinced that Affinity is doing anything wrong. The FAQ you cite confirms that the pair-of-S conversion is still the Unicode default, and other apps also use it. That's probably because so many fonts don't define U+1E9E, and capitalisation is not font-specific. If you know your font has a good definition of U+1E9E, you need to put it in manually.
  5. Affinity apps do support Device N colour spaces for vector gradients. I've attached an example file that has a gradient between two spots, and between a spot and a process colour. I've also attached the exported PDF/X-1a that has the Device N shadings. I made this with 1.9.1, but the support has been there for a while. It does have to be a vector gradient with the fill tool, and not a gradient overlay filter effect or other raster gradient. 2.afpub 2.pdf
  6. There is a global option to scale strokes with object. See my post above on June 27 2018.
  7. You can use Edit > Defaults > Save to make the current defaults apply to new documents.
  8. It's stored with the rest of the image data in the Affinity document. Our file format isn't documented and shouldn't be a concern of other apps. It should just mean that importing a PDF and then exporting it repeatedly won't degrade the image.
  9. Affinity will store the compressed data from the PDF in that case, and will only recompress if something is done to the image.
  10. The default autocorrect includes dash dash => en-dash. This is less likely to trigger by accident than dash => en-dash. It looks like it is trying to do en-dash dash => em-dash, but it doesn't work well partly because the autocorrect doesn't kick in until you type a space, and then the space breaks up the pattern. It should have dash dash dash => em-dash instead.
  11. Can you upload a document where they are set wrong, so we can see what is happening and fix it?
  12. You can set the text background colour from the Character panel. It's next to the Font style and colour.
  13. PDFLib used to support it, but decided to stop doing so in recent versions. I've not been able to convince them that it is needed.
  14. Thanks. I had actually been testing on an older version,, where it works. It does crash as you describe on So it is a relatively new regression. I've logged it to be fixed.
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.