|
About the Articles Knowledgebase
|
ProZ.com has created this section with the goals of:
Further enabling knowledge sharing among professionals
Providing resources for the education of clients and translators
Offering an additional channel for promotion of ProZ.com members (as authors)
We invite your participation and feedback concerning this new resource.
|
|
|
|
|
Recent News
Featured Articles
»
La representación del personaje de Tristana en la novela de Galdós y en la película de Luis Buñuel
|
|
La representación del personaje de Tristana en la novela de Galdós
y en la película de Luis Buñuel.
|
Recent Articles
»
Poza tłumaczeniem: co może ujawnić analiza wielojęzyczna i OSINT
By Bartosz Pelka
| Published 09/7/2026
| Getting Established , Marketing Your Language Services , Miscellaneous , Technology , Translator Education , Other Specialties , Translator/Client Matching , Other , Polish , News , Opportunities | Not yet recommended
|
Większość pracy wywiadowczej i w OSINT kończy się na angielskim. To, co naprawdę ciekawe, zaczyna się tam, gdzie tłumaczenie w ogóle nie powstaje — na przykładzie jednego cyberataku i pięciu języków pokazuję, ile ta luka faktycznie kosztuje i dlaczego na ten sam problem trafia się w due diligence, wywiadzie konkurencyjnym i ocenie ryzyka.
|
»
Beyond Translation: What Multilingual OSINT Can Reveal
|
|
Most OSINT and intelligence work stops at English. The interesting part starts where translation never happens at all — using one cyberattack and five languages to show what that gap actually costs, and why due diligence, competitive intelligence and country risk all run into the same problem.
|
»
Seven Hundred Languages and a Font Problem
|
Indonesia has more than 700 living languages, and keeping them alive requires two different things that people tend to conflate: a record and a speaker. The record side runs into concrete obstacles — scripts that reached Unicode late or, like Pegon, not at all; Javanese material trapped in legacy fonts that no search engine can read; thousands of digitized *lontar* sitting as images because nobody has transliterated them; recordings labelled too vaguely to be useful. On the technology side, roughly ten of those 700 languages have usable corpora, and the parallel text that does exist is mostly scripture, which teaches machine translation a sermon register unfit for a tenancy agreement. That gap is where translators have a stake: orthography decisions, terminology for modern domains, legal and medical register, evaluation standards, and control over who gets to train on an elder's voice. But none of it makes speakers. Digitization buys time; only a household passing the language to a child keeps it alive.
|
»
OmegaT 6.1: How I Fix Word Export Errors Every Time
|
|
I learned that OmegaT-to-Word export problems are usually not because OmegaT destroys a document, but because Word files are complex .docx archives made of XML that OmegaT rebuilds using inline tags to preserve formatting. From my experience, the most important lesson is that those tags are not clutter; they are what keep the Word file structurally intact, so deleting, moving, or misplacing them can corrupt the exported file or scramble the formatting. I also see OmegaT 6.1 as a worthwhile release because it brings Java 21+ support, native Apple Silicon and ARM Linux builds, improved spell checking, LanguageTool 6.5, better packaging, and important bug fixes, but I know those upgrades do not eliminate the common causes of Word export failure. When an export fails, I first work out whether the file is truly broken or whether Word is simply blocking it, usually by opening it in LibreOffice; if LibreOffice opens it, I treat the issue as a Word trust, location, filename, or Protected View problem, but if it fails there too, I go back to OmegaT and check the tags. My routine is to clean messy Word source files before translating, keep filenames simple, preserve every tag exactly, avoid the Remove Tags option for Word files, run OmegaT’s tag and issue checks before export, export to a plain local folder, close Word before generating the target file, and always keep the original source file so I can regenerate the document without re-translating anything.
|
»
Proofreading Legal Translation: The Rules, the Limits, and the Brief You Should Write Yourself
|
|
Most arguments about legal proofreading start with the word "proofreading" itself. This article sets out eight rules for revising legal and judicial texts, explains where a linguist's job stops and a lawyer's starts, and makes the case for writing your own specification instead of asking the client for one.
|
No articles found.
|
|
printer version