CLI RemoveTextForHI leaves empty lines

[Manujito]

Hi, I'm working on a batch script and run into an error with the RemoveTextForHI command.

When using it from the GUI, everything works correctly, but using it via command line leaves empy lines and dialogue dashes all around.

Examples:

I'm using the latest version (4.0.10).

Hope it gets fixed, thanks!

[niksedk]

Hopefully fixed in latest beta: https://github.com/SubtitleEdit/subtitleedit/releases/download/4.0.10/SubtitleEditBeta.zip

And in the cli only version too: https://github.com/SubtitleEdit/subtitleedit-cli

[Manujito]

Hopefully fixed in latest beta: https://github.com/SubtitleEdit/subtitleedit/releases/download/4.0.10/SubtitleEditBeta.zip

Thanks for the quick update. But it's "almost" fixed. Two issues remain:

1. Now the lines are not automatically renumbered after HI lines are removed...

2. ...and lines with dialogue dashes are still left behind:

[niksedk]

Could you attach the subtitle file (Github accepts .zip attachments)

[Manujito]

Sure, here it is:

Another Life.S01E01.en.vtt.zip

I tried both converting from .vtt to .srt and .srt to .srt

[niksedk]

Hm, I cannot re-create the issue:

Any ideas?

[Manujito]

That's from the GUI though. My issue only happens when using the CLI command through a .bat script.

I don't know why there's a different behavior, since I assumed the CLI would just use the same code that the GUI uses, but there is.

[GrampaWildWilly]

This is kind of a shot in the dark. In .bat files, you have to be careful about certain characters. One that comes to mind is %. You need to take evasive maneuvers with these characters. Specifically in the case of %, you have to code %% if you want it to be interpreted as a percent sign & not as the beginning of a parameter being passed around. I think there's other such characters as well. I imagine there's documentation on this at the Microsoft web site . . . if you can manage to concoct the right search to make it give you the relevant help, a not insignificant feat.

Or not. Like I said, I'm guessing.

[niksedk]

It should be the same code... I will test from cli.

[niksedk]

Sorry, I cannot re-create your issue in latest beta...

[Manujito]

I just tried the latest beta. The lines are now numbered correctly, the only issue that remains is the dialogue dashes left behind, which again, it's not an issue when using the GUI.

Example of the issue:

I stripped down my script to a couple of lines to be able to just drop it in the beta folder and test it, this is what I'm using:

test.HI.remove.zip