Issue 124539 - Internal Hyperlinks lost in partial PDF export without automatically inserted blank pages
Summary: Internal Hyperlinks lost in partial PDF export without automatically inserted...
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: save-export (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL: http://www.bielefeldundbuss.de/LibO/T...
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-27 18:21 UTC by Rainer Bielefeld
Modified: 2014-03-28 18:24 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: 4.1.0-dev
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Rainer Bielefeld 2014-03-27 18:21:38 UTC 
Hyperlinks from source.odt still look like hyperlinks (blue characters underlined), but no hyperlink exported: No mouse pointer change when mouseover, no jump when click.

Hyperlinks work fine if all document becomes exported to PDF with the same settings.

Partial PDF export works fine from the same documents with LibO 4.2 because of FIX for "LibO#34093 - Partial PDFEXPORT of particular Master Documents breaks hyperlinks" 

You can find the LibO Bug test kit at above mentioned URL. Follow instructions in LibO Bug to reproduce the problem.

CONFIRMED & OS & Version due to Results in LibO Bug.

This one might be related to "Issue 113182 - Hyperlink broken in partial PDFexport of Spreadsheet"

Might be a good opportunity to check "Issue 106636 - PDF Export: Hyperlinks do not work in header/footer in case of a partial export"
Comment 1 Rainer Bielefeld 2014-03-27 18:31:35 UTC 
Still Reproducible with server installation of "AOO 4.1.0-dev – English UI / German locale - [AOO410m14(Build:9760)  -  Rev. 1577236 2014-03-15]" on German WIN7 Home Premium (64bit)", own separate user profile.
Comment 2 Armin Le Grand 2014-03-28 18:04:34 UTC 
Tried different things with the PageNumbering, does not really look wrong. It also may have to do with #119348#, but I tried in the debugger to run without that fix and the effect is the same. It's about exporting Pages 4-13 with all CheckBoxes in 'Links' tab checked. Also tried the rRenderable->render call in PDFExport::ExportSelection which uses nCurrentRenderer derived from nSel to be based on nIncreasingPageNumber, too. Will need to take an even closer look...
Comment 3 Armin Le Grand 2014-03-28 18:24:00 UTC 
Debugged CalcOutputPageNum in SwEnhancedPDFExportHelper, looks good and gives the physical PageNum. Checking what the PdfExport does with these will be much harder...