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 471393 - Synchronize subtitles using multiple sync points
Synchronize subtitles using multiple sync points
Status: RESOLVED FIXED
Product: gnome-subtitles
Classification: Other
Component: general
0.8
Other All
: Normal enhancement
: ---
Assigned To: Maintainers of GNOME subtitles
Maintainers of GNOME subtitles
: 556460 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-08-29 02:03 UTC by Luciano A. Ferrer
Modified: 2009-06-06 01:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Luciano A. Ferrer 2007-08-29 02:03:23 UTC
It will be great to have two new little buttons somewhere, to store first and last times and then readjust subtitles (selected or all) using those values... currently we have to write times, and the fill the time inputs...

for ex, when the actor starts talking the first dialog I hit pause, and then this start dialog button (to store the current time), then I go to the last dialog and hit pause when the actor start it and hit the end dialog button...
and then... what? maybe another two buttons? one for sincronize using all the subtitles and another to sincronize using the selected subtitles?
or maybe you can go to the adjust menu, and then you have two buttons, first and last dialog, and when you hit them the values are used in the time inputs (where you can make little adjustments after that)
Comment 1 Pedro Castro 2007-09-06 23:03:37 UTC
Hey there,

This feature is already on the TODO list. It's the automatic equivalent to the current "Adjust" dialog. The idea is to have a button that sets a "synchronization point", and another that opens a synchronization dialog, which lists the current sync points.
Comment 2 Pedro Castro 2008-10-17 20:04:31 UTC
*** Bug 556460 has been marked as a duplicate of this bug. ***
Comment 3 Pedro Castro 2009-06-06 01:54:13 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release.