English | Français | Deutsch | Español | Català | Portugues
Documentation | TranslationTool
1. status: To Do
2. status: I'll Do it
3. status: Part
4. status: For revision
5. status: Done
If someone wants a text to be translated, it should be posted with the status "To Do". The translator can select this text and before s/he starts, s/he makes a comment to it, which says something like "I will do it" and switches the status of the request to "I'll do it" using the "edit" link on the top right of the page, so no one else will waste time in translating the text a second time.
Finally the translation will be posted (again as a comment to the original text) and the status will change to "For revision" or "Done". Thats all.
If a translator can't translate the whole proposed text, s/he can post a part of the translation with the status [Part]. Another translator can then finish the translation.
In the left column we have the logo, a pull-down-menue to select the language of the user interface, a list of language-links, a search interface, a short user guide, a few upcoming events and the list of indymedia centers which you will find on every indymedia-startpage.
When the startpage is loaded, the server will detect the browser language setting and tries to give you a user interface in the corresponding language. The default is English. The pull-down-menue below the logo gives you an additional possibility to switch to another language for the user interface. Help texts and navigational elements like links, buttons and labels will appear in the language you select here.
The language links help you to sort the center-column. If you click on "en", the language code for "english", all articles with "en" somewhere in the topic / language field will appear. (Note, that the language of the user interface will not change! The language of the user interface depends only on your browser language settings and the selction of the pull-down-menue below the logo)
For the guide to the search interface see below.
The right column has a news feed on the top, followed by rss/rdf-syndication links, and an open posting newswire - not for translations but for translation work specific technical, organisational, etc. topics. The preferred language here is english.
Also on the right side (upper right corner) you see a news feed, included with rss/rdf-syndication from the open posting news wire of http://www.indymedia.org .
The same technique used for including a news feed from somewhere else can be applied by the users of the TranslationTool: The Tool produces several rss/rdf-feeds, that you can access using the urls called "All" | "To Do" | "Rev" | "Done". Whenever an article is done for example, the rss/rdf-feed called "Done" will send you a notification.
Having posted a "To Do" article doesn't mean at all, that the article will get translated. Translators translate whatever they like and often look for articles, they would like to publish in a different langage, by themselves.
Do a translation
You can add infos like the time until you think you'll have finished the translation or ask for help, etc. in the body field. Don't forget to switch the status of the request to "I'll do it" using the "edit" link on the top right of the page.
| Using this table of radio buttons you can insert the language code syntax, depending on the phase of the translation process more easily and faster. But you don't have to use it since you can edit the topic/language-field as before. But you don't have to use it since you can edit the topic/language-field for as before. Each column stands for one target language (eg. en for english). A selection of a radio button in a "to do" - row below 'en' inserts [en: todo] in the input field above the table; a selection in the "done"-row inserts [en: done] a selection in the Reset-line deletes the entry of a special language. You can select only one radiobutton in each language column. New entries are attached to the end of the string in the input field. The topic keywords are not touched. More language columns can be added to this table. For the moment we added only those, that were used most on the translation tool. But please don't hesitate to use the tools for other languages! Just keep the same syntax and use the appropriate language codes. |
Topic / Language
|
The search capabilities are at the very core of this tool. Advanced search functions are used to sort the translations by date, topic, languages, authors or create rss/rdf-feeds. Every article gets indexed immediately after being published.
Searches can be initiated by special links (language links in the left column; "To do", "I'll do it", "Part", "For revision" and "Done"- icons above the center column) and by filling out the search form on the left column. Also the urls behind the red coloured keywords are predefined searches for terms in the topic/language field.
The matches of every search are sorted by date and diplayed in reverse order (the newest article that matches you query is shown on the top).
The search functionality corresponds directly to the metadata input: Only through good input into the different fields of the posting form you will later get the search results you need to find everything.
You can search for articles or comments depending on which radio button is selected. Article search is the default. If you select comments, and status "All", you will get the most recent comments which were published, so you can quickly see if somebody added a translation.
This search form uses different fields to search for strings: the title/author/language-topic/body - fields. The easiest way to start a query is to type a term into a search field and hit enter (alternatively you can click on the search-button).
You can use boolean algebra in your searches: If you type several terms into one search field (seperated by spaces) they are by default combined throught logic "AND". If you want to find every article containing the word India or Narmada in the title string, use "India OR Narmada" as search term of the title field.
If you want to search for all articles of a special language, use the language links above the search form or type the language code ("en", es", ...) into the topic/language field.
If you fill out two (or more) fields for the same query, all search conditions have to be true, to match an article. They are connected through boolean "AND". For example if you search all articles concerning Argentina that already have been translated, type "Argentina" (lower/upper case doesn't matter) into the field with the label "topic/language" and select "done" from the status-pull-down menu.
Multi language search Diacritical characters like "ã" in "São Bernardo" or "í" in "Cronología" matter in your query: you would find a match using the term "Cronología" but not using the term "Cronologia" if "Cronología" was given in the title field during posting.
Advanced Searching(derived from the Zope Book:) The Search Interface supports a rich search grammar for doing more advanced searches than just looking for a word. For example you can use a google-like syntax with parentheses, AND/OR/ANDNOT, +/-, phrase search and wildcards (*,?) Boolean expressions Search for Boolean expressions like: word1 AND word2 This will search for all objects that contain both "word1" and "word2". Valid Boolean operators include AND, OR, and NOT. A synonym for NOT is a leading hyphen: word1 -word2 which would search for occurences of "word1" but would exclude documents which contain "word2". A sequence of words without operators implies AND. A search for "carpet python snakes" translates to "carpet AND python AND snakes". Parentheses Control search order with parenthetical expressions: (word1 AND word2) OR word3) This will return objects containing "word1" and "word2" or just objects that contain the term "word3". Wild cards Search for wild cards like: Z* which returns all words that begin with "Z", or: Zop? which returns all words that begin with "Zop" and have one more character - just like in a Un*x shell. Note though that wild cards cannot be at the beginning of a search phrase. "?ope" is an illegal search term and will be ignored. Phrase search Double-quoted text implies phrase search, for example: "carpet python" OR frogs will search for all occurences of the phrase "carpet python" or of the word "frogs" All of these advanced features can be mixed together. For example: ((bob AND uncle) NOT Zoo*) will return all objects that contain the terms "bob" and "uncle" but will not include any objects that contain words that start with "Zoo" like "Zoologist", "Zoology", or "Zoo" itself. Similarly, a search for: snakes OR frogs -"carpet python" will return all objects which contain the word "snakes" or "frogs" but do not contain the phrase "carpet python". |