How to Convert RoboHelp To DITA XML
When Converting RoboHelp Files, Follow These Steps:
- Prepare your Robohelp® project
- Prepare your zip file for upload (Option 1: zip the entire Robohelp project folder; Option 2: zip all HTML, XPJ, HHC, GLO and CSS files)
- Specify the DITA target
- Prepare a Migrate Rule set
- Convert your content to DITA XML
- Review your DITA using an XML editor
- Refine the DITA conversion by updating the rule set if necessary
Converting a RoboHelp® project to DITA is easier than you might think. Tasks, troubleshooting topics, cross references, reusable content, glossaries, conditional text, and folder structures are all accurately converted. Using rules to leverage the visual cues in the document to discern its implicit structure, Migrate will produce valid DITA XML output within a few minutes. The same set of rules can convert similar documents, and an online rules editor lets you modify the conversion so that little to no pre- or post-conversion cleanup is required.
Migrate can handle a large range of source formats including Word, FrameMaker, RoboHelp, DocBook, InDesign, Flare, and XML/SGML/HTML.
WEBINAR | Converting RoboHelp Content to DITA XML
Recorded on Wed, July 29, 2020
Our Presenter:
Helen St. Denis | Conversion Services Manager
RoboHelp projects are typically quite large. Too large for manual conversion to be feasible. But there’s also generally a lot more to your RoboHelp content than just the text. What about build tags, for example, for multi-channel publishing? Can your folder structure be maintained? What about snippets, can we retain the reuse there? These are the sorts of questions we are frequently asked. We’ll show you how we answer these and more.
Don’t worry if you can’t make the scheduled time, we’ll be sharing the recording with everyone who registers following the live broadcast.
How to Convert HTML To DITA XML
When Converting HTML Files, Follow These Steps:
- Prepare each document in HTML format
- Prepare an “index.html” file containing links to all the HTML files that need to be converted
- Zip the index file, the other HTML files, and the image folder together and upload the zip file to Migrate to be analyzed
- Specify the DITA target
- Prepare a Migrate Rule set
- Convert your content to DITA XML
- Review your DITA using an XML editor
- Refine the DITA conversion by updating the rule set if necessary
Converting HTML files to DITA XML can be a simple process with Stilo. This can be achieved by applying built in annotations and adding rules to leverage the visual cues in the document to discern the implicit structure. Then with little or no preprocessing and postprocessing, Migrate will produce a valid DITA XML output within a couple minutes. The same set of rules can convert all documents that follow a similar template.
Migrate can handle a large range of source formats including Word, FrameMaker, RoboHelp, DocBook, InDesign, Flare, and XML/SGML/HTML.
How To Build Fast-Flow Content Conversion Pipelines With OmniMark
OmniMark Fast-Flow Content Conversion Pipeline Components:
- Parsers. OmniMark includes parsers for many common data formats, including XML, SGML and RTF. You can also write custom parsers using OmniMark script.
- OmniMark Script. For creating your own filters, parsers, validators and business rules, OmniMark provides a high-level scripting language designed for creating content conversion components that operate in a streaming pipeline environment.
- Multiple Inputs. An OmniMark conversion pipeline can integrate content from multiple sources into a single content stream. Supported scenarios include combining similar content from different suppliers or enriching content with data drawn from corporate databases on the internet.
- Filters. OmniMark includes a number of pre-built filters for common content conversion operations. You can use these filters in your pipelines or use them as templates for developing your own filters.
- Multiple Outputs. An OmniMark pipeline can be split to send output to two or more different destinations. Support scenarios include the output of the same content to multiple formats, and splitting a single content stream into two different streams with different content in each.
- Database Interface. OmniMark can pull data from or send data to most popular databases.
- File System Access. OmniMark provides complete access to local networked file systems.
Enabling Organizations To Meet Critical Demand
Large organizations today need to process increasing volumes of content, including corporate data, office documents, plain text and markup (XML, SGML, HTML), for delivery to enterprise information portals or supply chain partners.
When you need to acquire content from multiple sources, and convert, transform, validate and integrate it into your mission critical business systems, the processing of that content can rapidly become a major business issue.
Processing bottlenecks can develop within enterprise information architectures that are designed to provide real-time delivery of content to hundreds, or possibly thousands of online users. When you need to modify your system to handle new content types or integrate new business rules, and processing volumes increase substantially, bottlenecks can increase and system performances can rapidly deteriorate.
Building high-performance content conversion solutions requires specialist content engineering skills, supported by specialist processing tools.
Event-Based Parsing
With conventional tools, there is little more you can do to optimize the development process and/or the overall conversion time. With OmniMark, however, there is another option. OmniMark allows you to create conversion pipelines which can be broken down into smaller steps without the need to serialize and parse the data between each conversion step.
Like some other tools, OmniMark uses an event-based parsing approach. Unlike other tools, however, OmniMark allows you to combine multiple parsing sources in a common parse event stream, and to generate parse events at each stage in the pipeline. Because each filter in the pipeline can catch incoming parse events and insert new parse events into the parse event stream, there is no need to serialize data between filters, which means the pipeline runs faster and uses fewer resources.
Solving the Time Crunch
Because there is no need to serialize and parse between each step, you can break the process down much more finely, which keeps each filter as simple as possible and allows you to build a library of reusable filters. This helps you to maintain and update your conversion pipeline with minimal effort and disruption.
Because OmniMark is a full-feature content processing platform, there is no need to use different programming languages for different parts of the process. All the capabilities you need for the content processing are present in OmniMark. Taken together, these features provide the solution to the content conversion time crunch: rapid development execution add up to rapid completion of the content conversion.
The OmniMark Solution
OmniMark allows developers to build efficient content conversion pipelines that support the rapid insertion of multiple content filter elements without loss of processing speed. Organizations can easily create purpose-built conversion pipelines that enable them to convert structured, semi-structured and unstructured content, even content that is unique to their business in either it’s format or meaning.
The modular nature of the OmniMark pipeline architecture means that content conversion specialists can develop plug-and-play conversion modules that can be swapped into the pipeline architecture as needed, with confidence, and without impacting the flow of the working pipeline.
OmniMark offers outstanding speed, scalability and stability, regardless of the format or semantics of the content being processed or the business rules that are applied during processing. It is the superior performance for high volumes, time sensitive content conversion environments, that sets Omnimark apart.
How to Convert FrameMaker To DITA XML
When Converting FrameMaker Files, Follow These Steps:
- Prepare your document in FrameMaker MIF format
- Upload your document to Migrate for analyzing
- Specify the DITA target
- Prepare the Migrate Rule set
- Convert your content to DITA XML
- Review your DITA using an XML editor
- Refine the DITA conversion by updating the rule set if necessary
FrameMaker is widely used for writing and editing complex structured or unstructured documents. At Stilo, by applying built in annotations and adding rules to leverage the visual cues in the document to discern the implicit structure, without preprocessing and postprocessing, Migrate will produce a valid DITA XML output within a few minutes. The same set of rules can convert all documents that follow a similar template.
Migrate can handle a large range of source formats including Word, FrameMaker, RoboHelp, DocBook, InDesign, Flare, and XML/SGML/HTML.
WEBINAR | Converting FrameMaker Documents To Good, Usable DITA
Recorded on Wed, June 17, 2020
Our Presenter:
Helen St. Denis | Conversion Services Manager
Whether your legacy content is in structured or unstructured FrameMaker, there’s a lot more to this content than just the words on the page. You may have conditional text, variables, or text insets, that allow you to reuse content. You may have index terms, cross references and footnotes. You want to be able to retain the usefulness of these features, and even to enrich the content in other ways, as part of your conversion process, rather than after the fact. We’ll show you how you can do just that with Stilo Migrate.
Don’t worry if you can’t make the scheduled time, we’ll be sharing the recording with everyone who registers following the live broadcast.
How to Convert Word To DITA XML
When Converting Word Files, Follow These Steps:
- Prepare your document in MS Word format
- Upload your document to Migrate for analyze
- Specify the DITA target
- Prepare a Migrate Rule set
- Convert your content to DITA XML
- Review your DITA using an XML editor
- Refine the DITA conversion by updating the rule set if necessary
One of the things authors love about Microsoft Word is that it’s easy to make your content look just the way you want it. This does not always lend itself to a straightforward conversion to DITA XML. Fortunately, at Stilo, we can leverage the visual cues in the document to discern the implicit structure of the content with rules. The same rules can convert all documents that follow a similar template. Without preprocessing and postprocessing, Migrate will produce a valid DITA XML output within a few minutes.
Migrate can handle a large range of source formats including Word, FrameMaker, RoboHelp, DocBook, InDesign, Flare, and XML/SGML/HTML.
2019 Accounts Now Available
We are pleased to announce that the 2019 Accounts are now available and a PDF copy will be emailed directly over the coming days to all those shareholders who have registered with us on or before 30th April 2020.
If you are an existing shareholder and would like to otherwise request a copy of the accounts, or have follow-up questions that you would like to raise, then please contact us at [email protected].
How To Solve The Content Processing Challenge With OmniMark
OmniMark Solves The Content Processing Challenge By:
- Scalable Streaming Architecture. Faster than alternative approaches for processing content and requiring far less memory and system resources to complete processing tasks.
- Rules-Based Model. Proven to be the most effective model for handling the complex nature of content processing applications, and allows rapid development of functional applications.
- Powerful Pattern Matching. Optimized for efficiency and tightly integrated with markup processing.
- Context Management. Enables a hierarchical approach to processing content, making applications efficient, scalable and maintainable.
- Full SGML/XML. Support and Content Validation OmniMark has built-in SGML/XML markup parsers, with XML processing an integral part of the platform such that it is handled transparently for the developer.
The Content Processing Challenge
All large organizations today need to process ever increasing volumes of content in all its forms, including data, plain text, hypertext and markup (XML, SGML, HTML), for delivery to enterprise information portals or supply chain partners. When content needs to be acquired from multiple diverse sources, converted, validated, integrated and transformed, the processing of that content rapidly becomes very complex, and a major issue for many organizations. Processing bottlenecks can readily occur within enterprise information architectures that need to ensure the real-time delivery of content to hundreds, or possibly thousands of online users. When systems need to be modified or maintained, and processing volumes increase substantially, the situation can rapidly deteriorate. Building high-performance content processing solutions requires specialist content engineering skills, supported by specialist content processing tools, seamlessly embedded within enterprise information architectures.
The OmniMark Solution
OmniMark has been built from the ground up to provide content engineers with a high-performance content processing platform able to support the most demanding content processing applications. It has evolved from being a domain specific, text processing language used for processing marked-up files and unstructured text, to become a single, integrated content processing platform featuring a wide range of connectivity and integration capabilities. OmniMark is able to process content from any source and deliver precisely-tailored information, on demand, to everyone who needs it. Increasingly this means streaming content into other applications, where specialized tasks are performed in specialized environments.
Open Standards
The ability to seamlessly combine pattern-based text and data processing with structured markup parsing allows developers to create powerful hybrid applications. When it comes to XML, OmniMark supports well-formed and schema-based parsing, being equipped with both a built-in XML parser and an interface to external parsers. SGML is fully supported including the latest amendments to the standard that were made to accommodate the adjustments needed by XML. OmniMark supports the W3C XML Schema via an External Parser Interface (EPI). The EPI also allows other types of XML Schema to be directly supported in OmniMark’s Markup Processing domain, including non-XML or customer-specified XML protocols. An XSLT processor is integrated for performing specific markup processing tasks or when working with small XML instances and applying multiple views to the same content.
Connectivity and Integration
Broad connectivity and communication options allow OmniMark to interact with other applications via application program interfaces (APIs) and user interfaces. Most major networking protocols are supported, including TCP/IP, HTTP, HTTPS, FTP and mail (POP3 and SMTP). Data sources and sinks may be accessed transparently via URLs, whether they are on a local machine, corporate network, or public internet.
In addition, OmniMark supports sophisticated high-level database access via ODBC and XQuery. It has extensive support for the native Oracle Call Interface 11g. It also includes directory connectivity via LDAP. OmniMark functionality can be extended through its SDK to support other emerging protocols and specific APIs.
How to Convert Complex Table Structures To DITA XML
When Converting Complex Tables, Follow These Steps:
- Prepare your document with tables in one of the following formats: MS Word, FrameMaker, Robohelp, InDesign, HTML, XML, Flare, etc.
- Upload your document to Migrate for analyze
- Specify the DITA target
- Prepare a Migrate Rule set
- Convert your content to DITA XML
- Review your DITA using an XML editor
- Refine the DITA conversion by updating the rule set if necessary
Converting complex table structures to DITA XML can be challenging. Fortunately, it is easy to convert complex tables automatically using Stilo’s Migrate.
Tables are often used to represent tabular information or used to lay out content on a page in a way that makes it easier for the reader to understand. This can create table representation that is very complex.
Examples of tables Migrate can convert include:
- Complex tables with merged cells
- Tables with steps or notes
- Definition tables or tab separated tables
- Tables need to switch columns or need to be stripped