Search the Community
Showing results for tags 'keyboard layout'.
I use a ANSI (qwerty) keyboard, but type in multiple languages, most of which are european, so I use the EURkey keyboard layout by Steffen Brüntjen to type the language specific letters occasionally needed. As an example to type the german Umlauts (ä,ü,ö) you would use the keybind "CTRL+ALT+A/U/O" or "AltGr + A/U/O". In Affinity Publisher 2, when typing in a Text Frame or Artistic Text Frame, the same keybinds with "CTRL+ALT" do not produce the desired characters, instead no input is read by the program. Using "AltGr" does produce the desired characters in the Text Frames. Interestingly if I go to Edit -> Preferences -> Auto-Correct and type in the "Replace" or "With" input fields, the program behaves as expected with both input methods, meaning that it can read the inputs normally. The problem can repeatedly be reproduced on new files. Technical details: Windows 10 Home 64 bit, Version 21H1 OS build 19043.1526 Ryzen 5 5600X processor 16 GB RAM Radeon RX 6800 XT Graphics card Issue persists with and without hardware acceleration enabled No relevant background software that may intercept the keystrokes other than the OS Recipe: Have ANSI (qwerty) Keyboard (Issue supposedly appears on other keyboards too) Have EURkey keyboard layout installed and selected Open Affinity Publisher 2 Create new Project Create a text or artistitc text frame Type in it Try to insert special characters with the CTRL+ALT+Character binding Unverified personal assumtions regarding the issue: The only other program where I have seen similar behavior in the past was in Joplin, a notetaking software. In there the issue existed because the keybindings were already preoccupied by the program, and had to be unbound in the settings. After unbinding it worked as intended. Since in Affinity Publisher 2 only one of the relevant keybindings seems to be preoccupied with another keybind ( CTRL+ALT+SHIFT+S for export), this solution does not work here. However my assumption is that the program somehow blocks the keybind because it reads some of the input. Since using AltGr keybinds works, my assumption is that the issue is the using of the CTRL key on the keyboard to switch into the mode in which you can see the distances of text fields to their surroundings (for lack of a more specific term). A "fix" could consist of either making it so that the keybinds work on EURKey again (evaluating how realistic that is is beyond my technical skills), or giving us the option to bind this control mode in the settings to some other key, which might also work. I'm of course willing to elaborate should further information help on my part. I know this is a bit of a nieche issue, but it seems like unwanted behavior and as such it should qualify as a bug. I asked about possible ways to fix it in the Support & Questions part of the forums and was advised to specify it as a bugreport. Thank you for your time.
I am pretty new to Affinity Publisher 2, but after getting a recommendation from a friend I decided to give it a try and am currently testing out the 30 day trial to see if it works for me. For the most part, I really like how intuitive the software seems to be, but there is one dealbreaker issue that I have not found a workaround for so far: (I assume) some of the keyboard shortcuts of the program block essential keyboard shortcuts used in my keyboard layout, making these impossible to use. To explain in a bit more detail, I write on a iso keyboard, but regularly have to write multilingual texts (usually german or english, occasionally other european languages). The best way to do so for me has been using the EURkey keyboard layout, which maps a bunch of european characters onto the ISO keyboard. While using Affinity Publisher 2, these characters do not get printed and as a result, I have to essentially write and more importantly edit text in external programs and copy it over. As an example for german, the letters Ä,Ü,Ö as well as ß are all typed by using CTRL + ALT + (A/U/O/S). If you add shift to it, they are printed uppercase. In almost every software I use, this works without issue. The only software I have so far encountered where it doesn't work is Joplin (a notetaking software), which blocks the CTRL+ALT+S keybind. In that software, I could find the keybind in the programs settings, unbind it, and use the software as intended. Naturally I tried to do something similar in Affinity Publisher 2 by going to Edit -> Preferences -> Shortcuts and looking for any of these keybinds being occupied. I don't find any of these keybinds in there and if I add an already occupied keybinding (for example CTRL+A for select all), I get a warning that this keybind is now double bound, but the same does not happen to the EURkey keybinds, leading me to believe the sofware occupies/blocks these keybinds in some other way that I have yet to find a way to disable. My question therefore is if there is a way I can regain the ability to use EURkey keyboard layout keybinds in Affinity Publisher 2? Either by unbinding them if they are occupied by some other keybind or by fixing them in some other way? As it stands, this is unfortunately a dealbreaker for me that would make me decide against buying the software once my trial period is over, which is a shame, because I really like what I have seen so far, but the use of EURkey (or an equivalent other solution that adds the same functionality to Publisher 2) is non negotiable for the type of content I intend to edit. I am using the Desktop Publisher 2 software on Windows 10. I thank anyone trying to help for their time.
Note: The following issue applies specifically to a German ISO keyboard layout (and maybe only the German version of Publisher). In Publisher, the key command for “select next” is ⌥ ⌘ ] and for “select previous” it’s ⌥ ⌘ [ For “move one forward” (or whatever the phrase may be in English) it’s ⌘ ] and “move one backward” it’s ⌘ [ Now here’s the catch: on a German keyboard, [ is typed as ⌥ 5 and ] is ⌥ 6. So, in order to type ⌥ ⌘ ] I’d have to type ⌥ ⌘ ⌥ 6 which obviously can’t work. Effectively, the “select next/previous” shortcuts work, the “move one forward/backward” shortcuts don’t.
I am a affinity photo user in MAC & I can't write bengali properly with MAC Bengali QWERTY keyboard Please help me. thank you Anirban Palchowdhury