Bug 75019 - FILESAVE: Failed to cover Bookmark and Bookmark Link-Export to MediaWiki
Summary: FILESAVE: Failed to cover Bookmark and Bookmark Link-Export to MediaWiki
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version: 4.2.0.4 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard: BSA EasyHack DifficultyBeginner
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-15 13:47 UTC by steven
Modified: 2014-12-02 10:53 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description steven 2014-02-15 13:47:19 UTC
Problem description: 

ODT export to MediaWiki, failed to cover Bookmark Link

Steps to reproduce:
1. .... set a bookmark "abc" to the text "test"
2. .... set a docutment hyperlink to the text "1234, target="abc"; the link works
3. .... export to MediaWiki, 

a) the text "test" has no "abc" bookmark/anchor in the wiki page
b) the link display: [#abc test] in the wiki page


Current behavior:

Expected behavior:

for above example, 

the bookmark sould be cover to a Anchor, "<span id="abc" title="abc">test</span>" (<span id="{{{id}}}" title="{{{id}}}">{{{anchored text}}}</span>)

then it shoud be cover to "[[#abc|test]]
              
Thanks!
Operating System: Windows 7
Version: 4.2.0.4 release
Comment 1 steven 2014-02-15 13:54:53 UTC
Revised: the link shoud be cover to "[[#abc|test]]
Comment 2 David Tardon 2014-02-15 14:03:21 UTC
The code is in swext/mediawiki/src/filter/odt2mediawiki.xsl .

I suggest exporting a suitable input file into Flat ODF and then using an XSLT processor directly. One advantage of that approach is that one does not even need to build libreoffice.
Comment 3 Björn Michaelsen 2014-12-02 10:53:08 UTC
adding LibreOffice developer list as CC to unresolved Writer EasyHacks for better visibility.

see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.