[jQuery] Re: Using ASCII characters in textfield

2008-07-02 Thread Brian J. Fink

Apparently the Autocomplete plugin is escaping the & character. This
may be a bug, or may be done intentionally, I don't know.

I'm not sure what the workaround would be.

On Jul 2, 10:02 am, Gearóid O'Ceallaigh <[EMAIL PROTECTED]> wrote:
> I'm using an autocomplete function on a textfield but I'm having a
> problem since the autocomplete array is filled with German words so
> special characters (such as ü, ä and ö). I can insert the ASCII codes
> for these characters in the array and when the autocomplete display
> pulls down, the array elements are displayed correctly.
>
> However, when the user selects an option with a German character, the
> ASCII code of the element is displayed instead of the German
> character.
>
> For example, if the user selects "Anlagenführer", the text field would
> be populated with "Anlagenführer".
>
> Does anyone have any ideas of a workaround?


[jQuery] Re: Using ASCII characters in textfield

2008-07-02 Thread Jörn Zaefferer

Set encoding of the enclosing page to UTF-8 and encode the page and
the data, no matter if local data or retrieved via ajax, as UTF-8.
Avoid using entity encodings entirely - as long as the encoding is
right, you won't need them anyway.

It may be hard to get there, but its more then worth the trouble!

Jörn

On Wed, Jul 2, 2008 at 4:02 PM, Gearóid O'Ceallaigh <[EMAIL PROTECTED]> wrote:
>
> I'm using an autocomplete function on a textfield but I'm having a
> problem since the autocomplete array is filled with German words so
> special characters (such as ü, ä and ö). I can insert the ASCII codes
> for these characters in the array and when the autocomplete display
> pulls down, the array elements are displayed correctly.
>
> However, when the user selects an option with a German character, the
> ASCII code of the element is displayed instead of the German
> character.
>
> For example, if the user selects "Anlagenführer", the text field would
> be populated with "Anlagenführer".
>
> Does anyone have any ideas of a workaround?
>