EPrints Technical Mailing List Archive
Message: #08252
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] .docx Export
- To: John Salter <J.Salter@leeds.ac.uk>, "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: Re: [EP-tech] .docx Export
- From: Dennis Müller <dennis.mueller@bib.uni-mannheim.de>
- Date: Tue, 14 Jul 2020 17:48:59 +0200
Hi John, thanks for your quick answer. With your help, I could more or less do what I want with the document saving it to some path on the server. However, I'm struggling to find out how to return the actual document in my export plugin's "output_list" subroutine. Returning $oodoc or the file path doesn't work, obviously. Can you help me out once more, please? Cheers, Dennis Am 10.07.20 um 15:33 schrieb John Salter: > Hi Dennis, > I think you should be able to achieve this. > It's similar to the way the OpenOffice / Coversheets works. > That's normally configured to export as a PDF, but it first takes an OpenOffice document (your branded template), and replaces tags (like '##TITLE##') with rendered content. > > These are the tags: > https://github.com/eprintsug/coversheets/blob/master/cfg/cfg.d/z_coversheet_tags.pl > and this adds them to the OpenOffice document: > https://github.com/eprintsug/coversheets/blob/master/lib/plugins/EPrints/Plugin/Convert/AddCoversheet.pm#L114-L127 > > Does that help? > > There are probably other ways - possibly other perl modules that would allow a more direct approach - but the above stuff seems to work OK. > I'm using it with LibreOffice rather than OpenOffice if that's useful to know too. > > Cheers, > John > > -----Original Message----- > From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Dennis Müller via Eprints-tech > Sent: 10 July 2020 14:15 > To: eprints-tech@ecs.soton.ac.uk > Subject: [EP-tech] .docx Export > > Hi everyone, > > we've had a user request for exporting views/searches as a .docx file > styled in our corporate design. Has anyone ever done something similar? > > Just for the file format, it might work to "wrap" a simple text export > in an exporter that has a > "application/vnd.openxmlformats-officedocument.wordprocessingml.document" mimetype, > but I don't see where I could slip in the design template along the way. > > I'd be glad to hear from your experiences. :) > > Best regards > Dennis > -- Dennis Müller, B.A. Universität Mannheim Universitätsbibliothek Digitale Bibliotheksdienste | Schloss Schneckenhof West | 68131 Mannheim Tel: +49 621 181-3023 E-Mail: dennis.mueller@bib.uni-mannheim.de Web: www.bib.uni-mannheim.de
Attachment:
signature.asc
Description: OpenPGP digital signature
- Follow-Ups:
- Re: [EP-tech] .docx Export
- From: Dennis Müller <dennis.mueller@bib.uni-mannheim.de>
- Re: [EP-tech] .docx Export
- References:
- [EP-tech] .docx Export
- From: Dennis Müller <dennis.mueller@bib.uni-mannheim.de>
- Re: [EP-tech] .docx Export
- From: John Salter <J.Salter@leeds.ac.uk>
- Re: [EP-tech] .docx Export
- From: Dennis Müller <dennis.mueller@bib.uni-mannheim.de>
- [EP-tech] .docx Export
- Prev by Date: [EP-tech] Linkcheck: HEAD method ends up in 404
- Next by Date: Re: [EP-tech] .docx Export
- Previous by thread: [EP-tech] Sort view with creators_name and corp_creators
- Index(es):