Translation Editor

Translation Editor is not used much anymore and is minimally supported. Please use ParaTExt instead.

Translation Editor helps Bible translators enter, edit and check Scripture in a vernacular language. It allows Bible translators to:

  • use styles, instead of standard format markers (back slash codes), to mark text structure.
  • see their work in formatted “WYSIWYG”  views, including direct printing of these formatted views.
  • zoom in to view text more easily.
  • produce back-translations for checking, optionally including an interlinearization of the original text.
  • print vernacular scripture and the corresponding back translation paragraphs in a diglot layout.
  • insert and classify notes.
  • insert pictures and footnotes
  • look up words in the Language Explorer lexicon.
  • run various checking tools to find errors (e.g. versification, characters and punctuation usage, capitalization, etc.)
  • create and use a custom spelling dictionary to view possible misspellings in the vernacular language (underlined with red squiggles), and use spelling dictionaries for the languages of wider communication (e.g. in back translations).
  • change the spelling of a word in all or selected locations throughout the scripture texts.
  • access tools in Language Explorer which list misspelled words in use.
  • view the vernacular scripture translations in Language Explorer, gaining access to the concordance, interlinear tools, etc.
  • use the FLEx interlinearization tool in combination with the parser to identify misspelled words (especially useful for agglutinative languages).
  • view Biblical resources (USFM-Paratext) such as the current verse in multiple, selected translations.
  • set Libronix to open every time Translation Editor is started.
  • set other Bible software programs to scroll together with Translation Editor (e.g. Translators Workplace, Libronix, etc.)
  • identify the translation of key biblical terms to check consistency.
  • import translations which are in standard format (e.g USFM) or OXES formats.
  • export translations to USFM, OXES, RTF, and using the Pathway tool to Open Office, GoBible and other formats.

Like the rest of FieldWorks, Translation Editor uses Unicode, and stores data in a project for easy file management and back-up.

Product Overview

7 Responses to “Translation Editor”

  1. steve says:

    I have 2 Q’s:

    I downloaded the newest version of FLEx but am having trouble finding the link to download translation editor. If the editor program was supposed to be included in what I already downloaded, I somehow missed it.

    Also, as a possible improvement of FLEx, it would be really nice if when I am moving from the texts section to the lexicon section I would be put on the entry my cursor was on in the text section. I realize that more than one entry would be possible, especially in my language with lots of affixes/clitics. Perhaps it could default to the root’s entry?

    Thanks

  2. Kari Valkama says:

    Hi,

    I would like to know, when were the import export tools developed for USFM, OXES and RTF?

    Yours,
    Kari

  3. ann_bush says:

    Hi Kari, I’m not sure exactly what you’re looking for, so if I don’t answer your question, please ask again.. USFM was developed by UBS so our import/export tools were developed as part of TE when it started maybe 10 years ago so TE could communicate with Paratext. The OXES standard was developed by SIL 3 or so years ago to replace USFM. RTF is a Microsoft standard that has been around as long as Word has. FieldWorks doesn’t uses FTF. We do imports and exports using the XML standard.

  4. Eldo says:

    If I download Language Explorer (FLEx) FW705-SE do I get the transilation Editor along with that.If not how can I dounload Transilation Editor?
    Regards,
    Eldo

  5. ann_bush says:

    Hi Eldo,
    If you download the BTE version of Flex, you will get TE included. It is not included in the SE version.
    Ann

  6. Eldo says:

    Thankyou Very much Madam.I have dwnloaded the BTE and it seems a wonderful one.The problem we are facing is our language is Malayalam (India -Kerala) and we dont have a Unicord Malayalam Typing soft.Can you provide such local language typing soft or can you help us how make one(we have unicord fonts available).Our ambition is to provide some Christian free literature…

  7. Tom says:

    Eldo,
    Are you connected with others in the Bible translation movement there in India. If so, you can check with them for advice (Viji Mathew or someone at NLCI can probably help). I believe Windows includes a Malayalam keyboard, but NLCI has one which seems to be preferred. If you are not connected there, please let me know and I will try to help you further.

Leave a Reply

(required)

(required)