The Manual

« Section 9 »

9.1 Project Actions

Once you have created a project and selected it, near the top will be the “Project Actions” link.

This allows you to do several things:

  • Import originals: Your new project will have no strings available to translate until you import some. You can also use this option to update the originals when you have a new version ready.
  • Permissions: Set the permissions for users on this project.
  • New Sub-Project: Create a new sub-project (see section “6.7 Creating a new project” for details).
  • New Translation Set: Translation sets let you define which languages you will be translating in to.
  • Mass-create Translation Sets: If you have another project with translation sets define, you can clone them to this project with this option.
  • Branch Project: This allows you to clone this entire project in to a new one.
  • Delete Project: This deletes the project from GlotPress.
  • Personal project options: This lets you set personal options for this project.

9.1.1 Import Originals

Importing your source strings is the first step in translating.

You must extract your original strings from your source code. This step is outside the scope of GlotPress, however there are tools available to do this for various frameworks that use gettext. If you are writing a WordPress theme or plugin, you can do this from the administration section of your theme/plugin site on via the “Generate POT File” option.

GlotPress supports 5 different types of files to import:

  • Android XML (.xml)
  • Portable Object Message Catalog (.po/.pot)
  • Machine Object Message Catalog (.mo)
  • .NET Resource (.resx)
  • Mac OS/X / iOS Strings File (.strings)

Now, from the “Import Originals” option, simply select the file name and type. Then click “Import” to complete the import.

9.1.2 Permissions

This menu is only visible to administrative users, normal users cannot see these settings.

Permissions in GlotPress are broken up in to four types of users:

  1. Administrators: Can create/delete projects, translation sets, permissions, glossaries and strings.
  2. Validators: Can add/delete strings and approve strings submitted by other users. Added via the permissions page by administrators.
  3. User: Can submit strings to translation sets for approval by Validators. Any logged in WordPress user.
  4. Anonymous: View translations only. Any user not logged in to WordPress.

The permissions page allows you to edit the list of validators only. You can use the standard WordPress tools to manage “users”.

The permissions page is broken up in to two sections:

  1. Validators: The current users that can approve strings for the project/locale.
  2. Add Validator: Add a new user to the above list.

The list of validators is in the format of:

user [name] can approve strings with locale [locale] and slug [slug]

Where the items in [] are replaced with the appropriate values for the user being listed.

Users can have multiple entries as needed.

To add a new permission, go to the bottom of the page and enter the user name to add, which locale to they will have access to and the slug. The slug ensures the translation set is uniquely identified.

To remove a permission, simply click on the “Remove” link to the right of the permission you want to delete.

9.1.3 New Sub-Project

The sub-project page is identical to the “Create New Project” page with the one exception that the parent project will be set to the current project.

9.1.4 New Translation Set

The new translation set page has 4 fields to fill out:

  1. Locale: The locale you wish to use for this translation set.
  2. Name: A human readable name for the translation set.
  3. Slug: A machine friendly name to use for the translation setup. This does NOT have to be unique by itself, but in combination with the project and locale the combination must be unique.
  4. Project: The project to assign the new translation set to.

Once you have completed the fields, click “Create” and you will be returned to the project page.

9.1.5 Mass-create Translation Sets

If you have several projects/sub-projects, you may already have setup the translation sets you want for another project. Instead of manually re-creating them for your new project, you can use this option to mass create them. This is particularly useful if you are using a parent/sub-project structure.

9.1.6 Branch Project

If you wish to create a new project that is identical to the current project you can “branch” it with this option. Note there is no way to “merge” projects once they have been branched and changes to the new project will not be copied back to the original project.

9.1.7 Delete Project

This option is self explanatory, however once a project has been deleted it cannot be recovered.

9.1.8 Personal project options

The personal project options allow you to set options for GlotPress that are specific to the user and project. By default the only option available is “Source file URL”.

This can be useful if your source code is not accessible by your users and validates but some team members have access to the repository.

9.2 Translations

The translations list is a list of all translation sets that belong to the project. The list is made up of six columns: 1. Locale 2. % (percentage complete) 3. Translated (number of strings with “translated” status) 4. Fuzzy (number of strings with “fuzzy” status) 5. Untranslated (number of strings with “untranslated” status) 6. Waiting (number of strings with “waiting” status)