Dear Aspose team, i have following problems, I dont know if it’s simple a incovenience of Word for Mac or an aspose problem. 1) When I create an empty word document with aspose, setting a rtf document as mailmerge datasource with aspose functions and open the word document in Word for Mac 2011 the datasource is ignored completely. Under Word for Windows everything is perfect.
2) When I set with aspose functions a rtf document as mailmerge datasource to a word document which was onced saved with Word for Windows (no matter what version or doc or docx) and try to open the word document with Word for Mac 2011 it can not regnonize the datasource. In both cases if I set in Word for Mac 2011 the mailmerge datasource with Word there is no problem and the rtf document is accepted as datasource. Can you help?
Aspose.Words for Java It supports content & formatting manipulation, mail merge abilities, ActiveX controls and support of DOC, DOCX, DOCM, DOTX, DOTM, HTML and XHTML formats Aspose.Words is a Java word processing component to read, write, modify & convert Word documents.
Thanks a lot! Kind regards, Jens Boeckel - Abacus Research AG Switzerland. Dear Adam, thanks for your reply. The delay doesnt matter. As attachment of this post you’ll find a zip file containing: - the word document generated with aspose and set datasource rtf - the word document created with Word for Mac 2011 and set datasource rtf - the rtf (.html) document used as datasource One idea I’ll have is the MappedDataFields we’ll set with the aspose library. It might help you finding the problem. Kind regards, Jens Boeckel - Software-Engineer Abacus Research AG Switzerland.
Hi Adam, thnx for your reply and I apologize for the long delay of my reply. To your topics: 1) csv is slightly better.
In an existing document with inserted mailmerge fields the datasource is regnonized. In a brand new document the datasource is not regnonized 2) Yes that would work but is no option for our solution, because we must set the datasource programmatically. 3) Document with datasource created in WordForWindows cant be opened in WordForMac because Word save the absolut path of the datasource file and as you surly know the filesystem/structure on Mac is absolutly different. Cur unam on twitter just got cockpit for mac. In opposite direction the problem exists as well. So I cant really test the behaviour. Thanks again!
Kind regards, Jens Boeckel - Software-engineer Abacus Research AG Switzerland. Dear aspose team, I just tested the new version of aspose.words (thank you for your support getting a new trial licence!
The good news: with docx documents and Word for Mac 2013 everything is perfect. The bad news - with doc there are still two issues: 1) if a doc document gets a mailmerge datasource and it is opened with word for mac a dialog comes up that the columnscount of values and headers in datasource does not match (but the columncounts are identical). If I set the datasource in word for mac manually after the warning occured, everything is fine.
After that I can set the datasource with aspose and it still works. I saw that the document saved with word for mac is about 10K bigger than the original document (18K). 2) The preview of the mailmerge field /the mapping of datafields does not work anymore after setting the datasource manually. I attached the doc documents - before opening with word for mac - after saving it with word Maybe you can find out the difference and solve the problem Thanks a lot!
Kind regards! Hi Awais, I had to setup a corresponding rtf-datasource file to be able to open the document on Windows. With it I could open the out.doc on Windows. So I copied out.doc and the corresponding datasource file to a MAC. I tried to open it with MS WordForMac 11. Unfortunately the datasource is not regnonized.
(see printscreen 1.jpg). After pressing ok, the dialog in printscreen 1a.jpg is occuring.
Aspose.words For Microsoft Word
Another try in our mailmerge program produces the printscreens 2.jpg, 3.jpg and 4.jpg on Mac and MS WordForMac. I’m curious why the problems only occur with doc.
With docx documents we dont have any problems. Thank you a lot!
We are pleased to announce the first release of Aspose.Words for Mac via Xamarin (17.10). In future, regular monthly releases will be published. ‘Aspose.Words for Mac via Xamarin’ has full functionality of Aspose.Words for.NET with. This version also includes all bug fixes and public API changes made in Aspose.Words for.NET 17.10, see following release notes for more information. Aspose.Words for Mac via Xamarin is an advanced Word document processing API to perform a wide range of document processing tasks directly within your native Mac applications. You can integrate this API through Xamarin framework for Mac applications.
Aspose.Words for Mac via Xamarin API supports DOC, OOXML, RTF, HTML, OpenDocument, PDF, XPS, EPUB and other formats. You can generate, modify, convert and render documents. Aspose.Words for Mac via Xamarin Resources Following are the links to some useful resources you may need to accomplish your tasks. (Aspose.Words for Mac via Xamarin is ported from Aspose.Words for.NET. So, you can use the same documentation).
(Aspose.Words for Mac via Xamarin is ported from Aspose.Words for.NET. So, you can use the same API Reference Guide).
Start a Free Trial Today Start a free trial today – all you need is to. Once you have signed up, you are ready to try all the powerful file processing features offered by Aspose. You can easily download ‘Aspose.Words for Mac via Xamarin’ API for evaluation. The evaluation download is the same as the purchased download. Please check.
The evaluation version of Aspose.Words for Mac via Xamarin (without a license specified) provides full product functionality, but it inserts an at the top of the document on open and save, and limits the maximum document size to several hundred paragraphs. If you want to test ‘Aspose.Words for Mac via Xamarin’ API without the evaluation version limitations, you can also request a 30-day Temporary License. Please refer to?