translation
Description
An FQL table which returns any translated strings for your app as well as the original untranslated strings.
Columns
| Name | Description |
|---|---|
approval_status string | The approval status of the string. The status is one of: auto-approved: Automatically approved by our system, based on votesapproved: Manually approved by you, another developer of your application, or an authorized translator*unapproved: Not approved in any manner |
best_string string | The translated string that gets displayed to a user translating your application. The user must be browsing Facebook in the locale of the approved translation. Querying on this column returns either a native string or translated string. If no entry for the corresponding native string exists in the Translations database, this column returns |
description string | The description of the native string needing translation. This text clarifies the context in which the text is used, and the meaning if it is ambiguous. This is shown to translators in the bulk translation user interface, among other places, and should describe the text well enough that someone can translate it without seeing it in the context of your application. In general a piece of text should always have a description unless it is a complete sentence whose meaning would be clear to a user who has never seen your application. If a description for the corresponding string or hash doesn't exist in the Translations database, this column returns |
is_translatable number (min: 0) (max: 1) | Whether the string is translatable. Strings are translatable only when the user making the request is in in translation mode and there's content yet unapproved |
locale | The locale for the translations for which you are querying. You can specify a locale of |
native_hash | A hash of the native string and a description. It's a unique identifier for the string. Query on this column to quickly return your application's native strings and their descriptions |
native_string string | The actual text from your application you previously submitted for translation to the Translations application |
pre_hash_string | A concatenation of the native string and its description. This string is used to generate the native hash. The native string is concatenated with 3 colons, the description, then another colon. Query on this column if you want to check whether a random string and description exists. A query containing the pre_hash_string runs more slowly than a query containing the |
translation string | The translation of the native string. If a translation for the corresponding string or hash doesn't exist in the Translations database, this column returns |
translation_id string | ID of the translation |
Examples
- SELECT ... FROM translation WHERE locale = A AND native_hash = B
- SELECT ... FROM translation WHERE locale = A AND pre_hash_string = B
Note: Additional filters on other columns can be specified but they may make the query less efficient.
Permissions
To read the translation table you need
- any
access_tokento read the translations for the app.
In order to make your query indexable, the WHERE in your query must contain an = or IN clause for the locale column and either the native_hash or pre_hash_string column.