Individual Project Tasks

Introduction

When a user selects a project name from the Projects page, the Project Overview page comes up with a summary of the project. There are a number of tabs on the top of the page. The tab that is selected is highlighted. For this example the Overview button is highlighted for the Project Overview page.

• Overview - a summary of the project, showing the data source, history, and a summary of Globalyzer and Localyzer configuration
• Globalyzer - a detail of the Globalyzer information including the number of issues found
• Localyzer - a detail of the Localyzer information including the locales and translation status
• Issues - detailed information about the Globalyzer and Localyzer issues
• Logs - report of the various actions performed on the project.
• Configure - allows the user to modify the project.

Analyze Project

[Admin, Manager]

The Analyze Project icon will run the project. When the button is selected, the icon will be shown twirling and a message will come up in the upper left about the job processing.

Overview

[Admin, Manager, Developer, Translator]

Once a project is created, selecting its name will open the Project Overview. Note that the Overview tab on the top is highlighted. The Overview page is a project summary page, showing the Globalyzer and Localyzer summaries and the Project History. Any of the analysis lines are selectable and will open the corresponding logs.

The Analyze project button will run the project.

Globalyzer

[Admin, Manager, Developer, Translator]

The Globalyzer Icon opens the Globalyzer Report page with the details of the Globalyzer analysis.

• Total Remaining Issues - all the issues that Globayzer has identified. This card is selectable and will take you to the Issues page.
• Total Issues Fixed - how many issues have been fixed since the project was created.
• Total Issues Density - number of issues divided by the number of lines of code that were scanned.
• Issues Types Breakdown - What types of issues were found.
• Issues Priorities Breakdown or Issues Severities Breakdown- A list of the severity of the issues. This can be toggled in the Advanced Settings.
• Issue Scans Breakdown - The rulesets used and the items scanned for.

Localyzer

[Admin, Manager, Developer, Translator]

The Localyzer Icon opens up the Localyzer Report page. The Localyzer page has a number of icons on the left side for actions that can be done.

Send kit to translation - send the latest prep kit to be translated at the specified Translation Management System or Machine Translation engine.

Check Import - Check the translation management system to see if translations are available to import. If previous translations passed the incoming checks but failed on pushing to the repository, Check Import will try again pushing to the repository those checked files.

Download files to translate - Download the files for a translation kit. Those files may have been sent to a TMS or an MT. This is a manual handling of files back and forth, useful in particular when working around some rare issue.

Upload translated files - Upload files which were translated for a prep kit sent to translation for one locale. The files may have been sent to a TMS. This is a manual handling of files back and forth, useful in particular when working around some rare issue.

Deactivate last translation kit - deactivate the last translation kit that was sent. A translation kit cannot be deactivated if any part of it has been imported.

Reset all translation kits - this is used as a reset for the project.

Create project baseline - Set the baseline so that the database can keep track of translation changes and imports. While creating and configuring the project, it does not have a baseline.

String Manager

Introduction video

Click on the image below to watch a String Manager introductory video:

Overview

[Admin, Manager, Developer, Translator]

String manager provides visibility into each key/value pair managed by Localyzer. A link for a specific resource points the browser to GitHub, GitLab or Bitbucket repository/project/branch/key-value pair. Typically, only developers will have access to their repositories and modify source strings.

Developers create and maintain the source strings, and if some strings need to be changed, only developers can change them. Users without access to the repository can copy the link and send it to the development team with some explanation, via Slack, Teams, Email, etc.

Localyzer makes changes to the target files with translations, pseudo-translation, context files, or LocalyzerQA type files. Developers should not modify those, especially outside of the branch where Localyzer pushed them, for fear of merge conflicts.

Search

From the search box input text, find strings that match by

• their values
• their keys
• their filename
• their description

Filter

Filtering is based on attributes of the key value pairs:

• to be sent
• sent and are not yet translated
• translated
• to be reviewed (or not)
• reviewed (or not)
• have context (or not)

Sort

Sort strings based on

• the text itself
• the key
• the filename
• the time it was found.

• In the screen shot above, strings that match 'model' and are 'to be sent' are displayed.

Strings can be set 'to be reviewed', or 'reviewed', or neither. Certain strings will be marked 'to be reviewed' by the system. Filtering allows to select strings based on the status of the string.

Expanded view

To see the expanded view of a key/value pair, click on the right down arrow.

• File and line number: The location of the string
• String key: the key for that string
• Source reviewed: a yes/no flag to indicate if the string was reviewed
• Source review recommended: a yes/no flag to indicate that string may be rewritten
• Translation status: The string was translated, is being translated, has not been translated in how many locales
  • Note: To see which are those locales, hover over the numbers

Multi String Selection

To select specific strings, click on the multistring selector, then click each string:

To help with the selection, use filter and search.

Send selected string to translation

Once strings are selected, click Send to translation, pick the locales (all, some), and click Send selected strings.

Context Capture

For project whose TMS has an InContext server, context can be acquired in 3 different ways and shown in the String Manager.

Webapp Context Capture

Project must be configured with a context locale, say 'la' for Latin. This will create a set of resource files in the context locale, - like 'la' (Latin). To capture the context, run the application in the Context Locale (la) and use the Lingoport Google Chrome extension to capture the context. The context will be pushed to the InContext Server associated with the TMS.

Figma

Use the Figma extension with the Enable Context Screenshots option set, on a project whose TMS as an InContext Server.

Each string will then be sent to Command Center with the design element as the context. The context PNG will be stored in the InContext Server.

Add Screenshots

Another option is to use the multi string selector or the context indicator to add a screen shot as a context for those selected strings.

Multi selector and Context

• Click on the multi selector (the list list icon)
• Select the strings
• Click on 'Assign Context Image'
• Add an image
• Click 'Upload'

Context Indicator for an individual string association:

• Click on the context selector
• Add an image
• Click 'Upload'

Context Viewing

When context has been associated with a string, the context indicator will show up as 'blue'. Otherwise, it will stay 'grey'. To view a context, click on the indicator. The context will pop up.

Filter those strings which do or don't have context, as above.

Sending Context to Translation

Context works for projects whose TMS has been configured with an InContext Server and PXML (see below). When sending files to translation, the PXML file will have an lrm_incontext element with the URL to the context for that string, held in the InContext Server.

Here is an example of Trados Enterprise showing the context:

PXML

When sending translation with context, best is to send them as PXML files.

• PXML

ChatGPT / LLM [Upcoming in 4.0.z]

When sending to an LLM configured with InContext Server, the context will be passed as an automatic prompt for better quality translation, as showing a string on an application screenshot helps an LLM disambiguate the meaning and potential translation for a UI string.

Issues

[Admin, Manager, Developer, Translator]

The Issues icon opens the Issues page and will show all the Globalyzer and Localyzer issues. Once the issues page is open, the issues can be searched, filtered and sorted.

Selecting an issue in the list will show more detail about the issue, including its status, type and priority.

• Go to line in source code - will take the user to the line of code in the repository, for users with repository access.
• Learn more about this issue - will open up documentation about the issue.
• Comments - any comments can be added about Globalyzer issues. They will remain after further analyses.

Project logs

[Admin, Manager, Developer, Translator]

The Console Logs icon opens up the logs to show when the project has been analyzed. Selecting any of the lines will open the log and show more detail.

In this example:

• The user making the change is testAdmin
• The version of Command Center is given
• One setting in the General Settings was changed
  • Tags were modified on the project: FTP to FTP and Build 5

Edit Project configuration

[Admin, Manager]

The Edit icon will open the Edit Project Configuration page. There are several icons on the left side of the page.

- validate the Localyzer configuration finds the resource files.

- make a copy of this project

- refresh the project

- remove the project from Command Center

General Settings

Data Source Settings

Access Settings

Globalyzer Settings

Localyzer Settings

Edit a project

There are multiple ways to get to edit a project.

First, from the Projects page, hover over the project and the Edit button will appear.

Second, select the project name (or the Globalyzer or Localyzer icon) to go to the Overview, Globalyzer or Localyzer page. Select the Configure button on the top to get to the Edit Project Configuration page.

From this page, any of the settings can be changed.

When changes are made and saved, a notice appears at the top of the screen about the project being updated. The project does not run until it is manually run or by an automated task.