Larry Fjeldstrom

Thanks for your pointing out that the issue revolves around the "NEXT" part of the style, which is the case, but I still am wondering why hitting "BACKSPACE" when the cursor is at the first of the second paragraph fails to delete the carriage return at the end of the first paragraph. The only way to get rid of the carriage return is to position the cursor at the end of the last line of the first paragraph and hit the "DELETE" key. Then the carriage return goes away. That is odd behavior if you ask me.

After typing in a paragraph, and starting a new line, if I type the BACKSPACE key, the cursor does not go to the end of the last line of the paragraph above. Instead the cursor stays where it is, and the paragraph that was below it magically switches to a different text style. If I hit backspace again, the lower paragraph returns to its original style, but the cusror stays at the beginning of the lower paragraph. My only workaround is to hold down the SHIFT key and arrow back to the end of the upper paragraph then hit DELETE. It works, but is a strange workaround if you ask me. I've used PUBLISHER V1 with no issues like this, but V2 has the issue, but I am not sure what sub-version this behavior began with. Has anyone else encountered this, or am I just in my own private world?

Full Specs: (Is this wnat you need?) OS Name Microsoft Windows 11 Pro Version 10.0.22631 Build 22631 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name LARRY-TABLET System Manufacturer Microsoft Corporation System Model Surface Book 2 System Type x64-based PC System SKU Surface_Book_1793 Processor Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz, 2112 Mhz, 4 Core(s), 8 Logical Processor(s) BIOS Version/Date Microsoft Corporation 394.779.768, 2015-08-11 SMBIOS Version 3.3 Embedded Controller Version 255.255 BIOS Mode UEFI BaseBoard Manufacturer Microsoft Corporation BaseBoard Product Surface Book 2 BaseBoard Version Not Available Platform Role Slate Secure Boot State On PCR7 Configuration Elevation Required to View Windows Directory C:\WINDOWS System Directory C:\WINDOWS\system32 Boot Device \Device\HarddiskVolume1 Locale United States Hardware Abstraction Layer Version = "10.0.22621.2506" Username FJELDSTROM\larry Time Zone Mountain Summer Time Installed Physical Memory (RAM) 16.0 GB Total Physical Memory 15.9 GB Available Physical Memory 3.67 GB Total Virtual Memory 24.2 GB Available Virtual Memory 2.92 GB Page File Space 8.29 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualisation-based security Not enabled Windows Defender Application Control policy Enforced Windows Defender Application Control user mode policy Off Device Encryption Support Elevation Required to View Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions Yes Hyper-V - Virtualisation Enabled in Firmware Yes Hyper-V - Data Execution Protection Yes

Windows 11 PC Laptop Affinity v2.4.2 As shown below, when awakening from sleep, only parts of the window get redrawn. I haven't noticed this before, but the occasion may have happened when the window was hidden. An example would be when I hover over parts of the menu when this has occurred. that part of the menu does redraw, and stays redrawn. when I hover over the minimize "-" icon, and then restore it to full size, everything comes back in its full "glory". Somehow the coders forgot to put in the code for the state "Recovering from sleep mode" in this version. Easily done. I'm a coder myself! The work-around is simply to minimize and then restore. Works every time, but makes Affinity look bad... ESPECIALLY with your new "partner" CANVA peering over your shoulders!!!

Hi Mike, I changed the name of the folder as you suggested, but still, en_CA does not appear on the language list after doing that. I keep wondering if there is any other setting that may have an influence on setting the language that I may have overlooked, but from what I can read, the instructions on importing a new language dictionary are very straight forward. Makes me feel inept. I'm comfortable with all things computer. I have a Comp Sci degree, but little things like this can bowl me over! Back to my drawing board I guess. -Larry

No, I don't have V1 installed. My PC computer (Windows 11 PRO) had to be wiped to factory state, so there is no V1 around. The .dic file is small, so I'll just attach it. The directory is C:\ProgramData\Affinity\Common\2.0\Dictionaries\en-CA I must have missed something small. Those are the peskiest things to find! -Larry en_CA.dic

I had to wipe my computer a while back. Now I have lost my "en_CA" language files. I have done all the above. Changed the directory, verified that I had the right files. The .AFF file is slightly different as follows: # 2024-01-29 (Marco A.G.Pinto) # - Fix: apostrophe handling, by adding: WORDCHARS 0123456789’ to the .aff. # SET UTF-8 TRY esianrtolcdugmphbyfvkwzESIANRTOLCDUGMPHBYFVKWZ' ICONV 1 ICONV ’ ' NOSUGGEST ! This difference is in a comment, at least I think that a leading "#" indicates a comment, and I think that blank lines are ignored. When i select the directory and hit close in the tools/additional language... selected, Affinity tells me to restart, and I do. Unfortunately if I go to the character panel and click on the Language selection dropdown, I see: No "English (Canada)" option. 😞 This is annoying. I did successfully make en_CA work. I installed it with V1. I didn't need to do it for V2, but now that I reinstalled Affinity Universal, again on the freshly wiped computer, I can't get it to work. Strange problem. I need to spend my time doing productive work... not fighting with language issues. Can anyone toss a rope to this drowning man?

I suspect that GREP styles are complex to implement from the position of the programmers at Affinity. When a user types in something into a body of text, a Grep style will automatically make changes happen. This can be very disconcerting during the process of entering Grep triggering events before other triggers have been entered. InDesign gets around this by allowing users to see the text in their story editor. The story editor disregards all styles letting you see all the Grep triggering characters. When I thought deeper into this I came upon an interesting solution that the Affinity programmers could consider: introduce a command which would toggle Grep styles on and off so that the Grep triggers would be visible and can be edited. I know that this is likely of no interest to many users that don't use or care about Grep Styles. I'm hoping that Affinity programmers that are interested in Grep Styles will read this. Implimenting the InDesign Story Editor may be a copyrite infringment in Adobe's eyes. The toggling on/off of Grep Styles would be functionally different from Adobe, and is actually simpler to impliment. I'm hoping that this would give the hope of implimenting Grep Styles in Affinity. I have a background in programming, and keep thinking of the issues that the Affinity development team must be facing. Percentage wise, Grep Styles is a minority component but for the users that love Grep Styles, it is a game changer preventing them from switching from InDesign to Affinity. That may be a significant growth area for Affinity's user base. Hopefully the people adjudicating the posts would bring this to the attention of the people at Affinity with the interest of Grep Styles.

Thanks so much Paul. I missed the shortcut for Show Text Ruler. It was staring right at me, and yet I missed it. I appreciate your gentle correction of my "rant". I now use <Ctrl>R for Rulers and <Ctrl><Shift>R for Text Rulers. Works great. 😃

I would like there to be a keyboard shortcut that mimics the action of the "T" shortcut. What I mean is with "T" as an example T toggles between TEXT, TABLE, and ARTISTIC TEXT Wouldn't it be great if <control>R toggled between show: MAIN RULER only, TEXT RULER only, BOTH RULERS , and NO RULERS I like the toggling concept, as the R alliteration is easy to remember when associated with Rulers. I'm hoping that Affinity software designers would agree. It would be a handy shortcut for most of us!

I tried to add an SVG image to my V2 Publisher assets. It would not add to the assets at all. No error message. No crash. Just silently refused to add. I don't know if this is a one of situation, or is this a known bug? Any suggestions? I tried to add by dragging onto the assets panel as well as the "Add from selection" method. Neither works.

Hobbyists will more likely not use GREP styles, nor would they possibly understand how to use one. I regularly have documents that rely on "massaging" database generated text that comes in plain text. Back in my InDesign days I didn't even need to think about editing the document to massage the text. Now for EVERY document I get this way (monthly) I have to do five Find/Replace operations, manually typing in the grep commands for each one. It is a huge time waster! I always have to carefully check to see that I have typed in the expression correctly. The end result is the same as when I did things in InDesign, but my productivity has gone down big time. Affinity is definitely the logical replacement for InDesign. Do I regret switching to Affinity? Not at all!!! I love using Affinity. I just wish that grep styles would be implemented, seeing that the first part of the issue is already implemented - mainly GREP. PLEASE PLEASE... Serif... Go the rest of the way and implement GREP styles. Those of us who would benefit from this improvement will rise up and call you blessed!

I've been thinking that the way Affinity handles producing templates is a bit awkward. In InDesign (forgive me for saying that name!) when you save a document, you can specify template from a dropdown under filetype. Somehow that makes more logical sense than using EXPORT as TEMPLATE. When doing Export as Template, it shows the filetype as "Affinity files" with no other option. I can live with this, but it would seem that saving a file as a template would seem more logical, and Affinity could handle the internal logic to save it as a template and automatically save the file with the aftemplate file extension.

You're preachin' to the choir here. Just hope Affinity joins the choir!

I couldn't agree more with all the grep-style proponents. The nice thing about a grep style is that it is non-destructive to the text. Using grep on its own forces the text itself to be modified. If I want to change the style of a body of text, I have to start from scratch if I use a replacement function in grep. When using a grep style the text remains unchanged. I do a lot of text importing from a database that is not in rich text format. For example something in bold looks like "This is in |bold| today." would become " This is in bold today." Back in InDesign, the text would look like "This is in |bold| today." but the grep style would change the looks. Remove the style and you would see the underlying text with the "|"'s in it. However in Affinity Publisher, once you execute a grep find\replace the underlying bold command ("|") is gone forever. Grep styles would be an answer to my prayers!!!