After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 583878 - Hitting space bar will copy source to target
Hitting space bar will copy source to target
Status: RESOLVED FIXED
Product: gtranslator
Classification: Other
Component: Interface
1.9.x
Other All
: Normal normal
: 2.0
Assigned To: gtranslator-maint
gtranslator-maint
Depends on:
Blocks:
 
 
Reported: 2009-05-26 10:55 UTC by Jean-Michel Pouré
Modified: 2009-06-22 12:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screencast demonstrating space bar problem (666.06 KB, video/ogg)
2009-05-26 11:42 UTC, Jean-Michel Pouré
Details
Kdenlive po that I am working on, in case this file would be the problem. (141.06 KB, text/x-gettext-translation)
2009-06-04 13:18 UTC, Jean-Michel Pouré
Details

Description Jean-Michel Pouré 2009-05-26 10:55:11 UTC
Please describe the problem:
I am using gtranslator from Debian SID. Hiting space bar triggers the copy of source content to translation content. Thus it is impossible to use gTranslator.

Steps to reproduce:
1. Run gtranslator and open a po file
2. Select any string
3. Hit space bar


Actual results:
Source is copied to target.

Expected results:
I expect a space.

Does this happen every time?
Yes. On two different computers.

Other information:
Comment 1 Jean-Michel Pouré 2009-05-26 11:42:04 UTC
Created attachment 135380 [details]
Screencast demonstrating space bar problem

When editing the first word, everything is fine. The bug happens when I press space bar: source text (French) is copied to target (English). My Gnome environment is English. When switching to French, the same happens.
Comment 2 Jean-Michel Pouré 2009-05-27 07:59:14 UTC
The same happens with Gtranslator compiled from SVN. I think this is a Ctrl+space shortcut issue. For some reasons, hutting space will trigger copy source to target. Could it be fixed ASAP please?
Comment 3 Jean-Michel Pouré 2009-05-28 15:36:59 UTC
Any fix? I am stuck on my translation projects, including Kdenlive.
Comment 4 Jean-Michel Pouré 2009-06-03 07:20:39 UTC
I am still stuck. I would appreciate an answer or at least a start of explaination why space bar acts as a shortcut.
Comment 5 Pablo Sanxiao 2009-06-03 07:54:01 UTC
I couldn't reproduce this bad behaviour. I have tested in Debian, Ubuntu and ArchLinux and it works fine. Maybe it's a problem with your system configuration... but not sure
Comment 6 Ignacio Casal Quinteiro (nacho) 2009-06-03 07:57:24 UTC
Can you check if you have the file ~/.config/gtranslator/gtranslator-accels ?
If you have it try removing it. Maybe that fixes your problem.
Comment 7 Jean-Michel Pouré 2009-06-04 07:21:15 UTC
Thanks for your answers. I tried to remove ~/.config/gtranslator/gtranslator-accels. It is recreated on every launch of gtranslator and will not change settings.
Comment 8 Ignacio Casal Quinteiro (nacho) 2009-06-04 11:00:29 UTC
Yeah, that file is reacreated each time you launch gtranslator. But the problem persist after removing it? BTW if you have System->Appearence->Interface->Editable menu shortcut... activated you can change the shortcut from control+space to anything you want. That's what it is saved in the gtranslator-accels file.
Comment 9 Jean-Michel Pouré 2009-06-04 13:18:57 UTC
Created attachment 135936 [details]
Kdenlive po that I am working on, in case this file would be the problem.
Comment 10 Bruno Brouard 2009-06-05 16:05:55 UTC
Hello,

I have the same behavior with the space bar.
I am running Ubuntu 9.04 i installed yesterday.

I had the same problem some months ago when i try to compile from SVN
a new version of gtranslator.

It doesn't depend on po file and i try to different computer.
A friend told me that changing his keyboard layout has solve the problem.

I use the default french keyboard. I think that M Pouré is also french ?

Bruno
Comment 11 André Klapper 2009-06-07 20:55:57 UTC
(In reply to comment #4)
> I am still stuck. I would appreciate an answer or at least a start of
> explaination why space bar acts as a shortcut.

This is a bug tracker, not a support forum. Patience please.
Comment 12 Ignacio Casal Quinteiro (nacho) 2009-06-07 21:16:47 UTC
Do you have several keyboard layouts, maybe you have this problem because of a gtk+ bug about managing several keyboard layouts.
Comment 13 Jean-Michel Pouré 2009-06-09 10:50:16 UTC
Got it. Thanks ! I clicked reset to default on Gnome Keyboard and my Euro keyboard was replaced by a "default French legacy keyboard". Then the gtranslator problem was fixed. Whaooo. So much time, but thanks for the informations.

My stations were upgraded from old Gnome releases and it seems that I kept old keyboards all way long.

Thank you very much friends.
Comment 14 Bruno Brouard 2009-06-12 08:09:36 UTC
I have done some tests.

First, i have only one keyboard layout

Second, i tested 3 different frenc keyboard layout and the same problem with space bar exist.

Third, and the more important : 
I try some modification in the "Keyboard Layout Options"
"Using space key to input non-breakable space character"

The original choice is "default"
If i choose : "Space key outputs usual space at any level" then the problem disappear. I try to put again "default" and it came back to the original bad state.


As conclusion, in the french keyboard layout (and maybe other), space-bar work as "non-breakable space" wich maybe correspond to the combinaison "ctrl + space" in english keyboard layout.


Now i can work with gtranslator by changing this default option (i don't know why this option exist because the space is still breakable anyway !) but it would be preferable to change your keyboard shortcut for replacing original text into translated text.

Bruno
Comment 15 Bruno Brouard 2009-06-22 12:42:59 UTC
I don't think that this BUG should be marked as FIXED because gtranslator should work with standard keyboard ?

Bruno

PS : the choise a made previously (see comment #14) was not correct : "Space key outputs usual space at any level" because it was then impossible to type unbreakable space. 

I must choose "Space key outputs non-breakable space character at second level." to make it work.