{"id":1644,"date":"2016-05-26T21:51:00","date_gmt":"2016-05-26T21:51:00","guid":{"rendered":""},"modified":"2017-03-13T18:36:52","modified_gmt":"2017-03-13T18:36:52","slug":"the-beginning-of-wisdom-some-practical-aspects-of-technical-translation","status":"publish","type":"post","link":"https:\/\/ata-divisions.org\/S_TD\/2016\/05\/26\/the-beginning-of-wisdom-some-practical-aspects-of-technical-translation\/","title":{"rendered":"The Beginning of Wisdom: Some practical aspects of technical translation"},"content":{"rendered":"
Nicholas Hartmann<\/o:p><\/span><\/i><\/div>\n
Introduction<\/o:p><\/span><\/b><\/div>\n
It has been said that no one but the author reads a document as carefully as the translator does. What if that same detailed consideration were applied to a piece of business correspondence that a freelance translator might receive and read every day, for example an e-mail message from a regular customer? That analysis is taken here as an opportunity to discuss some of the attitudes and habits that technical translators should cultivate.<\/o:p><\/span><\/div>\n
The message<\/o:p><\/span><\/b><\/div>\n
The names in the \u201cmessage\u201d below are fictitious, but its content and tone are typical. \u201cStanislaus Tweek\u201d is a composite of several of my regular patent-attorney customers, and \u201cHuber & Meyer\u201d stands for a German patent law firm that represents German companies and inventors, and must work through a U.S. attorney in order to apply for a U.S. patent. \u201cPrior art\u201d is that which is already \u201cknown\u201d in the strictly patent-related sense, i.e. the universe of existing knowledge to which a patentable invention must constitute a novel addition. \u201cDeclaration\u201d refers to a translator\u2019s formal statement of accuracy, discussed in more detail below.<\/o:p><\/span><\/div>\n
Dear Nick:<\/o:p><\/span><\/div>\n
Confirming our conversation of earlier today, please find attached the German text of another Jos. Schmidt GmbH electronic motor control system patent from Huber & Meyer in Munich. Please prepare an English translation of this text and e-mail it to Herr Meyer for review no later than June 21. My thanks again for accommodating the short deadline.<\/o:p><\/span><\/div>\n
I have enclosed two prior-art documents that are referenced in the specification, for whatever terminological assistance they may provide. Please note that we will require a Translator\u2019s Declaration for this application.<\/o:p><\/span><\/div>\n
Best regards,<\/o:p><\/span><\/div>\n
Stan<\/o:p><\/span><\/div>\n
Stanislaus Tweek<\/o:p><\/span><\/div>\n
Tincker, Fiddel & Tweek, LLP<\/o:p><\/span><\/div>\n
Intellectual Property Law<\/o:p><\/span><\/div>\n
Relationships<\/o:p><\/span><\/b><\/div>\n
Dear Nick: … Best regards, Stan<\/o:p><\/span><\/div>\n
The forms of address in Mr. Tweek\u2019s message are significant. He and I are on a first-name basis after working together for several years; we have met and we exchange Christmas cards. The relationship is cordial, even friendly, but still businesslike.<\/o:p><\/span><\/div>\n
We can be friendly because we know what to expect from one another:<\/o:p><\/span><\/div>\n
Although he can have someone else translate his patents more cheaply \u2013 and has done so when I have been unavailable \u2013 he still calls me first because he knows that I will give him a translation of the highest possible quality; deliver it on time; and be adaptable and flexible in terms of deadline, subject matter, consultation and review, and preferred style and terminology.<\/o:p><\/span><\/div>\n
I in turn know that he will allow me the longest possible deadline consistent with his own time constraints; provide whatever terminology support he can; shield me from the complexities of the patent system and the whims of German attorneys; and pay my invoices promptly.<\/o:p><\/span><\/div>\n
These mutual understandings are the foundation of how I define a \u201cgood customer.\u201d This particular relationship goes further, however:<\/o:p><\/span><\/div>\n
More relationships<\/o:p><\/span><\/b><\/div>\n
e-mail it to Herr Meyer for review<\/o:p><\/span><\/div>\n
Herr Meyer is the attorney at Huber & Meyer who actually writes the German applications that I translate. I am asked to send my translations to him so that he can make sure I am using the client\u2019s preferred terminology and suggest other minor procedural adjustments. He and I have learned to adapt to one another\u2019s idiosyncrasies and preferences, and to Mr. Tweek\u2019s as well.<\/o:p><\/span><\/div>\n
A few years ago, after disagreeing vigorously with some of Herr Meyer\u2019s proposed changes that, in my opinion, went well beyond what the original German text actually said, I contacted Mr. Tweek and asked him to clarify the responsibilities, roles and obligations of the three parties involved. His response was, in part (emphasis mine):<\/o:p><\/span><\/div>\n
You and I and Herr Meyer are all working for the ultimate client, Schmidt GmbH<\/u>, and our primary responsibility is to exercise our professional judgment in such a way that Schmidt GmbH obtains US patents which will stand up in court.<\/o:p><\/span><\/i><\/div>\n
You clearly cannot certify, as an accurate translation, wording which you believe introduces forbidden \u201cnew matter.\u201d If an infringer did manage to invalidate a Schmidt patent on the basis of an inaccurate translation of the text, this could destroy protection of one or more products from competition. People could lose jobs<\/u>.<\/o:p><\/span><\/i><\/div>\n
We must therefore continue to exercise our respective professional judgments while maintaining a cooperative spirit, since we are all on the \u201cSchmidt team\u201d together<\/u>.<\/o:p><\/span><\/i><\/div>\n
Because I communicate directly both with Herr Meyer (who originates the texts and who in turn is acting on behalf of Schmidt GmbH, which is ultimately affected by the quality of my work) and with Mr. Tweek (whose reason for wanting the best possible translation is to maximize his success in obtaining US patents for Schmidt GmbH so he can retain them as a client), I am no longer simply a \u201cservice provider\u201d but one of the participants in a cooperative endeavor. Each participant derives the same advantage from working together as effectively as possible: we retain our respective customers, earn their respect, and enhance our professional reputations.<\/o:p><\/span><\/div>\n
I therefore function as part of an explicitly defined \u201cteam,\u201d each member of which makes a specific contribution that is acknowledged and respected by the others. This requires that each team member not only possess the appropriate expertise, but also have the confidence to assert it. That in turn requires experience: my triangular relationship with Messrs. Tweek and Meyer is not one in which I could have functioned successfully at the very beginning of my translation career.<\/o:p><\/span><\/div>\n
Translation<\/o:p><\/span><\/b><\/div>\n
Please prepare an English translation of this text<\/o:p><\/span><\/div>\n
The American Translators Association\u2019s Code of Business Practices refers to a translator as a \u201cbridge for ideas from one language to another and one culture to another…\u201d A real bridge, however, is inorganic and immobile, a static, non-living structure. Translators are none of the above: we are alive and active. What we really do, as the Latin root of \u201ctranslate\u201d implies, is to act as carriers across<\/u> bridges.<\/o:p><\/span><\/div>\n
But what do we carry? Translators might seem to carry written words, as interpreters carry spoken words, but our ultimate purpose is always to convey what the words themselves are carrying: ideas, concepts, meanings, and thoughts.<\/o:p><\/span><\/div>\n
Words and language, after all, are just containers: they are conventions and agreements among groups of people that certain noises (spoken language) and squiggles (written language) have certain meanings.<\/o:p><\/span><\/div>\n
The translator must look at one set of squiggles, understand what they mean, and express that meaning as another set of squiggles. It might appear that the squiggles are the end product of translation (since words are often the unit by which we get paid). But the real product, the reason for making all the squiggles, is what they mean; and the quality of a translation is determined by how well the translator turns source symbols into meaning (= comprehension) and back into target symbols (= expression). The symbols are merely vehicles for moving meaning from the author\u2019s mind through the translator\u2019s to the reader\u2019s.<\/o:p><\/span><\/div>\n
Consider the Chinese ideogram <\/span>\u6c34<\/span>. If you cannot read Chinese, it is indeed merely a squiggle. Even a transcription into the Roman alphabet (\u201cshui\u201d) of that ideogram\u2019s pronunciation in Mandarin Chinese is meaningless without a knowledge of the spoken language.<\/o:p><\/span><\/div>\n
With appropriate dictionaries we can accurately translate <\/span>\u6c34<\/span> <\/span>into English as \u201cwater\u201d; and it might seem that our work is then finished. And so we are, if our work is performed only on the level of noises and squiggles. But water\u2019s real existence goes far beyond the spoken and written conventions of different human languages; if we really want to understand water, we need to walk along a beach, turn on a faucet, or step in a puddle.<\/o:p><\/span><\/div>\n
A true understanding of anything<\/u> can therefore be gained only by direct experience of it \u2013 the sound and feel of water, how one gear meshes with another, the size of the Grand Canyon. True understanding then leads to correct internalization of the meaning of a source-language text, which can then can be expressed accurately in the target language.<\/o:p><\/span><\/div>\n
This is why technical translators love factory tours: they are an opportunity to see real things and real processes that we would otherwise never directly experience.<\/o:p><\/span><\/div>\n
Time management<\/o:p><\/span><\/b><\/div>\n
My thanks again for accommodating the short deadline.<\/o:p><\/span><\/div>\n
The older I get, the more keenly I realize that accurate, high-quality translation of complex technical material is an intellectually and physically demanding activity.<\/o:p><\/span><\/div>\n
I have found that in the long run, it is better to turn down work and devote appropriate attention to what I have, than to produce less than the best possible quality just in order to generate more volume. The alternative is a vicious circle:<\/o:p><\/span><\/div>\n
Too much work = fatigue = inattention = mistakes = poor quality = loss of reputation, customer confidence and repeat business = … not enough work.<\/o:p><\/span><\/div>\n
Time management therefore means not only meeting deadlines, but also understanding one\u2019s limitations and capabilities and how they affect quality.<\/o:p><\/span><\/div>\n
Responsibility<\/o:p><\/span><\/b><\/div>\n
we will require a Translator\u2019s Declaration<\/o:p><\/span><\/div>\n
Here is the gist of the Translator\u2019s Declaration (also called a Verification) that I use. My thanks go to Jan Clayberg and Olaf Bexhoeft for providing me, fifteen years ago, with a copy of their battle-tested Declaration that I have used successfully ever since:<\/o:p><\/span><\/div>\n
I, Nicholas Hartmann, translator … declare that I am well acquainted with the English and German languages and that the appended document is a true and faithful translation of:<\/o:p><\/span><\/i><\/div>\n
[document reference]<\/o:p><\/span><\/div>\n
All statements made herein are to my own knowledge true, and all statements made on information and belief are believed to be true; and further, these statements are made with the knowledge that willful false statements and the like so made are punishable by fine or imprisonment, or both, under Section 1001 of Title 18 of the United States Code, and that such willful false statements may jeopardize the validity of the document.<\/o:p><\/span><\/i><\/div>\n
The Translator\u2019s Declaration is a formal statement that I have the knowledge and qualifications to do the job I have taken on, and that I take responsibility for what I have done. It is where the translator literally signs on the dotted line to verify accuracy.<\/o:p><\/span><\/div>\n
There are implied penalties for negligence and incompetence: for example, \u201cwillful false statements may jeopardize the validity of the document,\u201d thereby possibly invalidating the patent and once again causing people to lose their jobs.<\/o:p><\/span><\/div>\n
But the Declaration\u2019s choice of words is interesting: \u201cwell acquainted with\u201d (not<\/u> \u201can omniscient and unchallengeable expert in\u201d); \u201cto my own knowledge true<\/u>\u201d; \u201cstatements made on information and belief are believed<\/u>to be true.\u201d<\/o:p><\/span><\/div>\n
The Declaration does not impose a requirement for perfection. It does, however, put into legal language the obligations that every translator should already feel: to acquire and maintain knowledge of both the languages and the subject matter of every translation; to apply that knowledge with unfailing care; and to do everything necessary to ensure accuracy. In other words, to act like a professional.<\/o:p><\/span><\/div>\n
Subject knowledge<\/o:p><\/span><\/b><\/div>\n
another Jos. Schmidt GmbH electronic motor control system patent<\/o:p><\/span><\/div>\n
It is curious that in the Translator\u2019s Declaration, I am not required to affirm that I know anything about the subject matter of my translation. While such knowledge is obviously mandatory, the manner in which technical translators acquire it seems to be very heterogeneous.<\/o:p><\/span><\/div>\n
In my own case, for example, my three degrees in an obscure corner of the humanities might seem poor preparation for the translation of German electronics patents. But higher education does teach some useful habits of mind: research skills, intellectual rigor, the existence and function of specialized language, the fundamental importance of experimentation and the scientific method, and how to write clearly. I was also fortunate to have inherited from my father \u2013 a photojournalist and industrial photographer \u2013 his fascination with technology as an expression of human creativity, and to have accompanied him as he photographed production plants, laboratories, aircraft hangars, architectural monuments, machine parts, and much more.<\/o:p><\/span><\/div>\n
Other technical translators have come to their careers through very different but similarly indirect routes, but I believe that the details of training and background are merely secondary. What all successful and contented technical translators share is not a particular course of study but certain fundamental personality traits: we are insatiably curious about the real world, both natural and man-made; our curiosity is wide-ranging, even all-encompassing; and we firmly believe there is no such thing as useless information.<\/o:p><\/span><\/div>\n
The appeal and excitement of a life in technical translation are that it requires (and rewards) an omnivorous approach to knowledge: you drive hundreds of miles out of your way to look at a bridge, or take the long way round to whatever you need at the hardware store, or read owner\u2019s manuals for things you don\u2019t even own. What makes you a good technical translator is therefore not what you get taught while you\u2019re in school, but how much you want to keep learning for the rest of your life.<\/o:p><\/span><\/div>\n
Terminology, finally<\/o:p><\/span><\/b><\/div>\n
for whatever terminological assistance they may provide<\/o:p><\/span><\/div>\n
The title of this essay is taken from the Chinese saying<\/o:p><\/span><\/div>\n
\u201cThe beginning of wisdom is to call a thing by its right name,\u201d<\/o:p><\/span><\/i><\/div>\n
and terminology is obviously an important aspect of technical translation. But how do we decide what the \u201cright name\u201d is?<\/o:p><\/span><\/div>\n
Very often, it depends on what a lot of other right names are: in a particular industry or trade, within a particular document or set of documents, or even as preferred by a particular engineer or patent attorney.<\/o:p><\/span><\/div>\n
For example, a recent project required me to translate three French patents relating to a firearm mechanism: all three dealt with much the same subject matter, and had to be consistent with one another and with a previous (mediocre) translation that had already been submitted to the Patent Office.<\/o:p><\/span><\/div>\n
Those involved were the translator (me), another translator functioning as editor and as representative of the translation partnership that was my direct customer, the patent attorney who was their customer, and the engineers at the company applying for the patent. Because of the large number of interested parties and the need to conform to previously defined terminology, this one set of documents ended up tying all of us into some truly Gordian terminological knots.<\/o:p><\/span><\/div>\n
Let\u2019s start with the apparently simple concept of locking or immobilizing a movable part (French terms are in <\/span>italics<\/span><\/i>, English terms in <\/span>boldface<\/span><\/b>):<\/o:p><\/span><\/div>\n
We begin with <\/span>immobiliser<\/span><\/i>, which we effortlessly translate as <\/span>immobilize<\/span><\/b>. <\/span>Based on <\/span>desserrer<\/span><\/i> <\/span>= <\/span>unlock<\/span><\/b>, <\/span>we then rashly assume that <\/span>serrer<\/span><\/i> <\/span>= <\/span>lock<\/span><\/b>. Wrong: <\/span>bloquer<\/span><\/i> <\/span>= <\/span>lock<\/span><\/b>, because following exhaustive discussions between the attorney and the engineers, we were told that \u201cnone of the other options \u2013 jam, inhibit, block, trap, park, secure, freeze \u2013 seems to capture the idea here as well as \u2018lock\u2019.\u201d So <\/span>serrer<\/span><\/i> <\/span>= <\/span>interlock<\/span><\/b>.<\/o:p><\/span><\/div>\n
On to <\/span>verrouiller<\/span><\/i>. <\/span>Bolt<\/span><\/b> <\/span>seems obvious but that English word has a specific meaning in firearms; a better general term would be <\/span>lock<\/span><\/b>, but <\/span>bloquer<\/span><\/i> <\/span>already occupies that terminological space. So we select <\/span>clamp<\/span><\/b>. A <\/span>dispositif de verrouillage<\/span><\/i> <\/span>is then a <\/span>clamping device<\/span><\/b>; a <\/span>douille de verrouillage<\/span><\/i> <\/span>should therefore be a <\/span>clamping sleeve<\/span><\/b>, but turns out in fact to be just a <\/span>sleeve<\/span><\/b>, because the same reference number is used in one of the documents for a plain old <\/span>douille<\/span><\/i>, whereas a lexically identical <\/span>douille<\/span><\/i> <\/span>with a different<\/u>reference number is actually a <\/span>cartridge case<\/span><\/b>.<\/o:p><\/span><\/div>\n
The same problem occurs with <\/span>axe du canon<\/span><\/i>, which is the <\/span>barrel axis<\/span><\/b>, suggesting that every instance of <\/span>axe<\/span><\/i> <\/span>is therefore an <\/span>axis<\/span><\/b>. Unfortunately some of them are physical elements rather than geometrical constructs and are therefore <\/span>pins<\/span><\/b>.<\/o:p><\/span><\/div>\n
All these components move within something called a <\/span>b\u00e2ti<\/span><\/i>, which the dictionary defines as a frame; but <\/span>carcasse<\/span><\/i> <\/span>is already defined as \u201c<\/span>frame<\/span><\/b> <\/span>= the basic unit of a firearm that houses the firing and breech mechanisms and to which the barrel and stock are attached, aka receiver, although Client (12\/20\/04) says that frame is a superordinate term to receiver,\u201d a road down which we will not travel.<\/o:p><\/span><\/div>\n
Let\u2019s move on to <\/span>bo\u00eetier<\/span><\/i>, which cannot be a frame and which we define as a <\/span>housing<\/span><\/b>. A <\/span>bo\u00eetier de culasse<\/span><\/i> <\/span>is (thank God) a <\/span>breech housing<\/span><\/b>, so is <\/span>culasse<\/span><\/i> <\/span>then <\/span>breech<\/span>? Sorry, it\u2019s a <\/span>bolt<\/span><\/b> <\/span>(remember <\/span>verrouiller<\/span><\/i>?), which according to the client is the same as a <\/span>breech block<\/span><\/b>, being \u201cthe part that closes on the end of the barrel opposite where the bullet exits.\u201d<\/o:p><\/span><\/div>\n
Our joy at finding that <\/span>t\u00eate de culasse<\/span><\/i> <\/span>is in fact <\/span>bolt head<\/span><\/b> <\/span>is tempered by the discovery that <\/span>culasse mobile<\/span><\/i> <\/span>is a <\/span>mobile breech<\/span><\/b>, because \u201caccording to the client the bolt is the same as breech block, except that for <\/span>culasse mobile<\/span><\/i> <\/span>Termium gives breech bolt or even breech block or, when no rotary motion is performed, closure is usually referred to as a breechblock,\u201d another road down which we will not go.<\/o:p><\/span><\/div>\n
All this is fired by a <\/span>m\u00e9canisme de d\u00e9tente<\/span><\/i>, which we render as <\/span>trigger mechanism<\/span><\/b>. The result is that for <\/span>d\u00e9clenchement<\/span><\/i> <\/span>we then cannot use the obvious <\/span>triggering<\/span><\/b>, and must instead use <\/span>release<\/span><\/b>. Although <\/span>d\u00e9clenchement et\/ou arr\u00eat<\/span><\/i> <\/span>is translated in the prior US filing (the paradigm to which we must conform) as <\/span>triggering or blocking<\/span><\/b>, by special dispensation we are allowed to call it <\/span>release and\/or stoppage<\/span><\/b>. \u201cStoppage\u201d sounds funny, but as soon as we consider \u201clocking\u201d or \u201cblocking\u201d as an alternative we are hit on the back of the head by three boomerangs labeled <\/span>serrer<\/span><\/i>, <\/span>deserrer<\/span><\/i>, and <\/span>bloquer<\/span><\/i>…<\/o:p><\/span><\/div>\n
This went on for almost two months, through dozens of monolingual, multilingual, and pictorial dictionaries, downloaded PDF files containing parts lists for Finnish sporting rifles, e-mails, 40-minute telephone calls, a constantly expanding and mutating glossary, consultations with engineers, and so on. It came within eight hours of being a multi-year project.<\/o:p><\/span><\/div>\n
The \u201cright name\u201d is therefore whatever is right in a particular applicable context. The next time I encounter any of these terms in French I may not be able to use the same English equivalents even if they do refer to firearms, because a different document may be affected by different antecedents, contexts, and preferences.<\/o:p><\/span><\/div>\n
Summary and conclusions<\/o:p><\/span><\/b><\/div>\n
What is therefore the real meaning that a technical translator should extract from a message like the one we have been discussing? What are the real instructions being given? What must the recipient understand<\/u> in order to act on it appropriately?<\/o:p><\/span><\/div>\n
I believe there are six fundamental things that all translators, especially those dealing with technical material, must understand:<\/o:p><\/span><\/div>\n
a.                   <\/span><\/span>The nature of translation and the translator: that spoken and written languages are merely symbols and sets of assumptions referring only indirectly to real things, and that the real things are what is important and must be comprehended.<\/o:p><\/span><\/div>\n
b.                   <\/span><\/span>The translator\u2019s interaction with clients, editors, and ultimate customers: a translator, no matter where he or she is physically located, cannot ever work successfully in isolation.<\/o:p><\/span><\/div>\n
c.                   <\/span><\/span>Time management: knowing how much can be accomplished while maintaining high quality, which is the foundation of a long-term approach to a professional career.<\/o:p><\/span><\/div>\n
d.                   <\/span><\/span>How to acquire and refine subject expertise within one\u2019s own psychological and emotional context: if you don\u2019t know DNA from RNA but circuit diagrams are your favorite bedtime reading, then say No to the biomedical jobs and expand your knowledge of electrical engineering. Whatever you do, you must love it; otherwise translation is just a job, and there are easier jobs.<\/o:p><\/span><\/div>\n
e.                   <\/span><\/span>Our responsibilities to:<\/o:p><\/span><\/div>\n
–        <\/span><\/span>our customers, not only because they pay us but because we have accepted obligations with regard to delivery deadlines, accuracy, appropriateness, and quality;<\/o:p><\/span><\/div>\n
–        <\/span><\/span>our colleagues: we have a professional and moral obligation to help other translators learn and advance, to take pride in what we do, and to let the rest of the world know about it;<\/o:p><\/span><\/div>\n
–        <\/span><\/span>the public: the work we do affects our customers, and their customers, and eventually those customers\u2019 employees and stockholders. Translators must be aware of being participants in society and in the national and world economy;<\/o:p><\/span><\/div>\n
f.                    <\/span><\/span>How to collect, manage, and evaluate terminology: the words we use must be appropriate and up-to-date and must reflect, whenever possible, direct contact with what lies behind the terminology. Once you have stood inside a waste incineration plant and experienced its smell and heat, or spun a roller bearing, or looked carefully at a suspension bridge, you can bring true understanding to your translations of texts on those subjects.<\/o:p><\/span><\/div>\n
So perhaps \u201cthe beginning of wisdom is to call a thing by its right name,\u201d but it is only the beginning.<\/o:p><\/span><\/div>\n
#   #   #<\/o:p><\/span><\/div>\n
Nicholas Hartmann has worked as an independent technical and scientific translator since 1984, serving customers in the United States and Europe. For more information, please visit <\/span><\/i>www.nhartmann.com<\/span><\/i>.<\/o:p><\/span><\/i><\/div>\n

<\/p>\n

This essay was published, with very minor editorial emendations, in the April 2006 issue of the <\/span><\/i>ATA Chronicle<\/span>, the bimonthly magazine of the American Translators Association.<\/span><\/o:p><\/i><\/div>\n","protected":false},"excerpt":{"rendered":"

Nicholas Hartmann Introduction It has been said that no one but the author reads a document as carefully as the translator does. What if that same detailed consideration were applied to a piece of business correspondence that a freelance translator might receive and read every day, for example an e-mail message from a regular customer? That analysis is taken here as an opportunity to discuss some of the attitudes and habits that technical translators should cultivate. The message The names in the \u201cmessage\u201d below are fictitious, but its content and tone are typical. \u201cStanislaus Tweek\u201d is a composite of several…<\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","ngg_post_thumbnail":0,"footnotes":""},"categories":[1],"tags":[57,55,61,58,59,56,60,255],"class_list":["post-1644","post","type-post","status-publish","format-standard","hentry","category-blog","tag-nicholas-hartmann","tag-relationships","tag-responsibility","tag-subject-knowledge","tag-technical-translation","tag-terminology","tag-time-management","tag-uncategorized"],"_links":{"self":[{"href":"https:\/\/ata-divisions.org\/S_TD\/wp-json\/wp\/v2\/posts\/1644","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ata-divisions.org\/S_TD\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ata-divisions.org\/S_TD\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ata-divisions.org\/S_TD\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/ata-divisions.org\/S_TD\/wp-json\/wp\/v2\/comments?post=1644"}],"version-history":[{"count":1,"href":"https:\/\/ata-divisions.org\/S_TD\/wp-json\/wp\/v2\/posts\/1644\/revisions"}],"predecessor-version":[{"id":1791,"href":"https:\/\/ata-divisions.org\/S_TD\/wp-json\/wp\/v2\/posts\/1644\/revisions\/1791"}],"wp:attachment":[{"href":"https:\/\/ata-divisions.org\/S_TD\/wp-json\/wp\/v2\/media?parent=1644"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ata-divisions.org\/S_TD\/wp-json\/wp\/v2\/categories?post=1644"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ata-divisions.org\/S_TD\/wp-json\/wp\/v2\/tags?post=1644"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}