Ok not a bad idea.
Most of the docs are contracts etc with images in them etc and usually a few
pages long. The end user ideally would adjust the doc/template with any new
changes and upload to the system and we would use that when doing the mail
merge.
I found this and is a good example of wh
It depends on the file template but at minimum you can use openoffice
CLI to connect to a running headless OO.org instance (or a cluster of
them in the cloud) to perform a conversion to a more maleable format and
then back again. I'd have to dig up the code for specifics, but it was a
pretty fu
On 02/02/2011, at 1:03 PM, Bodaniel Jeanes wrote:
> you might try using headless openoffice.org to make the changes.
That sounds like an interesting approach. How does this work exactly?
Josh
--
You received this message because you are subscribed to the Google Groups "Ruby
or Rails Oceania"
Michael,
Depending on how complicated the documents are (visually), you might try
using headless openoffice.org to make the changes. At Mocra, we actually
built an entire app (with the idea to SaaSify it eventually) that took
most common file formats and did mailmerge (using native mechanisms
On 02/02/2011, at 11:35 AM, Michael Cindric wrote:
> Have a requirement where we need to design a doc using word templates
> dot files or even word docs docx files and then mail merge the data in
> using place holders e.g {{first_name}},
>
> Now word templates are now just really zip files but ha
Hi Guys,
Have a requirement where we need to design a doc using word templates
dot files or even word docs docx files and then mail merge the data in
using place holders e.g {{first_name}},
Now word templates are now just really zip files but having no end of
issues when l try to unzip merge in d
