After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 444945 - Option to auto trim long text lines
Option to auto trim long text lines
Status: RESOLVED DUPLICATE of bug 439832
Product: gnome-subtitles
Classification: Other
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Maintainers of GNOME subtitles
Maintainers of GNOME subtitles
Depends on:
Blocks:
 
 
Reported: 2007-06-07 00:42 UTC by Luciano A. Ferrer
Modified: 2010-11-07 12:34 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Luciano A. Ferrer 2007-06-07 00:42:23 UTC
Hi!

It would be nice to have an option to auto add a line break on long lines, more than XX characters... the user will have to add that XX value in the gnome-subtitle preferences or something...

and something like:
"This is a very long line, that most dvd players wont show correctly at all"
to
"This is a very long line, that most
dvd players wont show correctly at all"

or something like that :)
Comment 1 Pedro Castro 2007-06-07 11:25:20 UTC
Hi,

Bug #439832 proposes a dialog to show errors with subtitles. One of the errors would be detecting long lines, which is specifically being handled in #430961.

Now, what you mean, is to not only have that detection, but also automatically correcting it. How do you propose this to work? I'm thinking about a checkbox, near the respective option in the dialog I referred, saying "autocorrect". This means to autocorrect that kind of error when detected. What do you think?
Comment 2 Luciano A. Ferrer 2007-06-07 12:42:40 UTC
That will be amazing Pedro...

and warnings proposed on 430961 are nice too...

how will be handled/showed those warnings?
background coloring of problematic lines in the same workspace?
Comment 3 Pedro Castro 2007-06-07 13:22:22 UTC
Well, there must be a dialog shown with the errors for the incorrect subtitles. Coloring can also be done, but I'm not considering it at first.

About autofixing long lines, there are still some issues. For instance, what would you do if there are 2 lines of text longer than the maximum? Those can't be split because it would imply having more than 2 lines in a caption, which is not recommended.
Comment 4 itai_y_beerli 2007-10-06 09:33:22 UTC
I, too, would appreciate such a feature.
Comment 5 LoLDog 2009-10-04 17:06:40 UTC
I need those lines!

Seriously though what I would love is from when I'm translating have some thing that guarantee that I will have only 40 characters per line and stops allowing me to type any further. It could be that simple or it could automatically insert a CR when the number of characters reach 40 and stops typing in the second line.

As for when you are trying to correct subs when I do it manually I always leave the starting point alone and focus only on the end part I reduce the time to coincide with the start of the next sub minus 200ms.

example

1 [start 1.20.500]...[end 1.25.500]
2 [start 1.23.300]...[end 1.28.750]

They are overlapping so if I was to correct it, I would assume that I don't want to touch the start point because they are supposedly right already, they start at the beginning of a dialogue and are correct most of the time so I just ajust the end part to correct it.

1 [start 1.20.500]...[end 1.23.100]
2 [start 1.23.300]...[end 1.28.750]

usually I find that 200ms is a good space between subs but I do think that should be adjustable as there is times when people would not have the time to take out 200ms from each and every sub in a long dialogue it would amount to seconds in the end.

There is one snag though, when the sub has a very short duration and contracting it would mean not showing it at all or very very briefly, I think a sub should always be 500ms minimum in lenght otherwise it would be better to join it with the one ahead or before, that app could ask this if it finds them.

Cheers.
Comment 6 LoLDog 2009-10-04 17:13:18 UTC
"About autofixing long lines, there are still some issues. For instance, what
would you do if there are 2 lines of text longer than the maximum? Those can't
be split because it would imply having more than 2 lines in a caption, which is
not recommended."

I can answer that.

The solution would be to make the program delete all CR(Carriage Returns) from the text making it a one big line and add a CR at 40 and split the sub at 80 and asking for and end time for it then making a new sub and asking a start and end time for it. No?

Cheers.
Comment 7 Pedro Castro 2010-11-07 12:34:39 UTC
Marking as a duplicate of "Dialog with information and errors", which will include the features mentioned here.

*** This bug has been marked as a duplicate of bug 439832 ***