Create an account

The first thing you will need to do is to create an account on tethras.com. Be sure to validate your account by clicking on the link that is emailed to you after you sign-up. After you have created your account you can choose an account level from the Organization Settings.

The dashboard

When you first login to your account you will be taken to your dashboard. The first thing you will have to do is to create a project. To do this simply press the 'Create Project' button on the top right of the screen. You will be prompted to enter a project name and OS. When you have confirmed your selections you will be re-directed to the project page. (Note: You should create a separate project for each app. If you have ported your app to different OS's then it is generally best to create separate projects.) If you have upgraded to premium and have multiple users you will be able to see all the projects for your organization on this dashboard page.
Once you have projects on your dashboard you will be able to see the project status of each of them - see the section below for more explanation on project statuses.

Tasks & Discussions

Tasks & Discussions are a vital part of the Tethras system. During Sanity check the Tethras production managers will raise tasks in order to clarify meaning on strings. Translators may also raise queries at any given time. To view the tasks and discussions of your project, open it and select the tasks & discussions tab from the sidebar. You need to have uploaded files to your project for this tab to be visible.

Tasks

Tasks are raised by our production team during Sanity Check for strings with unclear context or for strings containing placeholders. When you answer the question your answer will be added to the string comment. Once you save your answer, the task will be marked as complete and it will be automatically archived - it will disappear from the the tasks section. You can always view your complete tasks by clicking the 'Show resolved' link, next to the section heading.
Tasks are usually queries that are crucial to the quality of your translations. Make sure to check them regularly and answer them.
You will be notified via email if there are outstanding tasks for any of your projects. You will be able to see if there are unresolved tasks or new discussions on your dashboard, under each project name.

Discussions

Discussions are conversations, raised either by translators, or by the Tethras production team. They can be raised at any time during the translation process, and are visible to all translators, working on your project, your project manager and yourself. Answering discussions results into adding a thread to the conversation - you will not be editing any of the metadata of the string directly. Once you replay to a discussion it will be marked with a darker color, until another replay's been added to it.
If you need to view the string metadata (file, comment, etc.), click the 'show details' link. From there, you can also edit the string comment if it is necessary.
You can archive the discussions by clicking the archive button () on the top right corner. Alternatively, you can click 'replay and archive' after you have typed your answer, and your discussion will be moved to the archived list, after your post have been added to the conversation. To view the archived discussions, click the 'Show archived' link, next to the section heading.
You will be notified via email every time a new discussion is raised, or if there is a new replay to a discussion. You will be able to see if there are unresolved tasks or new discussions on your dashboard, under each project name.

The more details you give us before you purchase, the fewer discussions will be raised, which will shorten the churnaround time. Tasks & Discussions can slow the translation process considerably so make sure to check them regularly and answer them.

Glossary

In Tethras we use glossaries for clarifications of complex or specialized terms to improve translation quality. We have glossaries for different OS's and Genres. App developers can add their own glossary as well to clarify meaning of terms and whether or not they should be translated. For example a good glossary terms are your app name, any character names, your organization name, any copyrighted terms, and any terms you don't want translated in general. If you don't want your app name translated anywhere inside the text you can set it to "DO NOT Translate" in your glossary.
If you have any character names you should specify their gender, and/or station because for many languages this is crucial information. For example in French the adjectives and plural forms used in a sentence differ according to the gender, while Japanese is hierarchy based and different words are used depending on the station of a character. Once a glossary term has been added we will search throughout your files and will highlight every exact match with that term for the translators working on your projects.
Below you can see an example for a glossary for a demo app called 'Discworld' with a couple of example terms already added in. The Discworld characters usually have double meaning names and are a good example for terms that need more explanation for proper translation. Here we have specified the character's gender, station any possible special use cases of their names.

Supported File Types

iOS and Mac OS

.strings and .plist

Android

strings.xml

Windows RT and Windows 8

.resx, .resw and .resjson

BlackBerry

.rrc

Subtitles

.srt and .sbv

Other

.html and .properties

All Platforms

.txt

Custom File Types

We support localizable resources that are a custom XML or JSON format. We provide full support for JSON files with the following structure:

• { "key1": "Hello World",
• "key2": "Username:",
• "key3": “Password:”
• }

If you need your custom xml or JSON localized, please get in touch with us at support@tethras.com. We'll have a few questions to help us understand how to best deal with your files.

If you have your own private file format that you wish to translate, we recommend that you convert this file to an XML or JSON format.

Custom Format:

• key1 = “Hello World”;
• key2 = “Username:”;
• key3 = “Password:”;

XML (could be represented as follows):

• <?xml version=”1.0″ encoding=”utf-8″?>
• <resources>
• <string name=”key1″><![CDATA[Hello World"]]></string>
• <string name=”key2″><![CDATA[Username:"]]></string>
• <string name=”key3″><![CDATA[Password:"]]></string>
• </resources>

Unsupported files

Below you can find a list of the file types we don't support but recognize, and some tips on how to convert them to a more localization-friendly format. It is very important that you export the unsupported files, don't change the file extension because this will lead to errors.

• .rtf - a Rich Text Format file, can be saved as Plain Text (.txt) using Notepad, Word or Pages. This will discard any formatting information your file might contain, like font size/weight, images or intends.
• .doc/.docx - Microsoft Word file formats, can be saved as Plain Text (.txt). This will discard any formatting information your file might contain, like font size/weight, images or intends.
• .xls/.xlsx - Microsoft Excel file formats, can be saved as Text (.txt) or Tab Delimited (.txt) file format. This will discard any formatting information your file might contain, like font size/weight, images or intends.
• .ppt/.pptx - Microsoft Power Point file formats, can be saved as .rtf file format and then exported as Plain Text as explained above.
• .markdown - Markdown is a plain text formatting syntax that can be converted to HTML. We can localize this content if you first convert the file to HTML.
• .yml/.yaml - This is a human readable data interchange format. We recommend you convert the data to any of the localizable resource formats in our supported files list.
• .po - This format is used by GNU gettext: an internationalization and localization (i18n) system. Please convert this file to one of our supported formats, or contact us if you wish to keep your file in this format.
• .pdf - Portable Document Format handled by Adobe Acrobat. It can be exported as .txt but very often the white space is preserved and there are new lines in the middle of the sentence and this will not allow us to parse the strings correctly. You will have to search for all redundant new lines in the document and remove them.
• .odf - Open Office Document Format, can be saved as Plain Text (.txt) using Open Office, Word or Pages.
• .pages - Mac text editor format, can be exported as Plain Text.
• .numbers - Mac spreadsheet editor format, can be exported as CSV and then to Plain Text using Excel.
• .csv - spreadsheet format with no formatting where columns are defined by commas, can be opened using Excel and then saved as Text (.txt) or Tab Delimited (.txt) file format.
• .xliff - Localisation Interchange File Format, a XML-based format created to standardize the way localizable data are passed between tools during a localization process.
• .jpeg/.jpg/.png/.gif/.bmp/.tif/.tiff - these are all picture files and if they contain any localizable content we can extract it and replace it for you. Please contact us and we will get back to you with a quote.
• .wav/.mp3/.ogg/.flac - these are all audio files and you will need to transcribe the localizable content from them. This can be time consuming so if you would like us to do that for you contact us and we will get back to you with a quote.
• .mp4/.avi/.mkv/.omg/.mov/.rm/.rmvb - these are all video files and you will need to transcribe the localizable content from them. This can be time consuming so if you would like us to do that for you contact us and we will get back to you with a quote.
• .swf - these are all video files and you will need to transcribe the localizable content from them. This can be time consuming so if you would like us to do that for you contact us and we will get back to you with a quote.
• .ai - Adobe Illustrator vector file format, it cannot be exported as Plain Text directly from Illustrator. You will need to either export it as .pdf first and save it as Plain Text from Adobe Acrobat Reader, or copy and paste the text content in any text editing program and save it as Plain Text. The second option is highly recommended, because when converting .pdf to .txt you may get redundant new lines that break the sentences in many parts and they won't be parsed correctly. Please note that depending on the purpose of the file (weather it was used for printing or not) the text it contains may have been converted to curves or in other words it is no longer editable text but just a vector graphic with the shape of letters. If this is the case you will need to transcribe the text because there is no easy way to convert the curves back to text. This can be time consuming so if you would like us to do that for you contact us and we will get back to you with a quote. If you are extracting content from .ai files yourself make sure to check if all of the text got exported/copied across correctly.
• .eps/.svg - widely used vector file formats, can be opened with any vector editing software (Adobe Illustrator, CorelDRAW, Inkspace, etc.) and cannot be converted to Plain Text directly. You will need to either export it as .pdf first and save it as Plain Text from Adobe Acrobat Reader, or copy and paste the text content in any text editing program and save it as Plain Text. The choice you make depends on the program you are using - but usually the second option will lead to fewer mistakes. Please note that in order to preserve the original look of the file the text inside is likely to have been converted to curves or in other words it is no longer editable text but just a vector graphic with the shape of letters. If this is the case you will need to transcribe the text because there is no easy way to convert the curves back to text. This can be time consuming so if you would like us to do that for you contact us and we will get back to you with a quote. If you are extracting content from .eps/.svg files yourself make sure to check if all of the text got exported/copied across correctly.
• .cdr - CorelDRAW vector file format, it cannot be exported as Plain Text directly from Corel. You will need to either export it as .pdf first and save it as Plain Text from Adobe Acrobat Reader, or copy and paste the text content in any text editing program and save it as Plain Text. The second option is highly recommended, because when converting to .pdf from most of the older versions of Corel, it breaks the text fields to many small pieces and that might lead to mistakes and divided words. Please note that depending on the purpose of the file (weather it was used for printing or not) all or part of the text it contains may have been converted to curves or in other words it is no longer editable text but just a vector graphic with the shape of letters. If this is the case you will need to transcribe the text because there is no easy way to convert the curves back to text. This can be time consuming so if you would like us to do that for you contact us and we will get back to you with a quote. If you are extracting content from .cdr files yourself make sure to check if all of the text got exported/copied across correctly.
• .psd - Adobe Photoshop file format, it cannot be exported as Plain Text directly from Photoshop. You will need to either export it as .pdf first and save it as Plain Text from Adobe Acrobat Reader, or copy and paste the text content in any text editing program and save it as Plain Text. Both options are equally eligible. Please note that depending on the preferences of the author the whole or part of text it contains may have been rasterized or in other words converted to picture that no longer contains any text related information. If this is the case you will need to transcribe the text because there is no easy way to convert the raster back to text. This can be time consuming so if you would like us to do that for you contact us and we will get back to you with a quote. If you are extracting content from .psd files yourself make sure to check if all of the text got exported/copied across.
• .indd - Adobe InDesign file format, it cannot be exported as Plain Text directly from InDesign. You will need to either export it as .pdf first and save it as Plain Text from Adobe Acrobat Reader, or copy and paste the text content in any text editing program and save it as Plain Text. The second option is highly recommended, because when converting .pdf to .txt you may get redundant new lines that break the sentences in many parts. Please note that depending on the purpose of the file (weather it was used for printing or not) the text it contains may have been converted to curves or in other words it is no longer editable text but just a vector graphic with the shape of letters. If this is the case you will need to transcribe the text because there is no easy way to convert the curves back to text. This can be time consuming so if you would like us to do that for you contact us and we will get back to you with a quote. If you are are extracting content from .indd files yourself make sure to check if all of the text got exported/copied across.
• .m/.js/.jsp/.php - These file formats contain the source code of your app. We cannot extract localizable content from these files automatically. We recommend that you look at our Knowledge Base and review the procedures on how to prepare your app for translation.

How can you improve the quality and speed of the translations for your app at no extra cost?

When a translator begins working on a localization project, context is essential. The translator will want to know what kind of app this is. Is it for a formal audience e.g. corporate, or is this app for general release? These small extra steps can mean the difference between a good localized app and a fantastic app. It can also save you time in your schedule as it will remove the need for the translator to raise queries in our discussion system and wait for clarifying answers from you. Here are some additional resources that will improve your app's localization quality at no added cost to you, the customer.
Developer comments: This is especially important where there are variables e.g. "Please close to allow the job to complete" In English this looks like an easy string to localize but for a French translator it is vital that they know what words are substituted at runtime to determine the construction of the sentence in French. In some other languages the word order will be completely different – some languages have the verb at the end of the sentence. The use of developer comments like this enables us to get the translation right first time every time: Variable 1 = The options window, the settings window, the Save as dialog; Variable 2 = file copying, file deleting, file renaming.
For every string that contains a placeholder there should be a comment indicating what that string will look like at runtime, Example: "Please close the settings window to allow the file copying job to complete"
Screenshots: Any screenshots of your app would be a huge help to a translator. The ability to see strings in context, especially where there are variables in the string, is of immense value to our translators.
Marketing text: Even if you are not localizing the marketing text for your app, allowing our translators to see exactly what the app does is extremely helpful. Often, knowing that a particular app is a Navigation app for instance will allow them to successfully interpret any acronyms in sentences e.g. MLS/mls Is this an abbreviation of Miles? Is it an acronym for Major League Soccer or is it a short way of writing Milliliters? If the translator knows that this is a navigation app there is a good chance that "mls" is a shortened form of "Miles".

How do we get this extra information to Tethras?

You can upload all of this extra content via the Translation Instructions Screen. For variables/placeholders, please ensure that your code is commented per the above instructions.
Character Restrictions: We recommend that you apply restrictions only if you absolutely must. It constricts the choice of words for the translators and can often lead to a less clear translations and may increase turnaround time.

Pseudo translations

We highly recommend that you build these pseudo test files into your app prior to purchasing translations. It will highlight the following issues:

• strings that have not been externalised
• strings that may break the layout due to length restrictions

It is always quicker and cheaper if these issues are fixed prior to ordering translations. If you find strings that have not been externalised simply fix them and reload your files. If you find strings that break your layout because they are too long, you can either change your layout (recommended) or impose a character restriction on individual strings. This can be done by clicking on view strings beside each file. If strings turn out to be too long after translation then you will have to pay to have them re-translated. (Note: The pseudo translations are 30% longer than the original string length. We cannot absolutely guarantee that this will be sufficient in all cases so you may still have to pay to correct a small number of strings if they are still too long even after testing with pseudo files.)
If you are new to localization you should read the following Getting Started Guide that highlights some of the more important points before purchasing.
For more information on pseudo translation watch Video 4: Pseudo Localization.