Support of unicode in gpt4-1106-preview

Hi,

we’re experimenting with gpt4-1106-preview using function call. and discovered the following:

if the user input is non ascii, the output will often be multi-level escaped unicode characters, which is a headache dealing with global audience…

example:


using prompt:

4 Likes

I have exactly the same problem.

I think it’s a similar problem below replied by @atty-openai

/t/gpt-4-1106-preview-messes-up-function-call-parameters-encoding/478500/2

It works right once I translated all Korean characters into English alphabets and remove all line-feed characters.

Please report this @atty-openai, Thanks!

2 Likes

I am experiencing similar issues with output that has Korean/English mixed output.
In the output below, ' g c g e e c h e w a s n e w .' is supposed to be Korean writing.

The student translated ' g c g e e c h e w a s n e w .' as
'They shared their experience.' 

Originally, my prompt surrounded user input in <<brackets like this>> and it caused significantly worse output.

1 Like

The problem is fixed in the latest update.