How can you ensure technical translations are jargon-free?

Is this a trick question? A technical translation may need to be full of jargon. It depends on the target audience and the nature of the text. You translate with those and other points in mind. The way to make sure it has the right language is to be a good technical translator. If you need to proof your own text for correct language, you might be doing the wrong job.

As a marketeer in web3, I think we have a way to go when it comes to education as a main barrier to use. Currently web3 use is limited because of the jargon-heavy approaches that promote exclusions rather than invitation to use this technology. Jargon is a really big issue when it comes to understanding and adoption so people feel that the possibilities are too complex or even a bit shady. The more people understand web3 in a language that they speak and understand, the more attractive it will be to them and they can start to experiment more within an industry. This is what I would love to see and then find out what people can really do with this technology.

Providing good technical translations is best possible when the source text is well written. Providing excellent technical translations, irrespective of the source quality, is entirely due to the skills, knowledge and expertise that professional technical translators can offer.

My best tipp is to use understandable, well-known synonyms. In some cases, technical terms may be unavoidable, in which case it is better to add a short, understandable explanation. Using simplified language can also be a good solution.

Indeed, go and spend launch time with your audience, listen how they talk to each other, come and see them working and try to figure how they communicate. Later catch one of them and ask him: "How did you tell the other guy...?" or "In your country how do you call this or that..."

Avoiding literal translations can help produce more accurate, natural, and engaging translations that respect the original text and its audience. A good translator should not only know the languages well, but also understand the culture, context, and purpose of the text. A good translator should also be flexible and adaptable, and use various strategies and techniques to overcome the challenges and limitations of translation.

Context is king, context is everything, context is your friend and ally. As a professional translator and language teacher, I never give the definition of a word without asking for its context. I apply this approach to all my translation projects, which span literary text, such as poetry and prose, dialogue, academic papers and much more, allowing me to provide an output that is as humanly accurate as possible.

To some extent I agree but since translating a term into target language that it is also important to add value to the target language by creating terms based on target language; since a language is dynamic in terms.

Avoiding literal translations is generally a good principle. However, it may not apply in the case of patent translations, where accuracy of translation is the most important thing, even when there are errors in the original, as is not infrequently the case. Back in the days when a translator actually certified translations of European patents for the UK Patent Office, they had to certify that it was a "true and correct" translation, and that principle still applies, regardless of any errors in the source.

For example in Hebrew beit sefer is a school but literally it's a book house which has no significant to the original meaning.

This definitely solves much of the issues faced when translating technical documents. By creating glossaries and style guides translators' work can be 10X-ed as they will not waste time conducting research and trying to agree on definitions and "safe" expressions. The first step includes having glossaries and style guides. The rest is a little more straightforward.

However, you almost never break down long sentences in patent translation - I'm not sure whether I've ever done it. I might split a sentence into two by using a colon sometimes, but not much more than that. 300-word sentence in the original? The translation needs to be of a corresponding length, especially patent claims, which should never be split: it's vital that they stay in one piece. But then patent translation is a law unto itself, which is why it should always be done by specialist translators.

One thing I've found is that translating long tecnical stories from one language to other can lead to frastration, intrest losing, inaccurate or even no sense to the other language. On the other hand it can work out if you try short, precise and clear sentences one after the other. Also prefer to use well-known vocabulary, avoid complicated grammar, making sure syntax and semantics work well together on the other langauge too. It is important to catch the attention and interest of the listener just like in any conversation and see if there's any understanding signs from the listener. It can be by words like: "yes, I understand, I see etc." or by nodding, eye contact or body language that shows collaboration of the listeners.

I have found that presenting as key bullet points helps the reader to understand much better. and help the translator/writer to be more concise.

Simplification and conciseness are the hardest things to achieve. They are a sign that the translator or writer are truly in tune with the language. One thing I try to do is, to keep my mind working in the target language, understanding it as a native and translating with the big picture in mind, as well as the details. It might sound a little counterintuitive, but I try to read the original text, forget it and then tackle it from the perspective of the target language.

A real story I withnessed. One day during a safety briefing the supervisor who did not know the language of the listeners said: "If there's an alarm, run to the road!". It was so troubling, making confusion and panic. But then a profesional translator mate came and asked permision to talk on the microphone and said: "When you hear high and low sounds from the announcement system please leave your work station and wait along the sides of the road. It was realy much better!

Telling a story always makes it more interesting and relatable to the readers. Gets their attention and keeps it for the entire story (if a good story!).

While visuals are helpful, it's best to use them only if they can fully exemplify the topic and reflect the current version of the product. A product's software tends to update quickly, so taking and using screenshots that accurately can get difficult, especially in the context of documentation maintenance.

Get feedback from people who are not experts on the subject, but rather people who have a basic understanding of the topic. Should the translation be fully understood, then you are safe.

In addition: Hire Specialized Translators: Employ translators who have expertise in the specific technical field. They will have a better understanding of the jargon and how to translate it effectively. Consistency is Key: Ensure that terms are translated consistently throughout the document. This helps in avoiding confusion for the reader. Stay Updated: Technical fields are constantly evolving, and new jargon can emerge. Regularly update your glossary and stay informed about changes in the industry. Use Technology: There are translation memory tools and software that can help ensure consistency and accuracy in translations. These tools can store previously translated terms and suggest them when the same terms appear again.

I suggest a translator to do a follow-up a while after he finishes his work, if it's possible, and check what was the react of his translation. To ask himself, did they understand me? Did they follow the instructions or reach out the information they needed? How good and faithful to the original was my work? And what else can be done to improve? I believe words has power if they didn't fall on deaf ears.

Our local corporation in my country rarely has an in-house translator, they usually put this job desk in some appointed department that deals with documentation. Actually, this is one of the important roles, especially when the translator has a special certification, such as a sworn translator.

Cross-referencing technical terms in both your working languages is crucial - sometimes a standard dictionary may not be sufficient. Key tools for me when translating are specialised terminology databases such as IATE (useful for European languages and semi-specialised terms) and WIPO Pearl, a terminology portal specifically for technical and scientific terms that displays real, in-context examples. These tools coupled with data and language mapping tools like Sketch Engine allow me to chose terms with confidence, especially when texts call for a high level of technicality.

Based on my experience, ensuring technical translations are jargon-free requires a deep understanding of both the source material and the target audience. It's essential to research and comprehend the technical concepts being communicated, while also being mindful of the language proficiency and background knowledge of the intended readers. Clear communication and the ability to convey complex ideas in simplified terms without sacrificing accuracy are paramount. Additionally, regular collaboration with subject matter experts and continuous refinement based on feedback help maintain clarity and effectiveness in technical translations.