Hi all,

I was using PotPlayer v1.6.63638 for long time. Now I'm using v1.7 and I noticed that precomposed ellipsis in subtitles (.srt) is not displayed anymore. I'm not talking about three dots as separate dots (...), but precomposed ellipsis, which is three dots as one character (…). (Ellipsis)

PotPlayer v1.6 displayed precomposed ellipsis in subtitles, but in v1.7 precomposed ellipsis is not displayed anymore. I tried to install v1.6 again and precomposed ellipsis is displayed. I'm using same settings in v1.7 as I used in v1.6 so I don't know if this is a bug or PotPlayer does not support this anymore?

"ellipsis in subtitles (.srt)"
On my system is displayed normally
pp 1.7.13679 \ Win 10

1
00:00:00,000 --> 00:01:00,000
A) Text … text
B) <i>Text …</i>
C) Text …

I found out something. Precomposed ellipsis is displayed in case A) and B) if there is something after the ellipsis, but it's not displayed in C) case.
Most if not all of my subtitles are encoded in ANSI format. If I change .srt encode to UTF-8, then ellipsis are displayed in all three cases.

I don't know what was changed in v1.7, but v1.6 displays precomposed ellipsis in .srt with ANSI encode, even in C) case.

If this is not a bug in v1.7, then maybe I will replace all precomposed ellipsis with normal three dots. It's easier then converting subtitles from ANSI to UTF-8. Or I will stay on v1.6.

Yes,
i have problem with ANSI + C) case.
I sent a report to dev.

Probably, the problem depends on something else.
The developer does not have this problem.

I found this site with all versions of PotPlayer:
https://www.videohelp.com/software/PotPlayer/old-versions#downloadold

I downloaded and tested different versions and up to v1.7.7569 (probably beta) or stable v1.7.7150 the Precomposed ellipsis is displayed, but it is not displayed anymore from v1.7.7627.

Something has changed between v1.7.7569 (v1.7.7150) and v1.7.7627. I hope this helps somehow. And I have Win 10 Pro v1803, if this could be somehow related to this problem.

I wrote email to developer to see if he found anything about this. He said that he don't know what could be wrong, but then he fix it in beta 1.7.16951 so now it works again!