The "HTML-to-RTF Pro DLL" component can convert HTML and ASP files into good-looking RTF with tables or transform tables to text. An output rtf file is smaller than input HTML.
The DLL component doesn't require Microsoft Word or any other word-processors.
Once embedded, the component enables the application to convert HTML, XHTML to RTF, DOC and plain text in ASCII or Unicode, exporting webpages in English and non-English languages, such as Japanese, Chinese, Korean. The original file can be uploaded into the application via form based file upload or via the form where the user needs to enter the URL address of the webpage to convert.
With HTML-to-RTF Pro DLL .Net, we are delivering a ready-to-use solution that enables developers of document management and Internet applications to focus on their core competencies, rather than spend time on creating their own solutions from scratch.
‘HTML-to-RTF Pro DLL .Net’ can be integrated into any application designed for Microsoft Windows, Linux, and Mac. The component requires Microsoft .NET Framework 1.1 or higher |
Key Features
The component converts XHTML, HTML documents to RTF, DOC and plain Text with support of:
- All HTML tags
necessary to make exact RTF analog
- A, B, BASE, BLOCKQUOTE, BODY, BR, CENTER, DD, DIV, DL, DT, EM, FONT, FORM, Hx, HEAD, HR, HTML, I, IMG, INPUT, LI, LINK, OL, P, PRE, SCRIPT, SELECT, SMALL, SPAN, STRONG, SUB, SUP, TABLE, TD, TEXTAREA , TH, THEAD, TITLE, TR, U, UL
- Font face, color and size attributes
- CSS
- CSS styles can be located inside HTML between <style>...</style> tags
- CSS styles can be stored in local *.css file and linked to HTML/XHTML
- CSS styles can be located in Internet/Intranet *.css file and linked to XHTML/HTML file
- Full text formatting: bold, italic, underline, strike, superscript and subscript
- Text indents
- Tables and nested tables
- Images in GIF, JPEG, BMP and PNG formats
- Imaged can be local or located in Internet/Intranet
- Images will be downloaded and stored inside DOC, RTF document
- Unicode support
- The component understand Japanese, Chinese, Korean , Cyrillic, etc
- Hyperlinks
- Special characters, such as & <, � - ÿ 	 - я etc.
- Page, text and table alignment
|
Click here to download the HTML-to-RTF Pro DLL .Net
(for C#, VB.Net, J#, ColdFusion, ASP.Net)
The trial version is complete functional and differs from full only that:
Converts only first 100,000 symbols
Can be used only for evaluating and testing |
$239 |
|
|
We offer three types of our DLLs (COM, Win32), so developers can use it from Visual Basic, C#, VBA, VB.Net, Delphi, Java, C++ or other language.
Component has methods for converting strings and files, it takes HTML string and returns RTF string or you can use it for working with files.
The component will help developers to streamline the development of word processing, document management, and Internet research software, cutting down the time developers spend on programming their own conversion technologies
|
a. Does the license provide royalty free use of components?
To contents
Yes, all licenses have royalty free basis of using our components.
b. What's the difference between developer and server licenses?
To contents
First of all, "Server License" is necessary only for developing Web-applications, for example ASP.Net.
If you are developing Windows Forms, Console or Desktop applications take a look only at the first part of license name "1 Developer ...", "4 Developers ...", "Site License ..."or "Source Code License ...". Don't care about number of "N Server Licenses", they are for ASP.Net apps. For example, if you are standalone developer the best way for you is "1 Developer ... License". If you are company and you have several developers who will work with the component choose between "4 Developers ..." and "Site License ...".
Regarding "Server License", it allows to deploy Internet applications with our component. For example, if you want to deploy your applications with our component on two production servers - the best choice is purchasing "1 Developer and 2 Servers License".
c. What's the difference between “1 Developer and 1 Server” and “1 Developer and Unlimited Servers” licenses?
To contents
Both licenses allows a single developer to develop unlimited number of WinForms and Web applications. But "1 Developer and 1 Server License" allows to deploy the component only at on production server. Another license doesn't have any limits of production servers.
d. How I can use "Source Code License"?
To contents
The Source Code is not for distribution, you can use only for development: including into your applications instead of dll file, bug fixing, own improvement of the component. You can't use it to create competitor product.
e. We'd like to redistribute your component as part of a Windows Forms application, what sort of license would be required?
To contents
So, if you plan redistribute our component with WinForms applications take a look only at the first part of license name "1 Developer ...", "4 Developers ...", "Site License ..."or "Source Code License ...".
Don't mind at number of "N Server Licenses", they are for ASP.Net apps.
All of our developer licenses are valid to redistribute the component with unlimited number of WinForms applications.
For example, if you are standalone developer the best way is "1 Developer ... License", if you are company and you have several developers who will work with dll choose between "4 Developers ..." and "Site License ...".
f. My company is looking at purchasing your component, that will be installed on one of our productions servers. We will also need a license for the developer in order to make additional changes to our application. I need to verify which license type we will need?
To contents
In my view the "1 Developer and 1 Server License" is enough for your needs. It covers a one developer and one server. We don't count testing servers.
g. We have an ASP.NET application and we are planning to use it for our system, we are software company that sell applications for different clients, do we have to buy your component just once or we have to purchase a different license for each of our clients?
To contents
If only one developer in your company will work with the component: you may purchase "1 Developer and 1 Server License". For each new client you will need extra "1 Server License" because it's ASP.Net application. But you may purchase "1 Developer and Unlimited Servers License" to cover unlimited number of production servers and clients.
h. For what purposes I can use "1 Server License"?
To contents
This license is necessary to deploy the component with your apps on additional production server.
i. Is it possible to upgrade one license to another?
To contents
Yes, sure it's possible. For example, you have "1 Developer and 1 Server License" and want to upgrade it to "1 Developer and Unlimited Servers License". Your steps:
Email us at sales@sautinsoft.com with mention about upgrading
We'll send you a link to pay difference between licenses cost |
