login | sign up

Your session has timed out due to inactivity.

You can go back to the overview without login or use the login form to login again before redirect

Knowledge Base / Getting Started with one2edit™ v3 / For Everyone

Glossary of Terms

Created on 08th December 2016 at 17:55 by Jamie O'Connell



In this Glossary of Terms, you will find the most important terms and definitions used within one2edit™.

NOTE:

It is especially important to understand the difference between a Master Document, a Version Document, and a Project. That is why these three terms are at the start of this glossary.

Asset Project

An Asset Project defines a number of things about where assets are held within a one2edit™ system.

An Asset Space is one thing that is defined by an Asset Project.

NOTE:

The Asset Project should not be confused with the standard Project.

Asset Space

An Asset Space is the portion of an Asset Project used for storage of assets.

A Project is created in one2edit™ from files that are located in an Asset Space.

The images that are linked to an Adobe® InDesign® document in one2edit™ are stored in an Asset Space.

Client Workspace

A Client Workspace is an area on a one2edit™ system to which specified users have access.

Users cannot see nor access any Client Workspace to which they are not explicitly assigned.

Projects and Jobs that are created within a Client Workspace are only accessible by those users in that Client Workspace (assuming their User Permissions permit such access).

A one2edit™ system must contain at least one Client Workspace, but may contain mutliple Client Workspaces.

Content Group

A Content Group defines what content in a Project can be edited by users.

Specifically, if content is in a Content Group, then it can be edited; if content is not in a Content Group, then it cannot be edited.

Content Groups may also contain Content Rules that define how the content in that group can be edited (e.g. changing text styles, replacing images, etc.).

If a Content Group is to contain translatable content, a source language for the content must also be selected.

NOTE:

There can be multiple Content Groups in a Master Document (e.g. one Content Group per target language in a multi-language document).

NOTE:

If content is not in any Content Group, it will not be editable. However, such content will still be rendered as part of the document and visible to users.

Content Rules (Policies)

Content Rules define how the users can edit content during a one2edit™ Job.

The rules are divided into text and image rules.

NOTE:

If no text Content Rules are assigned, the users can edit the characters of any text segments in the Content Group, but not the styling, etc.

If no image Content Rules are assigned, the users can select but not edit the images in a Content Group.

Font Package

A Font Package is a ZIP archive file containing one or more font files.

Such packages can be uploaded to a one2edit™ Client Workspace.

Any Master or Version Documents in that Client Workspace can make use of those fonts.

NOTE:

Fonts uploaded to one Client Workspace cannot be seen by documents in a different Client Workspace.

Frame Rules

Frame Rules are used to define how (and if) frames can be edited during a one2edit™ Job.

Frame Rules can be defined for an entire document or for specific frames.

NOTE:

Frame Rules are separate from Content Rules. Content Rules only apply to content within a frame, whereas Frame Rules apply to the frames themselves.

InDesign Preflight Profiles

An InDesign Preflight Profile is your defined quality check of a document to be done before handoff to a printer.

Preflight Profiles are exported from Adobe® InDesign® before being uploaded to a one2edit™ Client Workspace.

You can find out more about preflighting here.

Job

A Job is a combination of a Workflow and a document (either a Version Document or a Master Document).

The Content Groups and Content Rules which are set up within a Master Document define what content can be edited and how it can be edited.

The Workflow defines who can do that editing.

Language Sets

A Language Set is a set of languages in one2edit™ that have their own Translation Memory.

The "Commit Translations" Workflow action can be used to populate the Translation Memory of a Language Set with the translations done in a one2edit™ Job.

TMX (Translation Memory eXchange) files can be imported from an external source to the Translation Memory of a one2edit™ Language Set.

Master Document

A Master Document is the parent Adobe® InDesign® document in a one2edit™ Project.

The design for all documents in a Project flows from this Master Document (e.g. number of spreads, layers, frames, etc.).

All Content Groups are created and set up within a Master Document.

Version Documents are the child documents of this parent.

Note Groups

A Note Group is a color-coded grouping mechanism for notes.

They can help to distinguish (by name and color) which notes are meant for whom within a Job.

PDF Presets

A PDF Preset is a group of settings that create a PDF in the way that you want, e.g., bleed, slug, dpi, etc.

PDF Presets are exported from Adobe® InDesign® and then imported to a one2edit™ Client Workspace.

The PDF Preset files have a .joboption file extension.

You can find out more about PDFs and PDF Presets here.

Project

A Project is the wrapper that contains the Master and Version Documents within one2edit™.

It is possible to have a one2edit™ Project that consists solely of a Master Document.

NOTE:

It is possible to create a Project in one2edit™ that does not contain any documents. The Master and Version Documents can then be filled in at a later stage. This is, however, not a typical use-case.

Segmentation

Segmentation involves partitioning the 'stories' (via Segmentation Rules) of an InDesign® document into smaller segments for translation purposes.

By default, the text in a Master Document is segmented into paragraphs when a one2edit™ Project is created.

However, most Translation Memory entries are sentences or sentence-like units, so you should ensure that your Master Document is segmented in the same way.

NOTE:

The original InDesign 'stories' are left intact by one2edit™. The Segmentation is performed at the one2edit™ level, not in the InDesign document itself.

Segmentation Rules

Segmentation Rules are sets of regular expressions (regex) that use pattern-matching to break the text of a document into Segments (typically sentences or sentence-like units) for more efficient translation.

SRX (Segmentation Rules eXchange) files can be used to import Segmentation Rules into a one2edit™ Client Workspace.

It is possible to customise Segmentation Rules in one2edit™ according to your project requirements.

NOTE:

Segmentation Rules are language specific. Typically, rules are required for the source language of a Project, as the segmentation is performed on the text in the Master Document.

NOTE:

Default Segmentation Rules are provided with one2edit™, but these should be tested to ensure that they match the segmentation in your existing Translation Memory.

Segments

A Segment can be a sentence, paragraph, or sentence-like unit (heading, title, element in a list).

Breaking the text of a document into Segments (by the use of Segmentation Rules) allows for more efficient translation of that text when a Translation Memory is used.

Segments are sometimes referred to as 'translation units'.

Template

A Template allows a user to create a job with one-click, but without requiring any read or write access to Projects, Master Documents, Workflows, etc.

A user must be assigned to a Workflow in the Template, or have at "read" privileges for the Template, in order to start it.

When a Template is started, it spawns a Version Document from the associated Master Document, assigns the associated Workflow to that Version Document, and starts the Workflow, thus creating a Job.

Translation Memory

A Translation Memory, or TM, is a database that stores Segments, which can be paragraphs, sentences, or sentence-like units (headings, titles, elements in a list).

The Segments in a Translation Memory have previously been translated, and the database is used to aid human translators.

Each Language Set in one2edit™ contains its own Translation Memory.

TMX (Translation Memory eXchange) files can be used to import Translation Memory entries from an external source into the Translation Memory of a one2edit™ Language Set.

NOTE:

It is very common to only need one Language Set/Translation Memory in a one2edit™ Client Workspace.

User Permissions

User Permissions or Privileges are the rights that a user has within one2edit™, but outside of the document-editing process.

These permissions are defined by the user group in which the user resides, as well as folder permissions, etc.

They may dictate a user's access to folders, projects, etc. as well as defining what menu options are available to the user.

NOTE:

User Permissions have no effect on what the user can or cannot do when it comes to editing a document. The Content Rules dictate what is permitted during editing for all users.

Version Document

A Version Document is a child Adobe® InDesign® document in a one2edit™ Project.

A Version Document starts its life as a copy of the Master Document.

The content of a Version Document can be edited/translated in accordance with the Content Groups and Content Rules set up in the Master Document.

NOTE:

It is possible to have multiple Content Groups, assigned to different users, all within the same Version Document.

Workflow

Workflows are assigned to documents in order to create Jobs in one2edit™.

A Workflow consists of one or more Workflow Tracks.

The document to which a workflow is assigned must be either:

  • a Master Document containing populated Content Groups or
  • a Version Document created from a Master Document that contains populated Content Groups.

Workflow Track

A Workflow Track consists of an edit step, one or more review steps, and a target language (if translation is required).

Each step in a Workflow Track can have users and automated actions assigned to it. If no users are assigned to a step, that step is skipped (i.e. ignored).

For example, if no users are assigned to any review steps, then it is as if those steps do not exist.

There must be one Workflow Track for each Content Group in the Master Document.

Each Workflow Track must have the same name as the Content Group to which it is assigned.

If no steps in a Workflow Track are populated, that Workflow Track is effectively disabled, and the content in that Content Group cannot be edited.




© 2009-2024 1io BRANDGUARDIAN GmbH · All rights Reserved · Legal / Privacy Policy


top