MikeTO Posted September 22, 2023 Posted September 22, 2023 (edited) This is really unimportant, I don't think many people are customizing filler text and if they do it's just for one language. But... Settings > Filler Text has a Language list just like AutoCorrect, Abbreviations, and Title Exceptions except it doesn't work the same way for English. Although a number of English variations are listed, they all do the same thing. i.e., setting custom filler text for English UK sets it for all variations of English and changing the Language from one English to another doesn't change what's displayed in the text field below or inserted via filler text. I assume the same Language list was just re-used rather than creating a shorter one specifically for filler text. Filler Text settings are also document-specific, they're not global settings like the rest of settings. This reminds me of the above/below for cross-references in the 2.1 beta that was briefly stored in Settings. If filler text is doc specific then maybe it shouldn't be in Settings either and instead be accessed via a command like Text > Filler Text > Edit... Also, you can edit the filler text without a document open but you can't Save as Default or Revert to Default which is odd since those set global settings. Help should also note that Save as Default, Revert to Default, and Factory Reset are all language specific. Thanks Screen Recording 2023-09-21 at 9.41.47 PM.mov Edited September 22, 2023 by MikeTO added one more item Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
Staff stokerg Posted September 22, 2023 Staff Posted September 22, 2023 Hi @MikeTO, Thanks for reporting these I'll get them logged with the Developers. MikeTO 1 Quote
Staff Affinity Info Bot Posted December 13, 2023 Staff Posted December 13, 2023 The issue "Custom filler text is applied to all categories of English filler text" (REF: AF-372) has been fixed by the developers in internal build "2.4.0.2185". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.