Apache OpenOffice (AOO) Bugzilla – Issue 53064
"File -> Export as PDF ...." defaults to HTML (GTK-filepicker)
Last modified: 2005-09-02 10:32:25 UTC
I have a drawing open in Draw 1.9.117. When I choose "File -> Export as PDF..." plus "Save" I get the "HTML Export" dialogue instead of the expected "PDF options" dialogue. The work-around is to manually select "File type", but then there is of course no point in the "Export as PDF..." choice.
Sorry, not reproducible. When using export as pdf there is automatically the pdf file type filter selected. Any additional infos on how to reproduce this? Thanks.
I believe it worked as expected once here too - at least I did not notice the bug first time I used Draw. Now the problem occurs every time (for several days), I am not able to avoid it. This is what I do: 1. Start Draw 2. Load drawing 3. Choose File - > Export as PDF .... 4. Click Save and there is the HTML Export box. If I check the file-type list on 3., I find that HTML (not PDF) is selected.
just for the records: I can't reproduce this here on Ubuntu Linux using m122... Export as PDF exports to pdf, not to HTML... Maybe you could try a newer version (like m122) on your system?
confirming on linux with m125, but only with gtk-filepicker, not with OOo dialogs. There is no difference in choosing "File|Export..." or "File|Export to PDF..." In both cases the filetype defaults to HTML When trying to export a writer-Document, the dialog defaults to PDF. Even worse is the fact that the "Export directly to PDF"-button in the toolbar defaults to HTML as well. (again: Only the gtk-fpicker, not the OOo one) Writer probably only is OK because PDF is the first in the list of fileformats there. I guess when you set-up a new export Filter, then the dialogs would fail in writer as well.
.
i see the problem
done in cmcfixes16 cmc->mmeeks: might want this patch
verified in m125+cmcfixes16. Export defaults to PDF both when using Toolbar and the menu. Exporting to other formats still possible as wel :-)
I just updated to 1.9.125. I still have exactly the same problem as when I first reported the problem.
verified in m125+cmcfixes16. ^^^^^^^^^^^ This is the important part. The fix is not yet included in the main-codeline, it currently is in a cws. You cannot download a version with the fix at this time. You have to wait until the cws cmcfixes16 gets integrated (or build yourself as I did). resolving fixed again.
and verified again. Only when the issue is closed you can expect the fix to be available in a build you can download.
Sorry for my misunderstanding, and thanks for educating me :-)
set target to 2.0
1.9.127