Accented letters not behaving properly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-29-2007 09:45 AM
When we attempt to type names (users) which contain accented letters, they do not resolve. For example, if a tech is filling in an Incident form for one of our Paris office users, and that name contains one or more accents, the name does not appear from the pop-up menu of matching names. Instead, we have to click on the magnifying glass located by the user field, then search using only the letters preceeding the accented letter. Sometimes, we have to specify the first name instead as the last name may have accents on the first or second letter. Of course, if the first name is a common one, then we have even more difficulty locating the user. This has been causing much hardship for our technicians.
Has anyone else encountered this issue? Was there a work-around or solution which was identified?
Thanks.
P.S. When we don locate the name, it initially appears with additional unwanted characters. This can make it look like gibberish. Only upon saving the ticket does the name appear as desired.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-02-2007 08:58 AM
Our main concern is that names are not resolving when a non-accented letter is typed within the user name field within where an accented letter is expected. Has there been any progress with this issue? This problem is causing a significant impact in our foreign offices and I would love to see it go away.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-02-2007 09:28 AM
The progress right now is that I can't replicate it when I do it myself, even using the same names you mentioned. Which, unfortunately, means you're probably going to have to route this over to support to see if you guys can come up with a repeatable test case that I can take a look at. Just following the steps you mentioned (with the names you mentioned) seems to work for me on the current code base. It fails, as expected, on the older code, but, like I said, for me at least, it works on current code.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-07-2023 11:10 AM
This appears to be the bug I was thinking about.
Could you try creating a user with that name Squishmallows mushroom on /demo and attempting to autocomplete their name?
My assumption is that this has already been addressed and that it will operate properly on /demo (and hence properly on your instance as of July 5th).