Frequently Asked Questions About Live
The in-context feature of Transifex Live only works with Transifex Live projects. However, our Visual Context lets you translate file-based content using screenshots.
As of right now, if you use Transifex Live, you can download your translations as a JSON Key-Value file. To do this, visit your resource details page and click on the target language of your choice. Inside the pop up window, click on "Download only reviewed translations". Unfortunately you cannot use Transifex for converting one file format to another.
Knowing that international SEO is a concern for many companies going global, we've also created the Transifex Live Translation Plugin for WordPress, the largest self-hosted blogging tool in the world, which allows you to assign unique URLs to the multilingual versions of your website and also adds hreflang tags where applicable to help increase indexability in global search engines.
If you're still concerned about how Transifex Live will impact SEO, you can run a service on your server which pre-renders the content before serving it to search crawlers. Check out our Search Engine Optimization (SEO) article article for more info.
Translations are served through our Content Delivery Network (CDN), ensuring high uptime and low latency. We only serve the translations, not your site. This means you don't give up control of your site to a third party, and sensitive information like credit card numbers don't pass through our servers. Your website's reliability and security are totally in your hands.
Transifex uses Fastly's CDN. Knowing that application downtime often means the loss of customers and revenue, we carefully selected our CDN to provide our customers with a high level of performance that helps prevent applications from crashing.
We built Transifex Live with speed and reliability in mind so you don't have to worry about end user performance being negatively impacted. When a user visits your website for the first time, translations are fetched from the Transifex CDN, and are then stored locally on the user's machine (saved to the cache on their computer). This way, when a user reloads or visits your website in the future, the translations don't have to be downloaded again. Translations will load faster and overall site speed will remain at optimal levels.
When a user fetches translations from the Transifex CDN for the first time, they may see the page in your source language briefly before the translated content appears. To avoid this translation swapping on page load, you can implement what's suggested here.
Small, weighing roughly 22kb to ensure optimal site speed.
Static, meaning it's only cached after the first request and is not loaded again until changes or updates are made to your translated content.
Delivered through our CDN (Fastly), allowing you to serve your website using your own servers.
We do not handle Ajax content, we handle dynamic changes in the HTML. So if the outcome of an Ajax call is to display new content in the browser, Transifex Live will capture that content (e.g. a popup) and try to translate it.
No, your translators do not have to use Transifex Live to finish translations and can still work in the Web Editor or download XLIFF files and translate offline. We do, however, recommend at least using Transifex Live to review translations in context.
Approving/removing strings from a TX Live resource as well as publishing translations are actions that can only be performed by administrator users and maintainers.
<head> element of your site's HTML. You only need to do this once, and it'll allow you to use Transifex Live and publish translations.
- You'll be able to use the Transifex Live sidebar and translate directly on your site.
Yes, Transifex Live has been fully tested on Chrome, Safari, Firefox, and IE 9, 10, and 11.
Note that with Internet Explorer, hexadecimal colors in inline CSS containing is converted to RGB, thus creating a different signature for the same source string. To fix this, you can:
- Include styling in classes which works fine across browsers.
- Add the notranslate class to elements containing inline css.
- Define color styling using rgb and not hex values.
By default, Transifex Live automatically handles static content, i.e. HTML that's initially loaded from the first HTTP request. However, you can still translate dynamic content with Transifex Live using one of the following methods:
Refer to this article for details on using Transifex Live with dynamic content.
Yes, you can. The Transifex Live sidebar works directly on your site, so you'll be able to navigate to pages that are behind a login.
Transifex Live automatically detects the URL and feeds the right language. Related information about this can be found here. However, you may want to create a custom language picker to redirect your visitors accordingly. For example, when a user selects German from your home page using your site's language picker, they will be redirected to
http://www.example.com/de instead of seeing the German content on the same page. If you need more information about creating a custom language picker, check this article here.
Sometimes, when you have dynamic content, such as user names, they will be collected as well. However you can disable collection and translation of those strings by adding the "notranslate" class on the encapsulated html tags.
Also strings appearing in the Detected tab do not affect your billing quota. Those are just strings that are candidates for translations. Only strings in the Approved tab affect billing, which are strings that have been approved for translations by you.
Yes, to access your staging server through Live, first whitelist the following IP addresses:
Next, go to the Detailed view of your Web project, select Resources, pick the resource, and hit Settings. From there, you can set the staging domain. Note that content from the staging domain will be saved to the same resource as the production domain.
In the Publish widget, you can choose to make translations live either on your production site, or your staging site. Publishing to a staging server is useful for testing and if you have content on your staging site that's not ready to go public yet.
Nope, nothing changes in the API.
If your website is performing AJAX requests to show certain functionality or content, those requests might fail because in the Transifex Live preview, your website is loaded under the
live.transifex.com domain, yet you are requesting data from
your.domain.com, which the browser will block for security reasons. You can fix this by enabling Cross-Origin Resource Sharing (CORS) for the
live.transifex.com domain on your web server, like so:
For more information on how to enable CORS on various web servers, take a look here.
Yup. If you're running experiments in the source language, Transifex Live will not interfere at all.
$("h1").replaceWith("<h1>Localization doesn't<br> have to be hard</h1>"); window.Transifex && window.Transifex.live.translateNode($("h1").get(0));
When your site is being loaded through Transifex Live, it's actually loaded through one of our proxy servers. This requires whitelabeling, and unfortunately, there isn't any documentation regarding security implications, but we haven't had any reported issues. Transifex has no intention of accessing your code or making changes to your website. Our goal is simple: to provide you with the easiest way to localize content quickly and efficiently.
You can prevent sensitive data from ever going to Transifex by doing the following:
- Turn off auto detection of content by going to the Transifex Live settings and unchecking Identify new strings when page content changes. When auto detect is off, you'll have to visit a page directly while logged in to Transifex in order for content to be detected.
- Transifex Live by default doesn't save any data present in input fields, such as signup forms. The only way sensitive data would be detected is if the content is displayed in the HTML itself. In that case, you can tell Transifex Live to ignore a block in your HTML containing sensitive data using a notranslate class.
The approved strings and translations are not going to be removed if you change the website URL - if the content/strings remain exactly the same.