中国最专业的商业控件服务网

慧都控件网

节假日值班电话:023-66090381
product
最经典Silverlight控件套包助你打造酷炫的Web应用程序

寻找一款类似word的文档编辑控件

您好!根据您的需求,我们为您推荐一款.Net文档处理控件——Aspose.Words,该控件支持生成,更改,转换,渲染和打印文档,并可以通过编程创建,修改,提取和替换所有的文档元素包括章节,页眉,页脚,段落,列表,表格,文本,字段,超链接,书签和图像,可以很好的满足您的需求。

请推荐html->PDF, Word->PDF的好产品

根据您的需求,我们建议结合Aspose.PdfAspose.WordsAspose.PDF.Kit三个产品来使用,可以达到您所描述的需求。

上一个 上一个 Aspose.Cells 下一个 下一个Aspose.Slides
Aspose.Words
[产品编号: 10564 ]  
Aspose.Words

收藏订阅

  • 当前版本:v11   [销售以商家最新版为准,如需其他版本,请来电咨询]
  • 开  发 商:ASPOSE 独家代理
  • 产品类型:独立控件
  • 产品功能:Microsoft Office相关
  • 控件类型:.NET / JAVA
  • 其他特性:Windows Form
  • 产品源码:不提供源码
关于本产品的分类与介绍仅供参考,具体以商家网站介绍为准。
产品介绍 下载 购买 版本更新 开发商 视频与培训 评论(9)  
v8.1  Aspose.Words v8.0 (09-11-27) v6.6

Aspose.Words 版本更新 v8.0 (更新日期:11/27/2009)

What's New in Aspose.Words for .NET 8.0.0

  • Nested mail merge regions are supported.
  • Microsoft Word's mail merge settings and data source are preserved.
  • FlatOPC is supported.
  • Watermarks, background and WordArt are rendered to PDF, XPS and printed.
  • Print tickets are added to generated XPS with paper size, orientation and paper tray information.
  • DOCX to DOC and other formats conversion is improved. Many formatting loss issues resolved.
  • Many improvements in the OpenDocument Text (ODT) module.

Nested Mail Merge Regions

Yes, you now can just build a template document like this:

MERGEFIELD TableStart:Orders
...
MERGEFIELD TableStart:OrderDetails
...
MERGEFIELD TableEnd:OrderDetails
MERGEFIELD TableEnd:Orders

and then call

doc.MailMerge.ExecuteWithRegions(myDataSet);

and Aspose.Words will do its magic to produce an order document. Then you can of course

doc.Save(myStream, SaveFormat.Pdf);

etc.

Aspose.Words' support for nested mail merge regions allows you to generate reports from master-detail (parent-child) data with ease. If your data is inside a .NET DataSet object that has proper DataTable and DataRelationship objects set up, then all you need to do is pass a DataSet to the Aspose.Words mail merge engine. It will automatically figure out data relationships and generate a report with the required data. On the other hand, it is also easy to implement your own mail merge data source interfaces IMailMergeDataSource and IMailMergeDataSourceRoot to generate a report from any data source be it a LINQ query, XML file or a set of business objects. We will be writing more in the blog and in the documentation about this great new feature. This release is "nested mail merge V1.0" and includes only the features mentioned above. There is a lot more we plan to add to the reporting functionality in Aspose.Words in the future. Feel free to submit us your requests via the Support Forums.

Mail Merge Settings are Preserved

This might look like a small feature, but surprisingly it has been requested by many customers.

A Microsoft Word document can have a set of mail merge settings in it. These settings include the data source connection information, included/excluded recipients, mapped data fields and so on. Aspose.Words now preserves all this information in DOC, DOCX, WordML during load, save and conversions. You can also programmatically create or remove a Microsoft Word mail merge data source in a document. Programmatically creating a mail merge data source is great if you intend to give the document to users so they can insert merge fields into a document. Having a data source in a document will make the data source fields appear in a drop down box in Microsoft Word so the user will be able to insert them as "predefined" fields easily and without mistakes.

Flat OPC is Supported

An Office Open XML (OOXML) documents is a package that conforms to the Open Packaging Convention (OPC). Most of the OOXML documents you come across are DOCX files which are just ZIP files. The ZIP file is a container for an OOXML package. The Flat OPC format is an alternative way to package OOXML documents. A FlatOPC file is an XML document as opposed to a ZIP file. Aspose.Words now fully supports Flat OPC. Use the new LoadFormat.FlatOpc and SaveFormat.FlatOpc values to load, save and convert.

Watermarks, Document Background, WordArt Rendering

These features are of course essential for rendering of many business or official documents and we are happy to finally deliver them. All document watermarks, page background as well as WordArt text are now rendered to PDF, XPS and printing. WordArt with complex curves and gradients might be output in a simplified way, but still, in many cases it will look pretty much like in Microsoft Word.

DOCX to Other Formats Conversions and Rendering is Improved

"Font Calibri has changed to Times New Roman", "Font size has changed from 11 to 10", "Paragraph spacing is lost" and many others... Fixed! We have traced many of these issues down to some advanced features, such as document themes, document default formatting and also table styles were not fully supported in Aspose.Words during conversions. Aspose.Words for .NET 8.0.0 addresses many of these issues.

Breaking API Changes

There are some minor breaking API changes in Aspose.Words for .NET 8.0.0:

  1. Classes CompatibilitySettings, ViewOptions, ZoomType, ViewType, WriteProtection have moved from the Aspose.Words to the new Aspose.Words.Settings namespace. These classes are rarely used and if you experience a compilation problem, just add "using Aspose.Words.Settings;" to the source file.
  2. The IMailMergeDataSource interface has a new method GetChildDataSource added. This change will only affect you if you have implemented a custom mail merge data source. It is easy to resolve, just add the GetChildDataSource method to your implementation and return null.

All Fixes

Issue ID Type Desc Component Summary
10829 Bug DOC “System.ArgumentException” occurs during rendering to PDF and image
3747 Bug DOC Date format “hh:mm AM/PM” does not work correct during mail merge.
6392 New Feature DOC Preserve Mail Merge Data source during open/save in DOC
5312 Bug DOCX Cell background color is lost after converting DOCX to DOC.
5313 Bug DOCX Font is changed from Calibri to Times New Roman after converting DOCX to DOC.
5951 Bug DOCX SpaceAfter is not imported from DOCX
6016 Bug DOCX Background of table cells is missed.
6102 Bug DOCX Paragraph Spacing After is not correct after open/save DOCX.
6430 Bug DOCX Default font is not considered for paragraphs having default paragraph style (PDF, HTML)
7100 Bug DOCX Table formatting is lost upon DOCX import.
10921 Crash DOCX "FileCorruptedException" exception occurs upon openning DOCX file.
10751 New Feature DOCX Preserve Mail Merge Data source during open/save in DOCX
8825 New Feature DOCX Support The Flat OPC Format (Word 2007 XML).
7042 Bug Layout Some table rows become taller in layout
10705 Bug MailMerge Format of numbers is improper upon mail merge.
10811 Bug MailMerge Caps switch does not work with uppercase text.
11189 Bug MailMerge Numbers becomes rounded after mail merge.
11250 Crash MailMerge “InvalidOperationException” exception occurs during mail merge.
11027 New Feature MailMerge “NullReferenceException” exception occurs if remove merge field upon Mail Merge process.
39 New Feature MailMerge Support nested regions in mail merge
5170 New Feature MailMerge Make it possible to specify MailMergeDataSource for a document.
7580 New Feature MailMerge Make it possible to remove a connection from the mail merge data source settings in the document
10549 Bug MHTML Multipart boundary is not recognized if contains spaces
10628 Bug Model Conditional expressions without white space before comparison operator cannot be evaluated.
10809 Bug Model DOCPROPERTY field value is incorrect after updating fields.
10810 Bug Model DOCPROPERTY field in the footer is not updated.
10927 Bug Model Only part of field IF value is shown after updating fields.
10928 Bug Model Comma as decimal separator causes problems upon updating formula fields.
6815 New Feature Model White spaces ata the beginning and at the end are missed from DocumentProperty value.
7676 New Feature Model Add method that will remove SmartTags from the document, preserving content.
9202 New Feature Model Show document title as “Document Name” when print the document.
10530 Bug ODT Unnecessary styles of paragraphs and spans for headers and footers
10531 Bug ODT Text style of a hyperlink are not imported
10532 Bug ODT The shape background color is imported as blue when it is not set
10533 Bug ODT Span parent style should not be exported if it is paragraph style
10635 Bug ODT Ellipse content is not imported:
10636 Bug ODT "style:text-properties" element is exported empty when locale string is "none"
10637 Bug ODT "style:paragraph-properties" element is exported empty when paragraph.ParaPr.Shading.BackgroundPatternColor is empty
10638 Bug ODT Paragraph is exported inside paragraph when shape inside shapes group and paragraph inside shape
10639 Bug ODT Color of a background is imported incorrectly when colors "style:graphic-properties" -> "draw:fill-color" and "style:graphic-properties" -> "fo:background-color" are set
10640 Bug ODT Frame is exported empty when image has no data and is not link
10658 Bug ODT Run properties are not imported for line, rectangle and ellipce
10662 Bug ODT "style:text-properties" element of paragraph style is not imported when paragraph is list item in annotation
10665 Bug ODT "style:section-properties"->"style:columns"->"style:column"->"style:rel-width" do not coincide after export-import-export
10677 Bug ODT Unnecessary span style is exported when run contains '\r'
10690 Bug ODT Unnecessary list level style is exported when list style name contains "_20_"
10691 Bug ODT Attribute "draw:stroke-dash"->"draw:style" is not imported and styles names of "draw:stroke-dash" are not unique after export
10692 Bug ODT Empty spans are exported when field type is FieldType.FieldNone or FieldType.FieldCannotParse
10693 Bug ODT "style:paragraph-properties" element is exported empty
10719 Bug ODT "System.InvalidCastException: Unable to cast object of type 'Aspose.Words.Style' to type 'Aspose.Words.TableStyle'" during import DOCX -> export ODT -> import ODT -> export DOCX
10731 Bug ODT Unnecessary "style:text-properties"->"style:font-size-asian" attribute after export ODT->import ODT
10754 Bug ODT Paragraph alignment is imported/exported incorrectly when writing mode is "rl-tb"
10755 Bug ODT List level parent style is not imported
10779 Bug ODT "style:graphic-properties"->"style:horizontal-rel="page"" is exported incorrectly
10780 Bug ODT Attribute "style:graphic-properties"->"draw:color-mode="mono"" is not imported
10781 Bug ODT Transparent color is not imported for "style:graphic-properties"->"fo:border-top="transparent 0.088cm solid" attribute
10782 Bug ODT Error of rounding in "style:graphic-properties"->"svg:stroke-width" and "style:graphic-properties"->"draw:shadow-offset-x"  attributes export
10783 Bug ODT Unnecessary inverted commas in value of field "text:database-display"
10785 Bug ODT Font size is incorrect in ODT, when DefaultParagraphFont is defined.
10976 Bug ODT Error of rounding in "style:header-footer-properties"->"fo:min-height" and "style:header-footer-properties"->"fo:margin-top" attributes
10977 Bug ODT Incorrect elements inside a "text:database-display" element after export (simple text only is supported inside a "text:database-display" element in ODT)
10978 Bug ODT Span inside span after export (it is not supported in ODT)
10979 Bug ODT "style:graphic-properties"->"draw:stroke" and "style:graphic-properties"->"draw:stroke-dash" elements are not imported
10980 Bug ODT "style:graphic-properties"->"draw:marker-start-width" and "style:graphic-properties"->"draw:marker-end-width" are exported and imported incorrectly
10981 Bug ODT Unnecessary "style:graphic-properties"->"draw:stroke="solid"" attribute after import/export
10982 Bug ODT "style:font-face"->"svg:font-family" is exported incorrectly
10983 Bug ODT Ellipse size is incorrect after import/export when ellipse inside a shapes group
10984 Bug ODT Parent style of shape is not exported when shape inside a shapes group
10985 Bug ODT Size and style of border are exported and imported incorrectly
10988 Bug ODT "meta:user-defined" element value is not imported when it contains white spaces only
11128 Bug ODT "style:drop-cap"->"style:length" is exported incorrectly
11134 Bug ODT Parent style is absent after import for "NoList" and "TableNormal" styles
11135 Bug ODT User style becomes built-in style after import when its name coincides with  built-in style
11150 Bug ODT Style with style family is "paragraph"  is exported as parent style of span style
11163 Bug ODT Parent paragraph style is exported as "Standard" when its name is empty and StyleIdentifier.User
11191 Bug ODT Unnecessary list item is exported when list item run contains paragraph break
11266 Bug ODT Unnecessary style:paragraph-properties->fo:margin-bottom attribute is exported when Paragraph.SpaceBeforeAuto is true
11309 Bug ODT Element "text:h" instead of element "text:p" after export-import-export
11329 Bug ODT Table located in header or footer is exported in "office:body" content when it is nested into table
11355 Bug ODT Unnecessary empty paragraph after import when "style:drop-cap"-> "style:length" is equal to  paragraph text length
11375 Bug ODT "style:table-properties"->"fo:margin-left" is exported incorrectly when row alignment is RowAlignment.Right
11377 Bug ODT style:paragraph-properties-> fo:break-before = "column" is not imported when paragraph is empty
11421 Bug ODT Crash when converting HTML to ODT
11436 Bug ODT Winword does not open ODT document when " manifest:media-type = "" " is absent
11448 Bug ODT Winword does not open ODT document when "text:note" element does not contain "text:note-citation" element
11505 Bug ODT Winword does not open ODT document when "text:a"->"xlink:href" attribute contains file name without path
9962 Bug ODT Left margin of table is incorrect after import from ODT and export to ODT
10534 New Feature ODT Add import config:config-item name = "ShowRedlineChanges"
10641 New Feature ODT Add import of attributes: "style:graphic-properties"->"draw:luminance", "style:graphic-properties"->"draw:contrast", "style:graphic-properties"->"draw:color-mode"
10778 New Feature ODT Add import of attribute  "style:graphic-properties"->"fo:clip"
10989 New Feature ODT Add "style:text-properties"->"style:text-rotation-angle" attribute import
11125 New Feature ODT Add export and import of shape group
11129 New Feature ODT Add "style:paragraph-properties"->"text:line-number" attribute import
10831 Bug Rendering System.ArgumentNullException occurs during rendering to PDF and image
10833 Bug Rendering System.NullReferenceException occurs during rendering to PDF and image
10996 Bug Rendering System.ArgumentNullException occurs during rendering to PDF and image
10999 Bug Rendering System.InvalidOperationException occurs during rendering
9899 Bug Rendering Paragraphs borders are misplaced a bit.
9901 Bug Rendering Line of test is missed upon rendering.
10851 Crash Rendering “IndexOutOfRangeException” exception occurs upon converting to PDF/XPS.
7114 New Feature Rendering Watermark shape is lost upon rendering and saving to PDF.
8497 New Feature Rendering Support Watermarks (basic WordArt) Rendeing/Converting to PDF.
915 New Feature Rendering Render page background color or shape
9222 Bug Rendering.PDF Use default font when the font does not exist.
10670 New Feature Rendering.XPS Add verification if image format is supported by XPS.
11157 New Feature Rendering.XPS Support paper tray when outputting to XPS
10667 Task Rendering.XPS Validate all XPS files using isXPS conformance tool.
10472 New Feature Samples Make a sample How to Print via XPS
11002 Bug WML Line break is missed during open/save

Aspose.Words for Java 3.3

Issue Type Component Summary
10032 Bug Model List labels are displayed improperly after inserting HTML.
10994 Bug HTML List labels regression issues
11422 New Feature Model Support mail merge settings in the API, DOC and DOCX
11197 Bug DOCX DOCX produced by Aspose.Words for Java is corrupted, if insert more than 995 images.