ColorToDialog - Dash not being added when a different character speaks (color change)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- desktop-dev
Research direction
Start with ColorToDialogUnitTest.cs and run the existing TestDialog3 case to compare its behavior with the issue examples. Then locate the ColorToDialog handling for consecutive colored lines and reproduce the missing-dash case. Done means speaker changes between colored lines produce the expected dash without altering lines from the same speaker.
Written by the indexing model from the issue text.
Description
The plugin successfully adds a dash when a line next to a colored line has no color.
But it doesn't add it when there are lines with different colors.
For example.
Currently it turns this:
1
00:00:01,280 --> 00:00:02,639
Wow! #blue
I can believe this! #blue
2
00:00:02,720 --> 00:00:04,039
This is amazing! #blue
This is terrible! #red
Into this
1
00:00:01,280 --> 00:00:02,639
Wow!
I can't believe this!
2
00:00:02,720 --> 00:00:04,039
This is amazing!
This is terrible!
**When it actually should be:
1
00:00:01,280 --> 00:00:02,639
Wow!
I can't believe this!
2
00:00:02,720 --> 00:00:04,039
- This is amazing!
- This is terrible!
Or even this, (although it's not that usual)
1
00:00:01,280 --> 00:00:02,639
Wow!
I can't believe this!
2
00:00:02,720 --> 00:00:04,039
This is amazing! ((no dash since the previous line comes from the same character)
- This is terrible!
Otherwise, it's "destroying" info,
Currently it works if one of the lines have no color, but it won't work if the two of them are already colored.
I can't seem to replicate the "TestDialog3" result from ColorToDialogUnitTest.cs , so I'm not sure if it's working as intended.
tl;dr the plugin won't add a dash if all lines contain a "<font " tag
- Dominant language
- C#
- Stars
- 137
- Forks
- 48
- Avg merge
- 5m
- Merged PRs (30d)
- 6
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from SubtitleEdit/plugins
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
SubtitleEdit/plugins#286 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
SubtitleEdit/plugins#283 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
SubtitleEdit/plugins#274 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
SubtitleEdit/plugins#266 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
SubtitleEdit/plugins#265 · 2 comments ·
All issues in SubtitleEdit/plugins
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100