Transifex

  • Documentation
  • Projects & Content
  • Edit Source Strings

Edit Source Strings

Note

This feature is currently in beta (it is only available on the Pro plan and up). In order to try this out please contact us at support@transifex.com.

No need to rely on developers to fix minor typos and wording in source text by having them continuously upload source files. Such limitations cause delays in the localization process which means that tight deadlines might have failed to be met. Project maintainers can improve the wording in the source text by using the Transifex Web Editor. Customers who want to ensure proper grammar and alignment with other resources (marketing emails, Company’s Website) can now simply use the Translation editor in the same manner that they translate strings to other languages. After all the quality of the source text does matter.

  • Allowing users to modify the source text directly in Transifex. This only applies to resources that are key-based.

  • The Transifex platform now becomes the source of truth for source strings as well as Translations.

  • While in Beta, this functionality is only available to Project Maintainers and Organization Administrators.

  • This function is only supported for file formats with a key value structure. Source strings can be edited when uploaded using one of the following file formats:

    • Android XML
    • Apple PLIST
    • Apple Strings
    • Apple StringsDict
    • Chrome i18N
    • FreeDeskTop
    • PO (Gettext)
    • Java Properties
    • Java XML
    • Joomla (INI)
    • KeyValueJSON with ICU plurals
    • Structured JSON
    • Magento (.csv)
    • Microsoft Excel (.xlsx) -> Note: the key must be indicated in the .xlsx file.
    • Mozilla DTD
    • Mozilla Properties
    • PHP
    • Require JS
    • Wiki Markup
    • Windows .NET (Resx, Resw)
    • Windows JSON (resjson)
    • YAML
  • Because this feature is currently in Beta, it does not work for TX-Live and TX-Native projects.

  • Source strings uploaded using one of the following key-less file formats can't be changed in the editor; Word document (i18n type: DOCX), TXT (i18n type: TXT), HTML (i18n_type: HTML, XHTML), Subtitles (i18n type: SRT, SUB, SBV), XLIFF (i18n type: XLIFF), InDesign (i18n type: IDML), Markdown (i18n type: GITHUBMARKDOWN), TS (i18n type: QT).

  • There is no option at the moment, to overwrite updated source strings in Transifex when uploading a resource file via Github/Bitbucket/Zendesk integration. If there are source strings updated in projects with such integrations, the resource file should be downloaded from Transifex and replace itself in the code repository. In this way, existing project integrations will not break and both Transifex and code repository will be synchronized.

Where To Modify A Source String.

There are at least 2 ways to Modify a Source String. They are:

  • From Project->Resources, click on the Edit Source Strings link as seen below:

    pic1_200702_103922.jpg#asset:7480

    note: if this link does not appear then that means that the file format does not allow for source string edits.


  • From the translation editor select the source language from the drop-down list, or click the Edit Source link:

    pic2.jpg#asset:7382


  • The user changes a source text and saves the new version. The string is marked now as updated. If there was a translation for this string, it has been removed (but it is still in the TM!).

  • Each update from the original source text is logged: the user can see the different versions in the history tab. If the source string is not updated, the history tab will be empty.

    pic3.jpg#asset:7383

  • If TM Auto fill-ups are enabled and the updated source text matches an existing source text in Translation Memory or the Translation Memory group, then the translation will be filled in automatically.

  • The user changes the source text but to its original version (before update) and saves it.

  • If there was a translation for the original source text, it reappears (after switching to a target language);TM auto-fillup kicks in again, if it is enabled.

  • If the user changes the source text by deleting all text, then the Save button is disabled.

  • While the user edits the source language, the filter "edited_source_string:yes" or "edited_source_string:no" will be available. 

  • If the user selects "edited_source_string:yes", then any string of a specific resource that has been edited, will show up in the results

  • If the user selects "edited_source_string:no", then any string of a specific resource that hasn't been edited before, will show up in the results

  • The filter 'source updated before/after' should work based on the fact that an updated string was edited.

  • From the UI: Update the resource using the instructions indicated here. Note that an option appears to replace edited strings. Checking this option overwrites updated strings modified in the editor.

    pic5.jpg#asset:7390


    Please note that, if the uploaded resource does not contain source strings that exist in Transifex, these will be deleted in Transifex, regardless if the option 'Replace edited strings' was checked or not.

  • From the API using the update resource endpoint. Please note using the API will not replace edited strings in the beta release.

Updating Resource In User's Code Repository

There are two methods of updating the original source file located in your repository with updated strings (Source strings that have been modified):

  • Through the UI. Go to Resources. Then select your resource. Click on the source language in order to get the popup that appears below:

    pic-4.jpg#asset:7386

    Select the download resource link.

  • Using the API developers will periodically update their local source files with what's in Transifex.