About

Mneme has been designed to provide a complete environment that facilitates the linguist while translating/reviewing content during the various phases of a localization project; offering the linguist with a dynamic interface including a wide variety of tools & methods specifically designed to provide the ideal environment.
Mneme has been developed in .NET adhering to the new generation industry standard formats XLIFF, TMX & TBX, encompassing the latest technology from the .NET environment, utilizing web services that allow the user to connect directly to the LOGOS servers for various interactions, while providing secure data transfer using encryption.
Xliff has been chosen as the core format for Mneme to ensure interoperability with applications/tools developed by other software vendors; providing 100% compatibility and eliminating the restriction to work in specific environments to suit the needs of the translatable format.
It provides a fully dynamic translation editing interface, that supports a wide variety of methods and functions

• Advanced tag handling functionality that allows hiding and/or partial hiding of the tags within the translation units
• Seamless integration with the local and remote translation memory and terminology databases, that provides real-time fuzzy match support
• Segment splitting/un-splitting & Grouping/Un-Grouping; this functionality allows the linguist to additionally split segments into smaller units where segmentation was missed or not successful and/or merge segments when content has been incorrectly segmented by the filters that created the xliff file.
• Status/Flag handling that support revision control
• Advanced filtering of the file content.
• Comparison functionality that provides a visual report of the changes made to the segments.
• Standard text editing functionality, search/replace, spell check, cut and paste
• Validation reporting that performs various checks on the translated content to ensure correctness and consistency.

Full language support, including double-byte and bi-directional languages
Fully compliant with XLIFF 1.2. XLIFF is the XML Localization Interchange File Format designed by a group of software providers, localization service providers, and localization tools providers. It is intended to give any software provider a single interchange file format that can be understood by any localization provider. It is loosely based on the OpenTag version 1.2 specification and borrows from the TMX 1.2 specification. However, it is different enough from either one to be its own format.
Fully compliant with TMX 1.4. Translation Memory eXchange format (TMX). The purpose of the TMX format is to provide a standard method to describe translation memory data that is being exchanged among tools and/or translation vendors, while introducing little or no loss of critical data during the process
Fully compliant with TBX. Term Base eXchange (TBX) allows the representation of various kinds of information about individual terms that distinguish them from other terms in the same concept entry.
The main purpose of TBX can be seen as the structure that maintains all terminological information relative the individual concepts allowing for the flow of terminological data between technologies and systems, integration of terminological data from multiple sources & making entries which require some work available for public feedback

Requirements

Mneme was developed in C# using Microsoft .NET; therefore it is necessary to have the Microsoft .NET redistributable components installed on the user's computer to run the executable.
Note: If the .NET redistributable components are not installed on the user's computer, then they can be downloaded and installed from the following Microsoft web page:

• Windows 2000 or later versions of Windows (i.e. XP ,Vista, Windows 7 etc..)
• Microsoft .NET 3.5 redistributable components installed
• 10 MB of free disk space
• 1+ GB RAM

Instructions for Beta testing

The functionality available in the application is at the core level of development, meaning that only the necessary functionality has been integrated to allow the user to perform the basic functions.  This can been seen as the starting point.
• Please review the existing functionality and include detailed reviews when/where additional functionality is required and or where existing functionality should be changed.
• All functionality in the application can be considered new and needs to be reviewed and tested
• Test the application under different operating systems /localized etc.. to ensure no unforeseen anomalies occur.
• Try to involve a user to test the right to left language support.
• Include as much detail as possible with the debug error reports indicating clearly how to re-produce the bug.

 

Thank you for your support

Translation Memories

There are three types of memories available from the Mneme interface
Internal TM - This memory is composed of pretranslated fuzzy match units embedded in the xliff file; these matches will have been inserted automatically by the Logos Analysis/Pretranslation System (LAPS).
Local TM – This can be considered the main memory and is maintained automatically while the user is translating/modifying the content allowing for import/export, search and real-time automatic fuzzy match association.   The user can choose to retrieve matches from more than one database, as follows:

• Working TM - The working TM is updated automatically respecting the relative settings (i.e. merge, overwrite etc...) while the user is modifying the file content.
• Reference TM - Information can only be retrieved from the reference TM.

Note: The Local TM is fully compliant with the TMX 1.4 specification standard
Remote TM – This is a centralized memory that will be made available from the Logos servers and accessible from the Mneme interface connecting through secure web services. The main objective of this memory will be to allow various translators/reviewers to connect from different remote locations.
A major advantage of this service would be to minimize inconsistencies as seen when multiple translators are translating content of the same project simultaneously. Note: Access to the remote memory is not activated with this release.

Terminology

There are two types of TermBase memories available from Mname.NET interface

Local TermBase - This database is maintained by the user while working with the file content.  It provides the following basic functions

• Real-time term association - automatically highlighting the terms already present in the TermBase relative the active segment.
• TermBase maintenance - allowing the user to insert/modify/delete the concepts/languages/terms including all the associated properties (i.e. definition, status, part of speech, gender, context etc...) 
  Note: The local TermBase is fully compliant with the TBX-Basic specification standard

Remote TermBase - The centralized TermBase will be available from the Logos servers and accessible from the Mneme interface connecting through secure web services. 
As with the Remote TM the main advantages seen from working from a remote TermBase would be to ensure consistency where multiple translators/reviewers are working on the same content simultaneously.

Functionality specific

Merge/Un-merge
Merging translation units can be useful to overcome bad segmentation from the tool that filters and creates the original XLIFF file. It allows the user to fix these issues by merging the required units; the XLIFF specification ensures compatibility with this functionality allowing you to group units without changing the original file structure..
Split/Un-split
Splitting translation units is necessary when the tool that filters and creates the XLIFF file fails to segment the content correctly allowing the user to further segment the content into smaller segmentation units for translation; the XLIFF specification ensures compatibility with this functionality allowing you to include additional information under the <seg-source> structure to identify additional segmentation required for a single translation unit.
Inline Tags
The application maintains the inline tags in two modes, as follows:
• Standard – the tag format adheres to the XLIFF specifications and does not need further rendering during I/O calls.
• Compatible – the tag format does not adhere to the XLIFF specifications and needs to be escaped during I/O calls; interaction with these type of tags can been seen correctly from the interface however to ensure compatibility with the XLIFF, TMX and other structures they are encapsulated by the tag <ph>; example (<ph type="x-mneme_xliff_compatible ">...</ph>).

Spell-Checker

Mneme has integrated the spell checking engine from NetSpell
The NetSpell open source project is written entirely in managed C# .net code. NetSpell's suggestions for a misspelled word are generated using phonetic (sounds like) matching and ranked by a typographical score (looks like). NetSpell supports multiple languages and the dictionaries are based on the OpenOffice Affix compression format. The library can be used in Windows or Web Form projects.
The compatible dictionaries can be downloaded directly from the LOGOS server via web services from the Mneme interface; A valid User ID & Password are required to access the LOGOS server; these will be provided to all Logos collaborators. All available dictionaries will be presented from the server for the user to select. The user select the dictionaries that want to downloaded.
Note: The dictionaries are based on the OpenOffice Affix compression format; the available dictionaries have been converted from the dictionary list available from OpenOffice Lingucomponent
The current list of spell check dictionaries are available.

 

Culture Info	Language Name
cs-CZ	Czech (Czech Republic)
da-DK	Danish (Denmark)
nl-NL	Dutch (Netherlands)
en-AU	English (Australia)
en-CA	English (Canada)
en-GB	English (United Kingdom)
en-US	English (United States)
fr-FR	French (France)
de-DE	German (Germany)
el-GR	Greek (Greece)
he-IL	Hebrew (Israel)
hi-IN	Hindi (India)
it-IT	Italian (Italy)
lv-LV	Latvian (Latvia)
lt-LT	Lithuanian (Lithuania)
nb-NO	Norwegian (Bokmål) (Norway)
pl-PL	Polish (Poland)
pt-BR	Portuguese (Brazil)
pt-PT	Portuguese (Portugal)
ro-RO	Romanian (Romania)
ru-RU	Russian (Russia)
sk-SK	Slovak (Slovakia)
sl-SI	Slovenian (Slovenia)
es-MX	Spanish (Mexico)
es-ES	Spanish (Spain)
sv-SE	Swedish (Sweden)
th-TH	Thai (Thailand)
uk-UA	Ukrainian (Ukraine)

Translation Unit Status/Flags

The translation units can be marked or tagged while reviewing and/or translating the content.
Segment Status
• Protected – Indicates that the translation unit is locked for editing
• Un-translated – Indicates that the unit needs translation
• Translated – Indicates that the unit has been translated
• Updated – Indicates that the unit has been updated
• Reviewed – Indicates that the translations have been reviewed
• Approved - Indicates whether a translation is final or has passed its final review
Translation Status
• Pending - Indicates that the translation needs to be checked by reviewer/transaltor
• Checked - Marker to indicate that the translation has been checked by reviewer/translator
• Rejected - The translation provieded has been rejected.
The flags can be used to allow the user to identify and mark areas of the file by association of a flag; this can be useful for example to identify where in the file the user finished working on the day before etc...

Filters

Each of the translation units have a serious of properties associated to them that allows the application to maintain their structure.  The Filters window allows the user to filter a subset of the translation units respective of the filter criteria applied that is relative to the unit properties.
This allows the user to filter on units for specific information, example the user would filter on Segment Status=UnTranslated to locate all translation units that are not translated etc...

Validation Reporting

The validation process performs a series of checks on the translated content relative to the validation settings set by the user.
The report is organized by the validation checks (i.e. Tags, Numeric, Untranslated etc...) and provides a detailed message of each error found, including a link to the term itself; selecting the link will jump to the associated term from the list.

Validation Check	Details
Tags	Compare the source & translation for differences in the tags
Numeric	Compare the source & translation for differences found in the numeric data Note: differences related to globalization rules (i.e. thousand & decimal symbols) are ignored.
Untranslated	Report the terms whose translation is equal to the source text.
Inconsistencies	Report the terms where different translations exist for a single source term.
Generic	Performs rudimentary checks that would render the translation invalid (i.e. if translation is equal to nothing etc..) Note: these checks are always performed.
Min/Max Bytes	Validates the width of the strings against the allowable range specified by the source format
Scope		Details
Validate updated segments only		Validate only the segments whose translated terms have been updated
Ignore locked segments		Ignore segments that are locked for editing

Search & Replace

To find text

You can find each occurrence of a combination of any characters, including uppercase and lowercase characters, whole words, or parts of words, or regular expression.
• Select Find & Replace from the Tools menu
• In the Find What box, type in the search string, or choose a previous string from the drop-down list
Note: The Find What text is Regular Expression compliant
• Set the options you want to control the search

 

 

Option	Details
Case Sensitive	Find text having the given pattern of uppercase and lowercase letters
Search right to left	Specifies that the search moves from right to left instead of from left to right. A regular expression with this option moves to the left of the starting position instead of to the right. (Therefore, the starting position should be specified as the end of the string instead of the beginning.) This option cannot be specified in midstream, to prevent the possibility of crafting regular expressions with infinite loops
Match whole words	Find occurrences of the text as whole words
Column	Search in the source or target column
Search Direction	Search the content above or below the insertion point

 

Choose Find Next

Note: If the search string is found, then the screen scrolls so you can see the text in context
To replace text
You can find and replace each or every occurrence of a text pattern.
• Select Find & Replace from the Tools menu
• Specify the text to replace as described in Find Text
• Type the Replacement Expression in the Replace With box, or choose a previous string from the drop-down list
• Set the options you want to control the search

 

Option	Details
Case Sensitive	Find text having the given pattern of uppercase and lowercase letters
Search right to left	Specifies that the search moves from right to left instead of from left to right. A regular expression with this option moves to the left of the starting position instead of to the right. (Therefore, the starting position should be specified as the end of the string instead of the beginning.) This option cannot be specified in midstream, to prevent the possibility of crafting regular expressions with infinite loops
Match whole words	Find occurrences of the text as whole words
Column	Search in the source or target column
Search Direction	Search the content above or below the insertion point

 

Choose one of the following actions:

• Click Find Next to select the next occurrence.
• Click Replace to replace the current selection.
• Click Replace Next to replace the current selection, and find the next occurrence.
• Click Replace All to replace all occurrences of the search text, in the specified scope.