ChatGPT removes colons ":" and everything that follows it from prompts and replies

In Finnish language we use a lot of colons. Like a question “Who knows about the ERP?” would translate “Kuka tietää ERP:stä?”. But when I type that in and send the query, it reads “Kuka tietää ERP”. Basically ChatGPT is removing everything after (and including) the colon.

The same happen’s when it’s trying to type Finnish. Before GPT-4o when I used GPT-4 this worked normally, but now all the GPT generated answers are missing everything after the colon and the end result doesn’t look like my language at all anymore and need’s a lot of cleaning making the GPT much less usable than before.

5 Likes

Hi!
You are correct that there is a weird bug with text following colons.

We did some community investigations and found that the text exists, it’s just not being rendered…

3 Likes

Yes this is what I was expecting also because it’s grammatically correct but just not rendered. So it seems that the model itself is working properly but the UI somehow not.

3 Likes

Is there any solution or workaround for this?

2 Likes

Hi!
If my recall is correct the issue does not arise if there is a space between the colon and whatever follows next.
That’s an idea for a potential workaround.

Regarding when this issue will be fixed: I do not know.

You are right. For example, if I type this prompt:

“Hi ChatGPT, could you repeat these lines after me?
NASA
:NASA
NASA:n”

ChatGPT’s reply will look like this:
"Sure, here are the lines:

NASA

NASA"

So it works exactly as you described. However, the problem at least in Finnish language is that it’s not grammatically correct to add space before the colon.

It’s also worth mentioning that the problem is in ChatGPT’s responses, not in the user’s prompts.

I’ve noticed that this problem occurs on my PC (Chrome & Firefox) but my Android phone’s ChatGPT app displays the same chats flawlessly without any problems.

3 Likes

I can confirm that this problem is still occurring on my browsers as well. It’s been for months now. I’m using PC. It’s probably just a glitch in the code that if something is followed by a colon, it’s considered as something other than text. It would probably be an easy fix.

Too bad that now all the endings are still hidden. Those endings in Finnish language are for positioning, like “from”, “to”, and so on. Those colons and the texts after them would be valuable to see as a part of normal language.

Is there something I’m doing wrong? Could somebody please address this problem?

4 Likes

You are right that if there’s a space after a colon, then this problem does not occur. And thanks for being honest.

But I think it’s worth mentioning that this problem is in ChatGPT’s replies. It’s hard to make Custom Instructions work so that ChatGPT would always add space after colon, especially when it’s grammatically incorrect.

3 Likes

It is a ChatGPT-specific problem. markdown2 has no issues on API software.

Example usage being discussed:

(real advanced is to render the descender “o” of ဖင်လန်ဘာသာစကားတွင် in Graphite with a teardrop shape script)

OpenAI would have to address the issue.

3 Likes

I had a related issue with the colon. I frequently want to translate English text to European Portuguese and any non-English text into English. I provided the following instruction to ChatGPT:

  1. Any text in English following a colon (“:”) with not text preceding the colon should be translated into European Portuguese.

  2. Any text in any language other than English following a colon (“:”) with not text preceding the colon should be translated into English.

The result was inconsistent - it worked often but often ChatGPT would (1) start conversing in Portuguese on all inquiries and/or (2) instead of translating - respond to the translation request as if it was an inquiry.

I asked ChatGPT why this was and ChatGPT alerted me to the colon developer issue and this forum link. I asked ChatGPT for an alternative to a colon as a translation request shortcut and ChatGPT offered this:

“Translate the following text to European Portuguese:

[Your English text here]”

I said that I had to translate frequently and did not see the need or to type that much explanatory text with clear overarching instructions, and was looking for a briefer shortcut.

ChatGPT then responded with this alternative:

“I understand your need for a concise method to indicate translations without using colons. To achieve this, we can implement a simple tagging system. Here’s how it works:
• For translations from English to European Portuguese, precede your text with the tag [EN-PT].
• For translations from any other language to English, use the tag [XX-EN], where XX represents the source language’s ISO 639-1 code.

Examples:
1. English to European Portuguese:

[EN-PT] Please close the door.

Translation:

Por favor, feche a porta.

2.	Spanish to English:

[ES-EN] Por favor, cierra la puerta.

Translation:

Please close the door.

3.	French to English:

[FR-EN] Veuillez fermer la porte.

Translation:

Please close the door.

Note: This tagging system ensures clarity and brevity in your translation requests. If you have specific preferences or need further customization, feel free to let me know.”

I responded as follows:

“That code is still too long. If the instruction is to translate ALL English text to European Portuguese preceded by a code, why would I need to identify the source or destination languages?

Also, if the second instruction is to translate ALL non-English text preceded by a code into English, once again, why would I need to identify the source or destination languages?

The source and destination languages are clear in the [over-arching]instructions.”

ChatGPT then responded with this:

“Apologies for the earlier suggestions. To streamline your translation process without specifying source or target languages each time, we can implement a simple tagging system. Here’s how it works:
• For English to European Portuguese translations, precede your text with the tag [T].
• For any other language to English translations, use the tag [T] as well.

Examples:
1. English to European Portuguese:

[T] Please close the door.

Translation:

Por favor, feche a porta.

2.	Spanish to English:

[T] Por favor, cierra la puerta.

Translation:

Please close the door.

This streamlined approach eliminates the need to specify languages each time, as the instructions you’ve provided already define the translation directions. If you have any further preferences or need additional assistance, please let me know.”

I responded that I thought that was a good alternative to the colon and will try it out (which I have yet to do).

Update to my previous message. I just tried the suggested [T] code and I am getting the same inconsistent results as with the “:” translation shortcut code, so I am reverting to writing the full text each time: “Please translate to [Y] language”