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 504656 - Set defaultsubtitle format, character coding and newline type in preferences
Set defaultsubtitle format, character coding and newline type in preferences
Status: RESOLVED FIXED
Product: gnome-subtitles
Classification: Other
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Maintainers of GNOME subtitles
Maintainers of GNOME subtitles
: 558630 609192 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-12-20 12:53 UTC by Yann Basly
Modified: 2010-02-11 23:18 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Yann Basly 2007-12-20 12:53:10 UTC
Hi,

It would be nice to have the ability to set a default setting for the subtitle format, the character coding and the newline type in the preference window.

In order to have my subs working with my dvd player I always have to set the encoding to iso-8859-15, and the newline type to 'windows' (yes I know...).

Thank you !
Comment 1 Pedro Castro 2008-01-02 23:08:27 UTC
Hi,

Thank you for the report.

I agree with this, there should be a way to set this in the preferences.
Comment 2 Pedro Castro 2008-11-02 15:28:48 UTC
*** Bug 558630 has been marked as a duplicate of this bug. ***
Comment 3 Pedro Castro 2009-08-31 21:20:58 UTC
Additionally, as reported in http://sourceforge.net/forum/message.php?msg_id=7597002, there should be an option "remember last used" which would allow to remember the last used setting.
Comment 4 Pedro Castro 2009-09-05 19:20:55 UTC
It should also be useful to have an option for the fallback encoding. This would be used when auto-detection fails (example of greek encoding windows-1253).
Comment 5 Pedro Castro 2010-02-07 21:36:41 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release.
Comment 6 Pedro Castro 2010-02-11 23:18:00 UTC
*** Bug 609192 has been marked as a duplicate of this bug. ***