Dan C

Welcome to the Affinity Forums @BenKr!
In Affinity, you can use 'Copy' (CTRL + C) on your source text, then you can use 'Paste Style' (CTRL + Shift + V) on your destination text to copy the style between the 2.
You can also use the 'Style Picker' tool to achieve this without the need for keyboard shortcuts - https://affinity.help/publisher2/English.lproj/index.html?page=pages/Tools/tools_stylePicker.html&title=Style Picker Tool
I hope this helps

However, in V2.2 the 'Add' Geometry option will no longer reset the Bounding Box, even for a Closed Curve object. This has been discussed further recently here -
A feature request for a dedicated 'Reset Bounding Box' option is currently logged with our developers, under consideration for a future version

There's no direct option for this within the Affinity app - however you can copy your Adjustments.propcol file from one system to another to transfer these.
On Windows, these can be found in the following folders:
Affinity Store (MSIX) & Windows Store: %USERPROFILE%\.affinity\Common\2.0\user\
  Affinity Store (EXE) : %appdata%\Affinity\Common\2.0\user\ On macOS, this file is found under:
~/Library/Group Containers/6LVTQB9699.com.seriflabs/v2/user/
I hope this clears things up

Welcome to the Affinity Forums @BenKr!
In Affinity, you can use 'Copy' (CTRL + C) on your source text, then you can use 'Paste Style' (CTRL + Shift + V) on your destination text to copy the style between the 2.
You can also use the 'Style Picker' tool to achieve this without the need for keyboard shortcuts - https://affinity.help/publisher2/English.lproj/index.html?page=pages/Tools/tools_stylePicker.html&title=Style Picker Tool
I hope this helps

Unfortunately in V2.1, our team have found the following issues when exporting to raster (image) formats:
When exporting to a raster format and changing any of the 'Advanced' Export settings, the Matte will now apply with the last set colour (usually white), rather than transparent to the exported image. This is incorrect and should remain as transparent
  After changing the Matte (or having the Matte automatically set as above), the transparent (white circle with a red line) button in the Matte pop-out dialog does not work, meaning you cannot easily return to a transparent matte, without selecting one of the default presets.
  After changing the Matte (or having the Matte automatically set as above), and selecting an Export Preset, the UI does not correctly display the Matte as transparent and instead displays the previously set Matte colour (usually white) - though it does export as transparent. There are 2 known workarounds for these issues currently:
When using the Preset Export settings for these raster formats, the Matte will be correctly set to transparent, and exported as such.
  After changing the Advanced export settings as required, open the Matte dialog and change the drop-down menu to Swatches.
Here, you should see one of the default swatches on the right is 'no fill' (ie transparency). Selecting this 'no fill' swatch should return the Matte to transparent and the UI should reflect this:
  1712596548_2023-05-2411-50-07.mp4.c508454f1942159a3dd13c299a8db311.mp4

This allows the Advanced options to be changed and the Matte to export as transparent, but please do remember the Matte option must be selected last for this workaround to work.
Our team is working to resolve these above listed issues as soon as possible and we thank you for your patience and understanding in the meantime.

Welcome to the Affinity Forums @Underboyleheating 
The following Adobe article should outline this for you - https://helpx.adobe.com/uk/fonts/using/activate-fonts-desktop.html
I hope this helps!

Please find below direct links to the Hunspell dictionaries. To download a file, right click the link and select Save Link As...
(In Safari, select Download Linked File As... but do not select Download Linked File or .txt will be appended to the filename.)
 
af_ZA af_ZA.aff af_ZA.dic hyph_af_ZA.dic an_ES an_ES.aff an_ES.dic ar ar.aff ar.dic be_BY be-official.aff be-official.dic hyph_be_BY.dic bg_BG bg_BG.aff bg_BG.dic hyph_bg_BG.dic bn_BD bn_BD.aff bn_BD.dic bo bo.aff bo.dic br_FR br_FR.aff br_FR.dic bs_BA bs_BA.aff bs_BA.dic ca ca-valencia.aff ca-valencia.dic ca.aff ca.dic hyph_ca.dic cs_CZ cs_CZ.aff cs_CZ.dic hyph_cs_CZ.dic da_DK da_DK.aff da_DK.dic hyph_da_DK.dic de de_AT_frami.aff de_AT_frami.dic hyph_de_AT.dic de_CH_frami.aff de_CH_frami.dic hyph_de_CH.dic de_DE_frami.aff de_DE_frami.dic hyph_de_DE.dic el_GR el_GR.aff el_GR.dic hyph_el_GR.dic en en_AU.aff en_AU.dic en_CA.aff en_CA.dic en_GB.aff en_GB.dic hyph_en_GB.dic en_US.aff en_US.dic hyph_en_US.dic en_ZA.aff en_ZA.dic eo eo.aff eo.dic hyph_eo.dic es es_AR.aff es_AR.dic es_BO.aff es_BO.dic es_CL.aff es_CL.dic es_CO.aff es_CO.dic es_CR.aff es_CR.dic es_CU.aff es_CU.dic es_DO.aff es_DO.dic es_EC.aff es_EC.dic es_ES.aff es_ES.dic hyph_es.dic es_GQ.aff es_GQ.dic es_GT.aff es_GT.dic es_HN.aff es_HN.dic es_MX.aff es_MX.dic es_NI.aff es_NI.dic es_PA.aff es_PA.dic es_PE.aff es_PE.dic es_PH.aff es_PH.dic es_PR.aff es_PR.dic es_PY.aff es_PY.dic es_SV.aff es_SV.dic es_US.aff es_US.dic es_UY.aff es_UY.dic es_VE.aff es_VE.dic et_EE et_EE.aff et_EE.dic hyph_et_EE.dic fr_FR fr.aff fr.dic hyph_fr.dic gd_GB gd_GB.aff gd_GB.dic gl gl_ES.aff gl_ES.dic hyph_gl.dic gu_IN gu_IN.aff gu_IN.dic gug gug.aff gug.dic he_IL he_IL.aff he_IL.dic hi_IN hi_IN.aff hi_IN.dic hr_HR hr_HR.aff hr_HR.dic hyph_hr_HR.dic hu_HU hu_HU.aff hu_HU.dic hyph_hu_HU.dic id id_ID.aff id_ID.dic hyph_id_ID.dic is is.aff is.dic hyph_is.dic it_IT it_IT.aff it_IT.dic hyph_it_IT.dic kmr_Latn kmr_Latn.aff kmr_Latn.dic ko_KR ko_KR.aff ko_KR.dic lo_LA lo_LA.aff lo_LA.dic lt_LT lt.aff lt.dic hyph_lt.dic lv_LV lv_LV.aff lv_LV.dic hyph_lv_LV.dic mn_MN mn_MN.aff mn_MN.dic hyph_mn_MN.dic ne_NP ne_NP.aff ne_NP.dic nl_NL nl_NL.aff nl_NL.dic hyph_nl_NL.dic no nn_NO.aff nn_NO.dic hyph_nn_NO.dic nb_NO.aff nb_NO.dic hyph_nb_NO.dic oc_FR oc_FR.aff oc_FR.dic pl_PL pl_PL.aff pl_PL.dic hyph_pl_PL.dic pt_BR pt_BR.aff pt_BR.dic hyph_pt_BR.dic pt_PT pt_PT.aff pt_PT.dic hyph_pt_PT.dic ro ro_RO.aff ro_RO.dic hyph_ro_RO.dic ru_RU ru_RU.aff ru_RU.dic hyph_ru_RU.dic si_LK si_LK.aff si_LK.dic sk_SK sk_SK.aff sk_SK.dic hyph_sk_SK.dic sl_SL sl_SI.aff sl_SI.dic hyph_sl_SI.dic sq_AL sq_AL.aff sq_AL.dic hyph_sq_AL.dic sr sr-Latn.aff sr-Latn.dic hyph_sr-Latn.dic sr.aff sr.dic hyph_sr.dic sv_FI sv_FI.aff sv_FI.dic hyph_sv.dic sv_SE sv_SE.aff sv_SE.dic hyph_sv.dic sw_TZ sw_TZ.aff sw_TZ.dic te_IN te_IN.aff te_IN.dic hyph_te_IN.dic th_TH th_TH.aff th_TH.dic tr_TR tr_TR.aff tr_TR.dic uk_UA uk_UA.aff uk_UA.dic hyph_uk_UA.dic zu_ZA hyph_zu_ZA.dic

The Affinity apps perform what is called document-to-screen colour profile conversion.
This means that the colour values are translated from their initial document values based on the current display profile.
Other apps do not perform such conversions, so these incorrect colours may only be shown within Affinity.
If you find your apps canvas is not displayed as white, your colours appear incorrectly, or even the applications UI is not rendered as expected, this is usually caused by the colour profile (ICC profile) applied to your display/device.
Colour profiles can be applied automatically by the manufacturer of your display/device or can be manually created using a third party colorimeter for display calibration.
If your Affinity app is showing an off white canvas, or incorrect colours, we recommend changing your display's colour profile to sRGB IEC61966-2.1 to resolve this.
 
For Windows users:
Open Windows Run (Windows Key + R)
  Type colorcpl and click OK
  In the Devices tab, select the current monitor from the Devices dropdown menu and make sure Use my settings for this device is selected.
  If a profile is currently listed:
Select the profile in the list and then click Remove. You will be prompted to confirm, please select Continue.
If no profile is currently listed:
Proceed to the next step
  Click Add... and select sRGB IEC61966-2.1 from the list and click OK. Do not use the 'virtual' sRGB profiles.
The sRGB IEC61966-2.1 profile should now appear in the Profiles associated with this device: section.
  Select the sRGB IEC61966-2.1 profile and click Set as Default Profile to make it the default.
  If you have multiple monitors, please repeat the steps above by selecting your other monitor(s) from the Device dropdown list.
  Close the Colour Management window and restart your Affinity app. Your Colour Management settings should appear similar to the below:

 
For macOS users:
Navigate to Apple > System Settings > Displays
  Select your main device/display from the top of the dialog, if multiple devices are connected
  Change the Colour Profile option to sRGB IEC61966-2.1
  If you have multiple devices, please repeat the steps above by selecting your other monitor(s) at the top of the dialog
  Close the System Settings window and restart your Affinity app. Your display settings should now appear similar to the below:

 
If you have followed the above steps and are still experiencing colour issues in the Affinity apps, please create a new post detailing your problem, the profile(s) you have tried, and include a copy of your Affinity document if this only occurs in one specific file.

I can confirm this is logged as a Feature Request with our development team and not a bug - meaning it will not be given the same priority as reported bugs within the app.
Our development team don't tend to comment on, or provide timescales for features that we may choose to implement in the future, therefore I'm unable to provide any update on this request at this time, our apologies.
If you're working with Print and Bleed, you may want to consider using Canvas' in Affinity Designer for single spreads, or Affinity Publisher for multiple spreads within one file - as these are more designed for bleed publication documents, rather than Artboards in Designer.

Thanks for your report @Intuos5!
I've logged this with our development team as I'd expect Windows to use the same alphabetical ordering as found on macOS - I hope this helps

We have no issue with our customers mentioning and recommending software to others, I appreciate your hesitance here but provided you aren't trying to sell the software or providing a referral link etc then you're welcome to name any software you deem is relevant to the discussion  
 
(apart from Ad**e, the lesser mentioned the better )

Please find below direct links to the Hunspell dictionaries. To download a file, right click the link and select Save Link As...
(In Safari, select Download Linked File As... but do not select Download Linked File or .txt will be appended to the filename.)
 
af_ZA af_ZA.aff af_ZA.dic hyph_af_ZA.dic an_ES an_ES.aff an_ES.dic ar ar.aff ar.dic be_BY be-official.aff be-official.dic hyph_be_BY.dic bg_BG bg_BG.aff bg_BG.dic hyph_bg_BG.dic bn_BD bn_BD.aff bn_BD.dic bo bo.aff bo.dic br_FR br_FR.aff br_FR.dic bs_BA bs_BA.aff bs_BA.dic ca ca-valencia.aff ca-valencia.dic ca.aff ca.dic hyph_ca.dic cs_CZ cs_CZ.aff cs_CZ.dic hyph_cs_CZ.dic da_DK da_DK.aff da_DK.dic hyph_da_DK.dic de de_AT_frami.aff de_AT_frami.dic hyph_de_AT.dic de_CH_frami.aff de_CH_frami.dic hyph_de_CH.dic de_DE_frami.aff de_DE_frami.dic hyph_de_DE.dic el_GR el_GR.aff el_GR.dic hyph_el_GR.dic en en_AU.aff en_AU.dic en_CA.aff en_CA.dic en_GB.aff en_GB.dic hyph_en_GB.dic en_US.aff en_US.dic hyph_en_US.dic en_ZA.aff en_ZA.dic eo eo.aff eo.dic hyph_eo.dic es es_AR.aff es_AR.dic es_BO.aff es_BO.dic es_CL.aff es_CL.dic es_CO.aff es_CO.dic es_CR.aff es_CR.dic es_CU.aff es_CU.dic es_DO.aff es_DO.dic es_EC.aff es_EC.dic es_ES.aff es_ES.dic hyph_es.dic es_GQ.aff es_GQ.dic es_GT.aff es_GT.dic es_HN.aff es_HN.dic es_MX.aff es_MX.dic es_NI.aff es_NI.dic es_PA.aff es_PA.dic es_PE.aff es_PE.dic es_PH.aff es_PH.dic es_PR.aff es_PR.dic es_PY.aff es_PY.dic es_SV.aff es_SV.dic es_US.aff es_US.dic es_UY.aff es_UY.dic es_VE.aff es_VE.dic et_EE et_EE.aff et_EE.dic hyph_et_EE.dic fr_FR fr.aff fr.dic hyph_fr.dic gd_GB gd_GB.aff gd_GB.dic gl gl_ES.aff gl_ES.dic hyph_gl.dic gu_IN gu_IN.aff gu_IN.dic gug gug.aff gug.dic he_IL he_IL.aff he_IL.dic hi_IN hi_IN.aff hi_IN.dic hr_HR hr_HR.aff hr_HR.dic hyph_hr_HR.dic hu_HU hu_HU.aff hu_HU.dic hyph_hu_HU.dic id id_ID.aff id_ID.dic hyph_id_ID.dic is is.aff is.dic hyph_is.dic it_IT it_IT.aff it_IT.dic hyph_it_IT.dic kmr_Latn kmr_Latn.aff kmr_Latn.dic ko_KR ko_KR.aff ko_KR.dic lo_LA lo_LA.aff lo_LA.dic lt_LT lt.aff lt.dic hyph_lt.dic lv_LV lv_LV.aff lv_LV.dic hyph_lv_LV.dic mn_MN mn_MN.aff mn_MN.dic hyph_mn_MN.dic ne_NP ne_NP.aff ne_NP.dic nl_NL nl_NL.aff nl_NL.dic hyph_nl_NL.dic no nn_NO.aff nn_NO.dic hyph_nn_NO.dic nb_NO.aff nb_NO.dic hyph_nb_NO.dic oc_FR oc_FR.aff oc_FR.dic pl_PL pl_PL.aff pl_PL.dic hyph_pl_PL.dic pt_BR pt_BR.aff pt_BR.dic hyph_pt_BR.dic pt_PT pt_PT.aff pt_PT.dic hyph_pt_PT.dic ro ro_RO.aff ro_RO.dic hyph_ro_RO.dic ru_RU ru_RU.aff ru_RU.dic hyph_ru_RU.dic si_LK si_LK.aff si_LK.dic sk_SK sk_SK.aff sk_SK.dic hyph_sk_SK.dic sl_SL sl_SI.aff sl_SI.dic hyph_sl_SI.dic sq_AL sq_AL.aff sq_AL.dic hyph_sq_AL.dic sr sr-Latn.aff sr-Latn.dic hyph_sr-Latn.dic sr.aff sr.dic hyph_sr.dic sv_FI sv_FI.aff sv_FI.dic hyph_sv.dic sv_SE sv_SE.aff sv_SE.dic hyph_sv.dic sw_TZ sw_TZ.aff sw_TZ.dic te_IN te_IN.aff te_IN.dic hyph_te_IN.dic th_TH th_TH.aff th_TH.dic tr_TR tr_TR.aff tr_TR.dic uk_UA uk_UA.aff uk_UA.dic hyph_uk_UA.dic zu_ZA hyph_zu_ZA.dic

Hallo @Nostago,
Willkommen im Affinity-Forum  
Die violette Umrandung, die Sie sehen, sind „Schnappkandidaten“. Um diese auszublenden, öffnen Sie bitte das Schnappmenü und deaktivieren Sie „Schnappkandidaten anzeigen“.

Sie sollten diese nun nicht mehr anzeigen!

Hi Shema,
We currently have no plans for Linux I'm afraid and we cannot support emulation etc.
Lee
 

We have investigated this problem thoroughly, and unfortunately have found it to be intractable due to our application file size and the security that Apple builds into all it’s operating systems.
To support the different hardware Apple now makes, since 1.8.6 we have distributed a Universal Application (compiled for Apple-Silicon and again for Intel based macs) within the same .DMG installation file. These Affinity applications are consequentially almost twice as big as previous, but we have to provide both versions to support all types of current macOS hardware.
It seems the time required by YARA/Gatekeeper anti-virus checking, which occurs when first launching the app, is exponential with file size and therefore this delay out of our control - because we need to serve up a universal app through the mac App Store, and currently provide the same Universal App download from the Affinity Store.
The reason it happens every time you restart your mac is that the YARA/Gatekeeper system may have been improved since last time it checked our application, so it does not “save” the fact our application has already been checked. Other applications are likely much smaller files and so start quicker.
Unfortunately due to the above reasons, we do not currently have an option to reduce this start-up delay as it is intrinsically built into macOS security protocols and not controlled by Affinity directly - though we have informed Apple of this and will continue to monitor this in future macOS updates.
We may investigate an option in the future to provide separate installation files on macOS for each hardware type, from the Affinity Store directly - though we do not have any direct plans for this currently and unfortunately it would not change the behaviour experienced when using the mac App Store version.
Our apologies for any inconveniences caused due to this.

Hi Trev Raymond,
Welcome to the forums  
To edit a mask layer, simply select it in the layers panel. To focus the document only on the mask layer (or any layer for that matter) you can hold the alt key when selecting the layer, see below for a quick GIF showing this and a tutorial video showing a few more uses!
 
 

Hi @PeterB.,
I can confirm this is logged with our development team as a request for a future update, I'll be sure to add your 'vote' to this internally now.
I hope this helps

Hi @AndrewJJP,
Welcome to the Affinity Forums
I can confirm we've received your email regarding the same questions and we'll continue to support you there!
I can see the image that the OP originally included and has since removed - this is the same example image used in the website linked, which was the tutorial the user was following when Photoshop is discussed (https://nabesaka.com/using-iray-canvas-for-depth-of-field-in-daz-studio-3d/).
We sincerely appreciate the help and assistance you provide, both here and in other threads, but please be mindful of the language used - especially to new users as this could easily be construed as a "personal criticism or attack" - however I also understand you wanting to keep the forums a clean and respectful place.
As I understand it, this is simply how the Gaussian Blur is applied to the image. I created a test document with gaussian blur applied to the full image and exported this to JPEG, I then added a Gradient Mask to the Gaussian Blur layer and exported to JPEG once again. In a new document, I opened both images and aligned them, then changed the top layer to the Difference blend mode. This shows the area where the changes begin, which match exactly with the mask applied to the adjustment and therefore I do not see a bug here - unless I've missed something in your report!

Hi @Leigh Creggas,
It sounds as though you are looking for PDF 'fillable forms' - unfortunately this isn't currently a supported feature in Affinity, my apologies.
I'll be sure to add a 'vote' to this feature in our internal development log for you now, as this is something we may add in a future update
In the meantime, you may be able to export the PDF from Affinity and then use an external application to add these 'fillable forms', however I have no personal experience doing this, so hopefully other forum members can offer recommendations!

Hi @vidu3k333,
Thanks for your report - as NotMyFault mentions, this issue is already logged with our developers, so I'll be sure to update the report with them now.
In the meantime, moving the Pixel layer from the 'Layer' container should stop this from happening, then you can return the pixel layer to this location once you've finished editing.
I hope this helps!

Apologies, this is what I'm trying to explain - the K value in Affinity needs to be set based on the conditions the image was taken under.
For example, an image with a blue cast will have been taken in ~5000K conditions, therefore you would set the Affinity slider to 5000K, which would add the warm tone to the image.
The Slider/K value in Affinity is not to indicate the colour temperature being added, you are setting the value that the image was taken under, to 'balance' out the white tones.
I hope this clears things up

Hi @Leigh Creggas,
It sounds as though you are looking for PDF 'fillable forms' - unfortunately this isn't currently a supported feature in Affinity, my apologies.
I'll be sure to add a 'vote' to this feature in our internal development log for you now, as this is something we may add in a future update
In the meantime, you may be able to export the PDF from Affinity and then use an external application to add these 'fillable forms', however I have no personal experience doing this, so hopefully other forum members can offer recommendations!

Hi big smile, 
You can go to Document > Add pages from file
The rest is dependant on how the original document was constructed, but i think you'll find this does everything you need it to do.
Lee

Please find below direct links to the Hunspell dictionaries. To download a file, right click the link and select Save Link As...
(In Safari, select Download Linked File As... but do not select Download Linked File or .txt will be appended to the filename.)
 
af_ZA af_ZA.aff af_ZA.dic hyph_af_ZA.dic an_ES an_ES.aff an_ES.dic ar ar.aff ar.dic be_BY be-official.aff be-official.dic hyph_be_BY.dic bg_BG bg_BG.aff bg_BG.dic hyph_bg_BG.dic bn_BD bn_BD.aff bn_BD.dic bo bo.aff bo.dic br_FR br_FR.aff br_FR.dic bs_BA bs_BA.aff bs_BA.dic ca ca-valencia.aff ca-valencia.dic ca.aff ca.dic hyph_ca.dic cs_CZ cs_CZ.aff cs_CZ.dic hyph_cs_CZ.dic da_DK da_DK.aff da_DK.dic hyph_da_DK.dic de de_AT_frami.aff de_AT_frami.dic hyph_de_AT.dic de_CH_frami.aff de_CH_frami.dic hyph_de_CH.dic de_DE_frami.aff de_DE_frami.dic hyph_de_DE.dic el_GR el_GR.aff el_GR.dic hyph_el_GR.dic en en_AU.aff en_AU.dic en_CA.aff en_CA.dic en_GB.aff en_GB.dic hyph_en_GB.dic en_US.aff en_US.dic hyph_en_US.dic en_ZA.aff en_ZA.dic eo eo.aff eo.dic hyph_eo.dic es es_AR.aff es_AR.dic es_BO.aff es_BO.dic es_CL.aff es_CL.dic es_CO.aff es_CO.dic es_CR.aff es_CR.dic es_CU.aff es_CU.dic es_DO.aff es_DO.dic es_EC.aff es_EC.dic es_ES.aff es_ES.dic hyph_es.dic es_GQ.aff es_GQ.dic es_GT.aff es_GT.dic es_HN.aff es_HN.dic es_MX.aff es_MX.dic es_NI.aff es_NI.dic es_PA.aff es_PA.dic es_PE.aff es_PE.dic es_PH.aff es_PH.dic es_PR.aff es_PR.dic es_PY.aff es_PY.dic es_SV.aff es_SV.dic es_US.aff es_US.dic es_UY.aff es_UY.dic es_VE.aff es_VE.dic et_EE et_EE.aff et_EE.dic hyph_et_EE.dic fr_FR fr.aff fr.dic hyph_fr.dic gd_GB gd_GB.aff gd_GB.dic gl gl_ES.aff gl_ES.dic hyph_gl.dic gu_IN gu_IN.aff gu_IN.dic gug gug.aff gug.dic he_IL he_IL.aff he_IL.dic hi_IN hi_IN.aff hi_IN.dic hr_HR hr_HR.aff hr_HR.dic hyph_hr_HR.dic hu_HU hu_HU.aff hu_HU.dic hyph_hu_HU.dic id id_ID.aff id_ID.dic hyph_id_ID.dic is is.aff is.dic hyph_is.dic it_IT it_IT.aff it_IT.dic hyph_it_IT.dic kmr_Latn kmr_Latn.aff kmr_Latn.dic ko_KR ko_KR.aff ko_KR.dic lo_LA lo_LA.aff lo_LA.dic lt_LT lt.aff lt.dic hyph_lt.dic lv_LV lv_LV.aff lv_LV.dic hyph_lv_LV.dic mn_MN mn_MN.aff mn_MN.dic hyph_mn_MN.dic ne_NP ne_NP.aff ne_NP.dic nl_NL nl_NL.aff nl_NL.dic hyph_nl_NL.dic no nn_NO.aff nn_NO.dic hyph_nn_NO.dic nb_NO.aff nb_NO.dic hyph_nb_NO.dic oc_FR oc_FR.aff oc_FR.dic pl_PL pl_PL.aff pl_PL.dic hyph_pl_PL.dic pt_BR pt_BR.aff pt_BR.dic hyph_pt_BR.dic pt_PT pt_PT.aff pt_PT.dic hyph_pt_PT.dic ro ro_RO.aff ro_RO.dic hyph_ro_RO.dic ru_RU ru_RU.aff ru_RU.dic hyph_ru_RU.dic si_LK si_LK.aff si_LK.dic sk_SK sk_SK.aff sk_SK.dic hyph_sk_SK.dic sl_SL sl_SI.aff sl_SI.dic hyph_sl_SI.dic sq_AL sq_AL.aff sq_AL.dic hyph_sq_AL.dic sr sr-Latn.aff sr-Latn.dic hyph_sr-Latn.dic sr.aff sr.dic hyph_sr.dic sv_FI sv_FI.aff sv_FI.dic hyph_sv.dic sv_SE sv_SE.aff sv_SE.dic hyph_sv.dic sw_TZ sw_TZ.aff sw_TZ.dic te_IN te_IN.aff te_IN.dic hyph_te_IN.dic th_TH th_TH.aff th_TH.dic tr_TR tr_TR.aff tr_TR.dic uk_UA uk_UA.aff uk_UA.dic hyph_uk_UA.dic zu_ZA hyph_zu_ZA.dic

Thanks for your post @LilJ!
There are many existing threads here on the forums regarding Linux support and I understand that at this time, our position has not changed on supporting this OS.
Equally, you are not the first user to suggest a potential crowdfunded route to springboard initial development - 
Although I believe this decision is partly financially motivated (for example the initial & ongoing development costs, retraining our support team for a new OS, rewriting our helpfiles and FAQs, ect), our team have previously confirmed that even with sudo-unlimited funds, we are currently continuing to focus on Affinity for Windows, macOS and iPadOS at this time and are not planning a Linux, or for that matter Android version - so crowdfunding any initial development costs would unfortunately not change this.
We ask for any Affinity on Linux discussions to continue in these previous threads, rather than continuing in new ones, such as the following -
Many thanks for your understanding