gebi / ooopy

OOoPy is a library in Python for inspecting, creating or modifying OpenOffice.org documents. It uses the existing ElementTree XML library by for manipulation of the OOo XML.
6 stars 1 forks source link

ooo_mailmerge: documentation of .odt requirements #5

Open WeeSee opened 6 years ago

WeeSee commented 6 years ago

We should make clear how a template has to be specified:

Is the best way to use variables, e.g. set variable keyInDocuemt = keyInCsvFile?

Is there a better way to get the variables from the csv file into the template?

What's the matter with your example Carta.odt: set variable Spett = Spett.le?

When trying to print or exporting the merged document to a pdf file, every merged value gets a value of 0. What am I doing wrong?

When a merged document should have multiple merged parts on one page (e.g. for label printing): how can we specify "go to next address"? In Open Office there is a <next record> function but that only works with databases. I don't know hot to enter this function without database - and we don't use a database in ooo_mailmerge

gebi commented 6 years ago

i've never used this part of the project...

It's just that the current upstream at sourceforge is dead since many years and even after multiple mails i didn't get any response, that's why i've effectively forked the project and created it here in github ;) and fixed up what i needed.

i've only every used ooo_fieldreplace for my tasks, but it seems we both wanted to achive similar goals. I created a small sample script that can load data from a yaml file (including default handling with a global section) and expands one .odt template file to multiple output files which are then batch converted to .pdf.

I've also only ever used simple single variable declarations and left all decisions to my python code.

WeeSee commented 6 years ago

oh, what a pity!

I'm desperately looking for a batch merging process based on open office files. just .odt and .csv - no python, no programming, no user interaction.