The rules regarding --sentence and ellipses

[despairTK]

When a sentence ends with a "..." punctuation mark, it is automatically merged with the next sentence.
For example this situation:

177
00:24:45,760 --> 00:24:48,300
So I think...

178
00:24:48,300 --> 00:24:49,940
hmm...

179
00:24:49,940 --> 00:24:53,560
we can add like a cover page for our cafe design.

After merging:

177
00:24:45,760 --> 00:24:53,560
So I think...hmm...we can add like a cover page for our cafe design.

[Purfview]

Share json and srt of it.

[despairTK]

Thanks for your work, I tried both test versions, the first test version is very effective, the second test version is not merged correctly.

[Purfview]

the second test version is not merged correctly

share json and srt

[despairTK]

Files for the first test version:
test01-01.zip
test01-02.zip

Files for the second test version:
test02-01.zip
test02-02.zip

I just did a few more tests and found that the second test version will work normally, but sometimes it will encounter some special circumstances.

For example, in test01-01:

1
00:00:00,000 --> 00:00:07,320
So now we reach the last section of chapter 1, and here we finally get to do what you all signed up for, which is... Draw.

Compare test01-02

1
00:00:00,000 --> 00:00:06,420
So now we reach the last section of chapter 1, and here we finally get to do what you all signed up for, which is...

2
00:00:07,020 --> 00:00:07,320
Draw.

If "Draw" is used as a single line of subtitles, it may be translated into a meaning inconsistent with the content. For example, this subtitle file introduces the content of painting, so "Draw" should be translated into painting. But because it is disconnected from the previous sentence, the meaning after machine translation becomes drawing rewards.

However, this situation is relatively rare, and for me the first test version is more suitable for me.

[Purfview]

I tried both test versions, the first test version is very effective, the second test version is not merged correctly.

Looking at your files, test2 works correctly, when test1 is not.
So, I'll go with the test2 version.
If you think that test1 is better for you then I can add option to turn on the test1 behavior.

but sometimes it will encounter some special circumstances.

Model put "Draw" in the new segment with the capital letter, so it's a mistake of a model not a mistake of "..." splitting.
If "Draw" would be still in the same segment [in pure whisper output] then test2 wouldn't split it.

[despairTK]

Please follow the test2 version. This special situation I encountered rarely happens. Generally, when checking the subtitles, I will basically discover and modify it.

[Lycoan]

Now it's clear what you want.

"..." The presence of this symbol generally means that a sentence is not finished

Not always, sometimes it's the end of sentence.

Yes, sometimes it can be the end of the sentence: it can also indicate that the speaker leaves the scene and his voice fades.
If it is the end of the sentence, merging can lead to a wrong result, because the next part can belong to new speaker. That is why I like breaking subtitle by sentences, that way there can be no such merging error.

[Purfview]

That is why I like breaking subtitle by sentences, that way there can be no such merging error.

But in his both examples sentence is broken on every "...".

[Purfview]

that way there can be no such merging error.

He expressed it wrongly, in the OP he wrote a behavior he wishes [to merge on ellipses].

[Lycoan]

Okay, thank you for clarifying, now I know what you meant by ellipses. :)
It will be a nice feature.

[Purfview]

Implemented in r172.4.