I am about to rewrite our internal Open Office Mail Merge Tool that combines an odt Template and a XML File into the resulting document. Currently it is a very hackish Open Office Macro and I would like to base it on a reasonable library.
The ooo_mailmerge utility bundled with OOoPy seems as if I could model my tool after it. I would change/extend it to consume XML and add some functionality to create basic tables.
Do you think this is reasonable? Any comments? Suggestions?
Best Regards
Michael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
On Sun, Sep 22, 2013 at 02:46:37PM +0000, Michael Nagel wrote:
Hi there,
I am about to rewrite our internal Open Office Mail Merge Tool that
combines an odt Template and a XML File into the resulting document.
Currently it is a very hackish Open Office Macro and I would like to
base it on a reasonable library.
The ooo_mailmerge utility bundled with OOoPy seems as if I could model
my tool after it. I would change/extend it to consume XML and add some
functionality to create basic tables.
Do you think this is reasonable? Any comments? Suggestions?
Yes, should work, thats one of the use cases ooopy was written for.
You may want to look into the doctests, in particular
ooopy/Transformer.py has some mailmerge tests.
If you want to do more than just field replacement, you will have to
code your own transform. See the Field_Replace transform in
Transforms.py how simple field replacement is implemented (the central
part of the mailmerge).
Ralf
Ralf Schlatterbeck email: ralf@zoo.priv.at
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi there,
I am about to rewrite our internal Open Office Mail Merge Tool that combines an odt Template and a XML File into the resulting document. Currently it is a very hackish Open Office Macro and I would like to base it on a reasonable library.
The ooo_mailmerge utility bundled with OOoPy seems as if I could model my tool after it. I would change/extend it to consume XML and add some functionality to create basic tables.
Do you think this is reasonable? Any comments? Suggestions?
Best Regards
Michael
On Sun, Sep 22, 2013 at 02:46:37PM +0000, Michael Nagel wrote:
Yes, should work, thats one of the use cases ooopy was written for.
You may want to look into the doctests, in particular
ooopy/Transformer.py has some mailmerge tests.
If you want to do more than just field replacement, you will have to
code your own transform. See the Field_Replace transform in
Transforms.py how simple field replacement is implemented (the central
part of the mailmerge).
Ralf
Ralf Schlatterbeck email: ralf@zoo.priv.at