[Feature Request] Per-Format Export Settings

Open
#10,646 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
32/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
csharp
Domain
desktop

Research direction

No implementation files or tests are named. Start by reviewing the existing LRC exporter entry points and the attached mockups, then clarify which settings and format consolidation are in scope. Done means the agreed per-format options control tags and timestamp spacing without requiring duplicate formats or an unwanted export step.

Written by the indexing model from the issue text.

Description

I had an old local fork of V4 Subtitle Edit where I edited the exporter for LRC lyrics to exclude tags and add spaces after the line timestamps. I did this by commenting out the tag writing lines and adding a space to the line formatting. I'd love to have this as an option in V5 but doing so would require either:

  • Adding another save format for each of the LRC formats (12 formats in total; 3 for no spaces+tags (currently supported), 3 for no spaces+no tags, 3 for with spaces+tags, 3 for with spaces+no tags)
  • Always include spaces and always have tags excluded
  • Add an "Export Settings" window before the save file dialog for each option

The first method pollutes the UI with more formats for such a small change. The second one alienates users that prefer having no spaces and/or having the tags in the file. The third one would work but it adds an extra step in the export process which would get very annoying if working on multiple files in a row.

Adding per-format export settings would help massively in adding features like this and could further help in decluttering the amount of formats by merging similar formats under one and exporting based on these settings (EG: LRC Lyrics (.lrc), LRC Lyrics ms (.lrc), and LRC Lyrics, no end time (.lrc) becomes just LRC Lyrics (.lrc)).

I made some super quick mockups of the settings pages for how this could look. Thoughts?

Mockup 1 Mockup 2
Dominant language
C#
Stars
14.3k
Forks
1.3k
Avg merge
1h 19m
Merged PRs (30d)
782

Contributor guide

No contributing guide indexed for this repository

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.