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 514122 - Print dialog should use file name as basis for output PDF/PS file name
Print dialog should use file name as basis for output PDF/PS file name
Status: RESOLVED DUPLICATE of bug 587086
Product: gtk+
Classification: Platform
Component: Printing
unspecified
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
: 151387 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-02-03 17:49 UTC by Pavel Šefránek
Modified: 2010-10-11 04:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Pavel Šefránek 2008-02-03 17:49:51 UTC 
Currently, when you print to PDF, the print-manager uses 'output.pdf' as the
default for the file name it produces.

I would be better if it used the name of the file being printed as the basis for
the file name.  This would alleviate a lot of need to change the name before
'printing' and also help make it more obvious which file the output went to.
Comment 1 Pavel Šefránek 2008-02-03 17:50:58 UTC 
*** Bug 151387 has been marked as a duplicate of this bug. ***
Comment 2 Sven Neumann 2008-02-25 14:24:21 UTC 
Perhaps gtk_print_operation_set_export_filename() could be (ab)used for this. If the documentation was changed, this should be OK and it would not break existing users of this API, as far as I can see.
Comment 3 Sven Neumann 2008-02-25 14:45:20 UTC 
Actually, the application can already set the filename used. Just call 

 gtk_print_settings_set (GTK_PRINT_SETTINGS_OUTPUT_URI, uri)

with a file: URI. You should make sure that you set a filename that matches the output format as specified using the GTK_PRINT_SETTINGS_OUTPUT_FILE_FORMAT key.
Comment 4 Javier Jardón (IRC: jjardon) 2010-10-11 04:09:20 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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