Feature Request: Color for length/cps that is over certain threshold but not in the limit yet

Open
#16,586 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
desktop

Research direction

The request is to add a warning color for subtitle line length and characters-per-second when a line is close to the limit but not over it, matching the yellow used by the user-defined regex rules. Start by reading how the user-defined error rules and their colors are handled in the C# codebase, and check the existing CPS and line-length limit checks. Before coding, confirm with the maintainers how the threshold should be configured, since the issue leaves that open.

Written by the indexing model from the issue text.

Description

In the user defined error rules (which are great!) it's not possible to measure cps. I would greatly appreciate it if I could label subtitle lenghts that do not exceed the defined limit but come close to it. Same as in the user defined regex rules, I would prefer not to use the (red) error color (as it's not an error by definition) but the same as in the user defined rules (in my case that would be yellow).

In practical terms that would be very helpful as compared to just lowering the actual limit, as those would not show up in error reports and I can already think ahead for projects where the main movie is 24fps but the TV version is 25fps and therefore some subtitles would then exceed the limits in the broadcast version.

Thank you for considering that.

Dominant language
C#
Stars
14.8k
Forks
1.4k
Avg merge
1h 1m
Merged PRs (30d)
668

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SubtitleEdit/subtitleedit

All issues in SubtitleEdit/subtitleedit

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.