2021.2
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Connect 2021.2
- Setup And Configuration
- System and Hardware Considerations
- Installation and Activation
- Where to obtain the installers
- Installation prerequisites
- User accounts and security
- Installing PlanetPress Connect on Machines without Internet Access
- Installation Wizard
- Running Connect installer in Silent Mode
- Activating a License
- Migrating to a new workstation
- Information about PlanetPress Workflow
- Upgrading
- Server Configuration Settings
- Known Issues
- Uninstalling
- General information
- OL Connect projects
- The DataMapper
- DataMapper basics
- Data mapping configurations
- Creating a new data mapping configuration
- Opening a data mapping configuration
- Saving a data mapping configuration
- Down-saving a data mapping configuration
- Using the wizard for CSV and Excel files
- Using the wizard for databases
- Using the wizard for JSON files
- Using the wizard for PDF/VT or AFP files
- Using the wizard for XML files
- Advanced PCL to PDF options
- Data mapping workflow
- The Data Model
- DataMapper User Interface
- DataMapper Scripts API
- The Designer
- Designer basics
- Web
- Capture OnTheGo
- COTG Forms
- Creating a COTG Form
- Filling a COTG template
- Sending the template to the Workflow tool
- Receiving and extracting data from a COTG Form
- Using COTG data in a template
- Designing a COTG Template
- Capture OnTheGo template wizards
- Using Foundation
- COTG Elements
- Using COTG Elements
- Testing a Capture OnTheGo Template
- Using the COTG plugin
- Dynamically adding COTG widgets
- Saving and restoring custom data and widgets
- Using submitted COTG data in a template
- Capture OnTheGo API
- Content elements
- Snippets
- Styling and formatting
- Personalizing content
- Preferences
- General preferences
- Clean-up Service preferences
- DataMapper preferences
- Database Connection preferences
- Editing preferences
- Email preferences
- Emmet preferences
- Engines preferences
- Hardware for Digital Signing preferences
- Language preferences
- Logging preferences
- Parallel Processing preferences
- Print preferences
- Project Wizards preferences
- Save preferences
- Scripting preferences
- Servers preferences
- Web preferences
- Writing your own scripts
- Script types
- Creating a new Standard Script
- Writing a script
- Setting the scope of a script
- Managing scripts
- Testing scripts
- Optimizing scripts
- The script flow: when scripts run
- Selectors in Connect
- Loading a snippet via a script
- Loading content using a server's API
- Using scripts in Dynamic Tables
- Control Scripts
- Post Pagination Scripts
- Translating templates
- Designer User Interface
- Designer Script API
- Functions and fields
- Example
- Functions and fields
- html()
- margins
- front, back
- Generating output
- Print output
- Email output
- Web output
- Generating Print output
- Generating Print output from the Designer
- Generating Print output from Workflow
- Print settings in a template
- Aborting content creation
- Print using standard print output settings
- Print Presets
- Print using Advanced Printer Wizard
- Adding print output Models to the Print Wizard
- Splitting printing into more than one file
- Print output variables
- Generating Fax output
- Generating Tags for Image output
- Generating Email output
- Generating Web output
- Optimizing a template
- Runtime parameters
- PlanetPress Connect Release Notes
- OL PlanetPress Connect Release Notes 2021.2.1
- License Update Required for Upgrade to OL Connect 2021.x
- Backup before Upgrading
- Overview
- OL Connect 2021.2.1 Improvements
- OL Connect 2021.2 Designer Improvements
- OL Connect 2021.2 DataMapper Improvements
- OL Connect 2021.2 Output Improvements
- Workflow 2021.2 Improvements
- OL Connect 2021.2 Improvements
- Known Issues
- Previous Releases
- OL PlanetPress Connect Release Notes 2021.1
- OL PlanetPress ConnectRelease Notes 2020.2.1
- OL PlanetPress Connect Release Notes 2020.1
- OL PlanetPress Connect Release Notes 2019.2
- OL PlanetPress Connect Release Notes 2019.1
- PlanetPress Connect Release Notes 2018.2.1
- PlanetPress Connect Release Notes 2018.1.6
- PlanetPress Connect Release Notes 1.8
- PlanetPress Connect Release Notes 1.7.1
- PlanetPress Connect Release Notes 1.6.1
- PlanetPress Connect Release Notes 1.5
- PlanetPress Connect Release Notes 1.4.2
- Connect 1.4.2 Enhancements and Fixes
- Connect 1.4.1 New Features and Enhancements
- Connect 1.4.1 Designer Enhancements and Fixes
- Connect 1.4.1 DataMapping Enhancements and Fixes
- Connect 1.4.1 Output Enhancements and Fixes
- Connect 8.4.1 Workflow Enhancements and Fixes
- Known Issues
- OL PlanetPress Connect Release Notes 2021.2.1
- Knowledge Base
- Legal Notices and Acknowledgements
The description is added to the <data-translate> attribute of the HTMLelement in which the
source text is located, as its value, for example: <data-translate="Table">.
Note that a translation will only be applied if the value of the <data-translate> attribute of the
respective HTML element is exactly the same as the given Context (case-sensitive).
Tagging text in snippets
If the text that you want to tag for translation is located in a snippet, do not tag it in the section
where the snippet is used. Instead, open the snippet (see "Snippets" on page741) and tag the
elements inside the snippet as described above.
Tagging text that is inserted by a script
OLConnect will also apply translations to content that is inserted by personalization scripts, but
only if that content is marked for translation, and if there is a matching translation entry.
1. On the Translations pane, click on the New Empty String button to create the translation
entry.
2. Make sure that any element in which the text is inserted, are tagged for translation. There
are several ways to do that:
l Let the script insert the tagged HTML element as well as the text, for example:
results.html( "<p data-translate>Bill to @CustNumber@</p>"
);.
l If the script inserts text into an existing, empty HTML element, switch to the Source
view and add the data-translate attribute to the element (e.g. <p id="p1" data-
translate>).
Data placeholders in translation entries
A translation entry may include placeholders for data fields, e.g. "Dear @name@". (For more
information about placeholders see "Variable Data" on page805.)
Placeholders must not be translated; otherwise the personalization script will no longer replace
them with data
Typically, translators are familiar with entries that contain variables, but you may add a
comment explaining that the placeholder is used as a variable and that it should not be
translated.
Page 940