keys inaccessible with localized/platform-specific keyboards

<empty comment>

Another similar report:

I have some problems, these are not bugs, but makes work
difficult.

1., I have got trouble with snapping to grids and snapping
to guides.

I have hungarian keyboard, so on main keyboard there is "+"
above "3".
When I try to toggle snapping to grid, it zooms instead of
snapping.

The "\" is on my "Q" key (with Alt Gr), so it is unusable
for snapping.

(I can use # and | to hide grids, but it's not a solution)

I've got similar problems with a Belgian keyboard. The '`' key
does not work, nor do the numeric keypad keys '1' through '4'
and '6' -- but '5' is O.K. Go figure.

Looks similar to: [ 1000334 ] "Ctrl + ^" under Win v0.39 is
not working?!

http://sourceforge.net/tracker/index.php?func=detail&aid=1000334&group_id=93438&atid=604306

On 9/23/05, Daniel Stiefelmaier <email address hidden> wrote:
> Hi!
>
> While i translated the basic tutorial i came across some
things.
>
> Some are caused by KDE, some might be bugs, some are
caused by my german
> keyboard layout.
> As there will be customizable keybindings, some problems
might dissolve
> gracefully... :)
> There should be default keybindings for different
keyboardlayouts then.
>
> Well, here are the trouble makers: :)
>
> - There is no gradient tool if i press ctrl-f1
> - the edit menu should contain the Esc key for unselcting all.
> - alt+klick does not work with kde, its used there. if its
possible, id
> override the kde setting. if not, there should be a second
way to do
> that. Maybe Alt-Gr. (meta?)
> - i cant use ` or shift- ` ... in fact, i need to press
shift to
> create an ` . Hard to press Shift+` if you need shift to
create ` :) so,
> no zooming with that key!
> if we will have localized defaults, id recommend our # / '
key or the
> ä/ö keys for german.
> - rotate slow with shift+[ ] does not work. i need to use
alt-gr+8 or 9
> for [ ]. maybe that causes trouble.

See also this report on Mac OS X:

http://sourceforge.net/mailarchive/message.php?msg_id=13098640

see also
http://sourceforge.net/tracker/index.php?func=detail&aid=1337642&group_id=93438&atid=604306

I don't know if I'm posting to the right thread. I've found a weird bug: Alt-D opened "View" menu (Rissian localization) instead of making a clone. Restart helped.

0.45.1-1, WinXP

From comment #5 in duplicate bug #165881:
> We need to make a different keyboard profile
> for such users perhaps.

Other shortcuts related issues (from duplicates):

* Bug #165881, "Ctrl + ^ under Win v0.39 is not working?!"
Keyboard Shortcut "Ctrl + ^" for exclusive OR (XOR) will not work in Win2k, Win9x but it works fine in Linux.

* Bug #178738, "Path Effects shortcut mixed with Division (Shift+Ctrl+7)"
Opening it from the menu Path > Path Effects works fine but when I hit Shift+Ctrl+7 the only thing I get is a note in statusbar: Select at least 2 paths to perform a boolean operation.

* Bug #181393, "View shortcuts don't work on french keyboard"
Only 5, + and - shortcuts work on the numpad. Only + and - shortcuts work on the 'alphapad'. On the French azerty keyboard, the shift key must be pressed to uses 'alphapad' numbers.

* Bug #266913, "Text's letter spacing fails with localized keyboard layout"
The "Inkscape keyboard and mouse reference" tells me : Alt+> expand line/paragraph by 1 pixel; Shift+Alt+> expand line/paragraph by 10 pixels; Alt+< contract line/paragraph by 1 pixel; Shift+Alt+< contract line/paragraph by 10 pixels
But when I do theese advice, It's like if I was doing : Ctrl+Alt+> make the text object taller by 1 pixel; Shift+Ctrl+Alt+> make the text object taller by 10 pixels; Ctrl+Alt+< make the text object shorter by 1 pixel; Shift+Ctrl+Alt+< make the text object shorter by 10 pixels

* Bug #593031, "Keyboard shortcut for Next Zoom does not work"
The keyboard shortcut Shift+` should change the zoom level to the next in the history. However, it appears to do nothing at all.

Alphapad support for zoom shortcuts committed in the trunk, revision 9690.

Aloha
In azerty keyboard configuration, we can't use the '|' shortcut to activate/deactivate the guide lines.
Don't know if you've already noticed it.
Thanks in advance,

Hello.

Another keyboard related issue :
Im using Ubuntu 10.04 with Compiz.
The keyboard base layout is US (qwerty) because of my girlfriend. When I'm using the computer I switch to FRA (azerty).
Under Inkscape 0.48, if I write a text, keys input the right characters (A key input a A). But as soon as I'm using a Ctrl combo, let's say Ctrl+A, Inkscape uses the US keyboard layout and issue a Ctrl+Q instead of a Ctrl+A.

So :
- When not using a modifier key, Inkscape uses the current keyboard layout defined by the window manager.
- When using a modifier key, Inkscape uses the keyboard layout the X system started with.

Actually, to avoid this problem I'm using another user account with FRA keyboard by default. But I'm reporting this issue anyway because I guess it's not working really the way it should.

As comment Pierre in #13 :
Shortcuts # (Grid), | (Guides) and % (Snap) not working on Windows (french keyboard).
Is this the same bug as describe on the summary ? Or it needs an another report ?

Yes it is in my humble opinion.

Have similar problem, maybe it should be another ticket.
(Windows 7)
Character shortcuts (like Ctrl+C/Ctrl+V) work fine then current keyboard layout is English, but doesn't work then layout set to Russian. Non character shortcuts (like F1) work good with any layout.

Closing because INVALID: duplicate issue ad infinitum.

See https://gitlab.com/groups/inkscape/-/issues?scope=all&utf8=%E2%9C%93&state=all&label_name[]=Input%3A%3AShortcuts

If you feel this issue has been unjustly closed, please feel free to open a new issue at https://inkscape.org/report . Thank you.

Closed by: https://gitlab.com/greytomorrow