jmleray@translation2.com

Translation 2.0 Multilingual Terminology Search Engine / Moteur de recherche terminologique multilingue Translation 2.0

  

 

get translation 2.0 in your toolbar

Google Custom Search

 

 

Translation 2.0 Multilingual Terminology Search Engine -/- Moteur de recherche terminologique multilingue Translation 2.0       

Translation 2.0 Search Engine FAQs

- Is Translation 2.0 a multilingual search engine or an automatic translation service?

- What is a multilingual terminology search engine?

- What languages does Translation 2.0 search in?

- Why use Translation 2.0 and not Google?

- How do I find the terms I am looking for translated into other languages?

1) Common sense

2) Search engine syntax

- Can I add a resource (a site) to the Translation 2.0 search engine?


- Is Translation 2.0 a multilingual search engine or an automatic translation service?

Neither. A multilingual search engine automatically translates your request and submits it to search engines in multiple languages. A translation service automatically translates the terms in your request into the language you selected.
Translation 2.0 is a multilingual terminology search engine...
Top

- What is a multilingual terminology search engine?

It’s a search engine that quickly identifies relevant multilingual resources so you can find the terms or documents whose translations you are looking for in multiple languages. Top

- What languages does Translation 2.0 search in?

All languages; however, for the moment those with the greatest representation are English, French, Spanish, Italian, German, Portuguese, Dutch, etc. Top

Why use Translation 2.0 and not Google?

Simply because a general search engine like Google that indifferently indexes billions of resources creates a lot of noise, in other words, it gives you lots of results that have little to do with your search. On the other hand, a specialized engine like Translation 2.0, which contains several thousand specialized, term-rich resources, gives only relevant results that contain a response to your search. Just try this "test" search to compare Google and Translation 2.0. Top

- How do I find the terms I am looking for translated into other languages?

By refining your results step by step, in other words, by applying a twofold search strategy based on 1) common sense, and 2) the search engine’s syntax. Top

1) Common sense

When you submit a query to a search engine, the keywords you choose are a deciding factor in the success of the search process. Consider them carefully before starting your search.

a)  When you type the word(s) you want to translate into the search field, the first trick is identifying the bilingual or multilingual sites found by translation 2.0. In fact, sometimes all you need to do is toggle languages to see the translated page. For example:


b) If the above principles don’t yield the results you’re looking for, the second step is to type your request terms in both languages. Just follow this road to success:

- Each query must indicate: source language term(s) (ST) + target language term(s) (TT).

However, if you are looking for a translation, that supposes you do not know the corresponding target term. No problem: you know other terms – the relevant sector, a related term or a generic term like "glossary”, “vocabulary”, “dictionary”, “terminology”, etc. – that you can mix in.

Let’s try an example. Suppose you had to translate the source term immunoassay into French:

ST + Relevant sector = immunoassay "médecine"

ST + Related term = immunoassay immunologie

ST + Generic term = immunoassay glossaire / immunoassay français

Mix = immunoassay médical lexique / immunoassay médecine glossary

In every case, you can find the answer by exploring links in the very first page of results: dosage immunologique, or even immunodosage.

But to make your search even more effective, the golden rule is to use and combine the main commands of Google’s search syntax with your terms. The most useful commands for translation 2.0 are as follows.
 Top
 

 

2) Search engine syntax

Search engine syntax: Table of the most useful commands for multilingual terminology searches

TS + TC

 

Main type of query combining a source language term (ST) and a target language term (TT).

Note that putting the terms in quotes allows you to search for a specific expression ("medical term" / "terme médical") or the exact spelling. For example: médical without quotes returns medical and/or médical; "médical" returns only médical. Very practical for languages with diacritical marks.

 

Filetype:

 

Command used to filter results by file extension, returning only the selected file types. The most common extensions are: .PDF, .DOC, .XLS, .PPT, .PPS, .RTF, .TXT. Exclude file types by adding - before the command (-filetype:pdf excludes all .PDF files from the results.)

Adding this syntax to the preceding query restricts the number and also probably increases the relevance of results.

 

Site:

 

Command enabling you to search only in sites with the desired extension; very practical for restricting your search to one country.

It is also possible to restrict your search by language, using the language restrict operator (lang_en, lang_fr, etc.)

 

Inurl: / Allinurl:

 

Inurl: searches for URLs containing the first word after the colon, whereas allinurl: will find URLs containing all the terms in your query.

 

Intitle: / Allintitle:

 

Same characteristics as the previous command, searching for the designated term(s) in document titles only.

 

Intext: / Allintext:

 

Again, the same: searches for the designated term(s) in the body of documents only.

 

Mix

 

You can easily combine the above commands within one query, both to restrict the number of results returned and to increase their relevance.

Note: In combination queries, use only the command intext:, not  allintext:.

 

- Can I add a resource (a site) to the Translation 2.0 search engine?

Yes. If you know a relevant site that has not yet been indexed by the engine, just send me a mail. You can also notify me of broken links, and in general share your observations, feedback and testimonials by writing to jmleray@translation2.com. Top



 
Home | FAQ_EN | FAQ_FR| Results | Comments


Partners : Studio 92 - Multilingual XBRL Taxonomy


© 2007-2011 Jean-Marie Le Ray