Replication editing hint - indicates whether or not the inline code can be copied. Value description: yes if. Xliff Editor provides the easiest way of editing your XLIFF files. No more messing around with the XML format, or worrying about filecorruption. Xliff Editor includes full search support, handy keyboard shortcuts, and even basic read support for SDLXliff files! XLIFF files are based on the standard XML format, and are used specifically to exchange localisation.
![]()
Ocelot is an open source workbench for working with XLIFF files in a post-editing and language review environment. It implements the localization quality issue and provenance data categories from the proposed ITS 2.0 standard and utilizes the Okapi Framework for parsing XLIFF files.
Build Status:
Downloading and Running
A pre-compiled version of Ocelot is available from the Okapi downloadspage. Ocelot is distributedas a JAR file that will run on any platform that has Java 1.7 or laterinstalled. There are also native executables for the Windows and Mac platforms.
![]()
These files are also available on the Releases page.
Documentation
Additional documentation is available on theOcelot wiki.
##Reporting Issues##To report a bug or request an enhancement, please create an accountin the Ocelot JIRA and track all issues there.
Requirements
Build
Ocelot uses Maven, so all dependencies should be resolved upon build (mvn package). The output jar file will located in the created target folder.
Mac Builds
The
install phase will also create a disk image (DMG) file if thedmgbuild tool is installed.
When run on OS X, the
install phase of the build will sign the Ocelot.app artifact if the codesignId property is set in Maven. For example,
This will run the
codesign tool with the specified id. You must have XCode toolsinstalled and a valid certificate for the specified ID installed in your local keychainfor this to work.
Release packaging
Use
This will generate javadoc for the application and do other necessary build prep.
This can be run in conjunction with codesigning on the Mac:
Filter Rules
Filter rules are used to selectively display segments that match enabled rules. The configuration is loaded from the
rules.properties file, which is located under <home directory>/.ocelot (or can be created from scratch if it does not exist).
Filter Display Rules
Filter display rules control how to display segments that match a particular filter rule. They control how the flag on a segment in the segment view appears. Possible UI types are the border color, background color, and the text. They are specified in the same file as the filter rules (the rules.properties file).
XLIFF State Qualifier Display Rules
These rules control how the state qualifier attribute of a target in XLIFF will be indicated in the segment view. Each rule controls the background color of the segment number of a segment that has the specified state-qualifier attribute. They are specified in the same file as the filter rules (the rules.properties file).
![]()
The default plugin directory is located under <home directory>/.ocelot/plugins. Plugins must be compiled into a jar file and placed under this directory, or a directory chosen by the plugin manager. All plugins must implement the methods defined in the Plugin.java interface, which are used to display the plugin in the plugin manager UI. There are currently two types of plugins Ocelot supports: ITS and Segment plugins.
ITS plugins are plugins that are interested in the ITS metadata of segments within an open file. The required methods for ITS plugins are given in the ITSPlugin.java interface, so every ITS plugin must implement this interface. There are currently 2 methods, which determine how to handle a particular ITS metadata for a segment. ITS metadata is only sent to plugins when the export data button in the ITS Plugin UI is pushed, which will export the LQI and Provenance data of the currently open file to the enabled ITS plugins.
Segment plugins are plugins that are interested in events such as entering and exiting the edit mode of a target, or the opening and saving of an XLIFF file. The required methods for Segment plugins are given in the SegmentPlugin.java interface, so every Segment plugin must implement this interface. Events are automatically triggered if the plugin is enabled on the segment plugin manager UI.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |