Markdown <-> memoQ

#1

July 31, 2018 1:55 PM

STAGE 1. Work Involving Software Team

  1. The English source text can be downloaded from the door43 website, https://git.door43.org/Door43-Catalog. The catalogue organization and various projects can be browsed here.

  2. The best way to find the specific English repository is by the links from the uW (unfoldingWord) website, https://unfoldingword.org/content/. Scroll down to Dictionaries and click on the link translationWords (tW) -Stable
    image

  3. Now click on view source as seen in the image below
    image

  4. This will direct to Door43 catalog page for English translation Word resource. To do a diff Comparison of the versions click on the link as shown in the following image.
    image

  5. Click on Split View to see split screen of the diff comparison the same window and click on the Show Diff Stats (follow green arrow) to see the diff under each word.md file.
    image

  6. In certain cases, like tN it is always better to start using the latest release from the unfoldingWord organization https://git.door43.org/unfoldingWord/en_tn/releases .

  7. As an e.g., tW source text in English can be downloaded form this link https://git.door43.org/unfoldingWord/en_tw/releases . Click on Source Code (ZIP) to download the resource (red arrow). Always make sure that you are downloading the latest version (follow green arrow). To do a diff comparison click the link under changelog (orange arrow)
    image

  8. To view the diff comparison, follow step 4 & 5.

  9. Click on the link “Source Code (ZIP) for windows users. TAR.GZ if for Mac users” as shown in the image above (red arrow) to download the resource.
    image

  10. A zip fileimage will be downloaded to Downloads folder by default i.e.to My Documents  Downloads, unless saved to other location manually. This is applicable for users using image version 7 and up.

  11. The downloaded file has a lot of links and information that need not be translated. Each resource has a Python script that is run to remove links. For tW “removelinks.py” is used to remove links and other information that need not be translated.

  12. After the links are removed the file is ready to be pushed into memoQ as a bi-lingual document, ready to be translated by the translation team.

  13. NOTE: To download the latest repository that includes all the current updates follow this link https://git.door43.org/unfoldingword/en_tw . To download the resource, click on the download link as shown in the image below (red arrow) and follow steps 9 &10. To view diff comparison, follow steps 4 & 5. All the previous versions of the resources used for translation should always be compared with the latest ones and the changes needs to be incorporated by checking with the diff comparison.
    image

STAGE 2 Using memoQ for Translation

  1. Open memoQ

  2. On the top left corner click on memoQ tab next to project tab

  3. Click on the New Project under My memoQ tab to create local or online project

  4. Click on ‘New Project’ as shown in the image below
    image

  5. Give a name for the project and set the target language as shown in image above

  6. Click ‘Next>’ to go into the next window

  7. You can import the “Source Text” by clicking the import option or the source text can be imported at a later stage. As in this case click Finish to complete setting up the new project.

  8. Click on Translations under the overview as shown in image below.
    image

  9. Right click on the blank space as shown in image below click on ‘Import Folder Structure’. You can click on any of the options i.e. ‘Import’ or ‘Import With Options’. In this case we will go with the Import Folder Structure to import the files in one go.

  10. Click on three dots … as shown in the image below to select Source files in Base Path.
    image

  11. Select the folder where you have the source files saved. As in this case the files are saved on Desktop Exegetical WorktA&tW&tNen_tW 28 Feb 18 v.8. Select the folder for the file to be uploaded to memoQ
    image

  12. After selecting the folder, the next step is to click update and then define the files extension i.e. “.md” next to ‘Include Files’ Textbox as mentioned in the image below.
    image

  13. Check if the files have been imported as .md extension as mentioned in the image below and click OK.
    image

  14. On the next screen towards the left we see tW with .md extension having an exclamation mark in red image and under the Filter segment you will see “Unknown filter”

  15. Click the Filter and a dropdown menu will pop up. Select “Plain Text Filter” from the list for .md format files

  16. Once the “Plain Text Filter” is selected the red exclamation mark image turns into green image check mark and under the filter tab the “Unknown Filter” changes to “Plain Text Filter”. Click OK to continue

  17. Now you see the status bar progressing as it is getting the source files imported. Wait for this process to complete. It may take some time.

  18. Once the source files are imported the tW files can be displayed in .md (Markdown) format.

  19. Double click each word.md file to see the source translation. These files can be exported and
    assigned to translators for translation. The assigned file should be in RTF (Bilingual format). Clear orientation should be given not to edit or delete any file code or source text, by the translators. Translation must be done on the target without any source text being touched.

  20. In case of direct translation in MemoQ, you may exclude the procedure for “LiveDocs”. However if work assigned to translators is in bilingual format then LiveDocs needs to be created and the relevant translated files should be imported.

  21. Click on LiveDocs as seen in image below. Right click for options to create a new LiveDocs.
    image

  22. Fill the information for Corpus properties. Give a name for the Corpus. And click OK.
    image

  23. Once the LiveDocs is created the next step is to create the Translation memories. Click on “Translation memories” and right click in the area as shown in the image below. Click on the Create/Use New option
    image

  24. Give a name for the New Translation memory and click OK.
    image

  25. Click on LiveDocs after creating the Translation memory and right click on the space as seen in the image below to show options, click on Import Document or Import Folder Structure to import translated files.
    image

image

  1. You can select all the files together or select it one by one after clicking the Import Document option and then click “Open” button

  2. The extension will show as .rtf in the next window as the file exported is in RTF format for the translators to translate. After the translation is completed you need to import the file back in RTF format and then click OK.

  3. Under the - show all – you will see the file. Open the file by double clicking

  4. The next window will open in memoQ bi-lingual format.

  5. Click on Project home and click on the file that you want to work on and right click on the file and click on TasksPre-Translate as shown in image below.
    image

  6. A Pre-translate Statistics windows opens. Under lookup make sure that the radio button is selected for “Exact match” as shown below and then click OK.
    image

  7. Double click on the file that you pre-translated to see the content. To select the entire source and Target Press Ctrl+Shift+A.

  8. After the screen is selected press Ctrl+Enter Key together. Now all the segments turn green in color. Click on Project home tab.

  9. The file that you worked on shows the progress as 100%, in green. Right click on the competed file and export it in Dialogue. This file is to be saved in a different folder of your choice and it is to be replaced with the links and other information that was removed prior to importing it to memoQ in the final checked and approved stage.
    image

STAGE 3. Checking Process

  1. The checking process involves the translated files to be quality checked

  2. Checking the quantity of work

  3. Send the content for community check and further levels of the checking process until approved.

  4. Extract the final out and send the files to the Software team for adding Links and other omitted information

STAGE 4. Work Involving Software Team

  1. On receiving the final work, the software team will run the python script “placelinks.py” on the file to re-instate the links and information that was removed, prior giving it to translation team.

  2. The final product before uploading should be sent by the Software team for suggestions and help if needed.

  3. The issues related to formatting needs to be addressed here

  4. The file extension should be in Markdown format and the file needs to be uploaded to door43 finally.

1 Like

#2

Refers to Stage 1, point 6: In which cases is it better and why is it better? Without further explanation, the person reading these instructions won’t know what to do.

0 Likes

#3

I did not realize that, Let me make it more clear.

0 Likes

#4

Stage 1, point 13: My understanding from Jesse is that if using the unfoldingword version, instead of the catalog version, the content will need to be forked (not downloaded) in order to capture the version history. You can double-check that with Jesse.

0 Likes

#5

I think this title comes from the BCS description which doesn’t really fit here. In this general context, it might be better to say: “Downloading or forking the source content in MD format” or something along those lines to describe the objective of Stage 1.

0 Likes