How to reduce DTP and translation costs with FrameMaker

This document provides an overview and agenda for a training session on SAP Business Planning and Consolidation (BPC). It introduces key concepts in BPC including the architecture, dimensions, applications, and development methodology. The session will cover creating dimensions and applications, loading and validating data, and using BPC for reporting and planning. It also provides an overview of the fictitious company PetDepot and its requirements for the BPC implementation.

The document discusses modeling and the benefits of modeling complex systems. It notes that modeling helps visualize, specify, guide construction of, and document systems that would otherwise be too vast to comprehend. The importance of modeling increases as systems increase in scale and complexity. Modeling allows for simulating "what if" scenarios to help with early verification and validation. The document discusses how modeling enables the development of things as complex as software systems with millions of lines of code and global deployments.

This document summarizes a research study on data collection and analysis of programming language semantics. It discusses several key programming languages like C++, C, Pascal, Fortran, Java, Perl, PHP, and Scheme. It analyzes the features and usage of these languages. It also compares Python and R as good options for beginners in data science and discusses why Python may have a lower learning curve. Finally, it discusses the importance of incorporating semantic results into practical systems to help language designers and programmers better understand languages.

The document summarizes the Interaction Flow Modeling Language (IFML) submission. It discusses the objectives of IFML in modeling user interfaces, interaction flows, and backend integration. It provides an overview of the IFML metamodel, concrete notation, proofs of concept, and coverage of requirements. The submission is from multiple organizations and aims to standardize modeling user interfaces and interactions.

This document proposes developing domain-specific testing languages for software-as-a-service to raise the level of abstraction in software testing. It describes Ultimate Software's challenges testing their cloud-based human capital management solution and their approach to address these. This involves creating domain models, test commands, and configuration models. A prototype was developed as a Visual Studio extension called Legend to author tests using these abstractions. Lessons learned include the importance of configurable testing frameworks and cross-functional collaboration to build domain models.

This document summarizes Fabien Pinckaers' presentation at the OpenERP Community Meeting in 2013. The presentation outlines OpenERP's status, challenges, and ambitions. It discusses the roadmap for new features in version 8, including improvements to accounting, CRM, projects, human resources, and other modules. It also covers plans to transform the frontend and disrupt the CMS and e-commerce market. The goal is for OpenERP to become the worldwide leader in management software.

Ravikumar has over 20 years of experience in core banking solutions, including product development, customization, and implementation. He has worked as a technical architect, product manager, and delivery manager for a major banking software company, managing teams and leading projects for clients. Ravikumar has extensive expertise in technologies like Java, Oracle, and core banking functions such as deposits, lending, and account management.

This is the slideshow presentation used by Kipal Verma, Adobe FrameMaker Product Manager during the EU and USA Launch Events

Sometimes, a spontaneous road trip can be a lot of fun, as long as you’re willing to take the good with the bad—getting lost, car trouble, unfriendly (or just plain weird) natives, bad diner food. Usually, though, the most successful trips involve planning, roadmaps, and best of all, guidance from people who’ve already been there. The journey from traditional, deliverable-centric content creation to DITA-based content creation falls into this second category. In this session, we talk about one small publication group’s experience moving to DITA, from the initial discussions to the successful implementation of a FrameMaker-based, end-to-end publication process. Here are some of the high points of the project; we’ll discuss our decision-making process and some of our technical approaches in detail in the session.

Presented at DocTrain East 2007 Conference by Brian Buehling, Dakota Systems -- Since its inception, DITA has rapidly gained acceptance as a standard document structure used in many XML-based content management and publishing systems. DITA is an XML schema developed primarily to support technical documentation for a wide array of applications. This session will cover the commonly used element, attribute and entity constructs that are defined in the schema. More importantly, recommendations concerning how best to implement DITA solutions will be given. Special attention is given to developing practical DITA applications since, in many cases, some DITA elements will have to be extended through a mechanism called specialization to produce a robust XML-based publishing system.

Using the DITA XML standard can bring enormous improvements in the efficiency of localizing documentation. Some organizations report efficiency gains of 30-50% over traditional desktop publishing systems, and use the savings to expand further into global markets. This session gives a practical set of steps and guidelines for delivering your content smoothly and quickly in multiple languages. We will cover how to mark up content, how localization affects reuse, how to work with translators, and issues in generating localized deliverables. You'll learn about the big picture of how translation works in DITA, what steps you need to include in your process in order to get high-quality results, and exactly how to avoid common pitfalls that tend to make localization tricky.

This document discusses implementing a customer-driven transition from unstructured content to DITA. It outlines challenges such as categorizing topics, minimizing rework, retaining formatting and references. It then describes the solutions implemented, including using scripts, stylesheets and read/write rules to automate the process and address issues in legacy content like references and graphics. The goal is a phased, customized approach to transition content while retaining important existing features through the process.

The document provides an overview and instructions for localizing templates using Domino Global Workbench 8.5. It discusses installing DGW 8.5, creating a glossary database and tag file to extract terms, marking terms as "Do Not Translate", sending the glossary for translation, and building localized templates using the translated glossary. Steps are also provided for localizing templates using DGW's properties version, which extracts terms to properties files instead of a glossary database.

This document discusses options for extracting deliverables from DITA content, including HTML and PDF output. For HTML, the DITA Open Toolkit is recommended due to its support for automation and customization with CSS or XSL. PDF output is more challenging to automate due to the complexity of page layouts. The DITA Open Toolkit can generate PDF but requires significant customization of XSL formatting objects. Alternatives like FrameMaker or InDesign offer more control over pagination but involve less automation. The best approach depends on an organization's priorities around typography, automation, and existing tools or templates.

FrameMaker and XMetaL each have strengths and weaknesses for DITA support. FrameMaker provides better print/PDF output and WYSIWYG editing, while XMetaL enables more direct DITA authoring and enforces valid XML structures. Specialization is easier in XMetaL, while FrameMaker allows more author flexibility. The best tool depends on an organization's priorities and publishing workflows.

Presented by Dave Holmes at Documentation and Training West May 6-9, 2008 in Vancouver, BC In 2006, Business Objects faced a major challenge. How to migrate over 50,000 pages of unstructured non-topic based documentation it had acquired through rapid growth and acquisitions. The answer was to use DITA to standardize content creation, management, translation and publishing processes company-wide. In this session, you will learn how they went from planning to publishing using an iterative approach, and how you can use this method to see the results of a content migration sooner in your project cycle.

This document discusses using DITA (Darwin Information Typing Architecture) for technical documentation. It recommends not being afraid of DITA, as people will love it for its benefits. DITA supports topic-oriented structuring, has a growing expertise and tool landscape. Challenges include how to start and structure content in DITA. The document provides suggestions for both technical documentation experts and others on how to start and structure content in DITA. It also discusses complete tool solutions and reasons why people love using DITA for its multiple output capabilities and less maintenance compared to working in isolation.

1. The document discusses Blackbaud's multi-year plan to implement structured documentation using XML and FrameMaker. It overviews why the change was needed, why structure was chosen, and the training and steps involved in getting started. 2. Key aspects of the transition included selecting a core team, training with an outside firm, creating EDD and DTD files, and gradually introducing more writers while piloting the new process on small projects before taking on a large enterprise project. 3. The document provides advice on training, analyzing content, designing documentation, and generating output from the structured XML files. Challenges included the time, cost and difficulty of learning structured authoring.

Presented by Thomas Aldous at Documentation and Training East 2008, October 29-November 1 in Burlington, MA. This session is for anyone that is interested in learning how to manage a transition to Specialized DITA including Content Management Systems, Editors and Publishing Server issues and resolutions. As a added bonus, we will also convert an Word Document To Specialized DITA and edit the content is FrameMaker 8. There will be a question and answer period at the end of the session for both technical and project management issues.

breakdown of the most commonly used pdf libraries in rails projects,and an in depth review of prawn example pdfs and code can be seen at prawn.heroku.com More info at www.RailsPerformance.com

No matter your preference for OOXML, ODF, or PDF … the document standard requirements are going to become a fact of life for users of IBM Lotus Notes & IBM Lotus Domino in the next year. This sessoin will review the technical capabilities of all three formats and how they work with Lotus Software. We will check the format debate at the door and look at which format will provide you the functionality you need. We will then look at how you can generate all three documents from your applications using third-party tools and custom code. You will take home samples that allow you to export Lotus Notes data to OOXML, ODF, and PDF in LotusScript and Java – be prepared for a deep dive into code!