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 436298 - dia: File selection menus need warning of input method
dia: File selection menus need warning of input method
Status: RESOLVED WONTFIX
Product: gtk+
Classification: Platform
Component: .General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2007-05-06 09:27 UTC by Roland Stigge
Modified: 2009-02-14 23:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Roland Stigge 2007-05-06 09:27:55 UTC 
Hi,

a Debian user reported the following:

===============================================================
The windows that let you type in file names need to warn
you when the input method is not the default.  Otherwise,
it is possible to go to a non-standard input method
to put some special characters into a diagram,
and leave it turned on when you type a file name.
The file name then ends up with unintended 8-bit characters.

It would probably be best if all windows relating to filenames
had their own choice of input method.  Failing that, a little
notice saying "Input Method=IPA" would be good.
===============================================================

See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405323

I can reproduce the problem with dia 0.96.1. Please decide yourself if we should follow the above suggestions.

Thanks,

Roland
Comment 1 Lars Clausen 2007-06-29 16:41:01 UTC 
The file name input field does allow switching input method through a right-click, but it's not obvious that this is the case.  Giving a notice when input method is non-default is probably the best.
Comment 2 Hans Breuer 2007-09-08 19:12:24 UTC 
Having some extra visual feedback on the file dialogs input field looks rather odd to me. Also it would be a Gtk+ issue, wouldn't it?
Comment 3 Hans Breuer 2009-02-14 23:37:50 UTC 
follow up on my own comment, but not reassigning to gkt+