Bug 30685 - Unable to use special character codes.
Summary: Unable to use special character codes.
Status: RESOLVED DUPLICATE of bug 24197
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: unspecified
Hardware: PC Windows
: Normal normal
Target Milestone: master
Assignee: Cody Russell
URL:
Depends on:
Blocks:
 
Reported: 2015-06-02 15:08 UTC by evandcombs
Modified: 2015-06-03 14:14 UTC (History)
2 users (show)

Tags: gtk
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED DUPLICATE of bug 24197

Description evandcombs 2015-06-02 15:08:56 UTC
It does not come up with an error, but whenever I try to create a character with an accent, for example ñ which is created by pressing alt+164, it doesn't work. I cannot even copy and paste such characters into Xamarin Studio. I do not know why this is not supported, but it needs to be.
Comment 1 Mike Krüger 2015-06-03 12:23:54 UTC
That's an issue in the gtk IME layer I think.

At best it would be supported on windows like it's on linux - but I don't know if it's possible. (May be handled on windows level)
Comment 2 Cody Russell 2015-06-03 14:14:51 UTC

*** This bug has been marked as a duplicate of bug 24197 ***