How do you translate a free-body diagram into words or another language without reversing the forces? Begin with the object whose forces are shown, identify every external force arrow acting on that object, and record each arrow’s direction, label, and stated magnitude before rewriting the explanation. A free-body diagram is not merely a drawing of a moving object. It is a deliberately simplified model of interactions, so the central task is to preserve which body experiences each force.
This practical guide explains how to translate free-body diagrams, force diagrams, Newton’s-law illustrations, and vector labels accurately. It is intended for students, physics teachers, science translators, educational publishers, accessible-content writers, and multilingual learners. Readers searching for “free body diagram translation,” “describe force diagrams in words,” or “translate physics diagrams” usually need a method that keeps direction, magnitude, source, and sign conventions intact.
The reliable approach is to separate reading the physics from choosing the words. Identify the modeled system, interpret its conventions, write a controlled description in the source language, translate technical terms consistently, and verify the result against the original diagram. The objective is not an elegant description that sounds scientific. It is a description from which another reader could reconstruct the same physical relationships.
Why translating a force diagram differs from translating a sentence
Ordinary prose puts most meaning into its words and their grammatical relationships. A free-body diagram distributes meaning across arrows, attachment points, axes, labels, line lengths, symbols, and sometimes a nearby caption. The sentence “a block is pulled upward” cannot tell a reader whether the illustrated upward force is tension, a normal reaction, buoyancy, or a resolved component. Nor does the sentence reveal whether the chosen object is the block, rope, or complete system.
A successful translation therefore begins with an inventory rather than an interpretation of the author’s intention. Notice what is actually depicted, what the surrounding problem states, and what remains unknown. Do not convert a diagram of forces into a prediction about velocity unless the problem’s equations or other information justify it. Physics translation is unusually unforgiving of small grammatical changes: “force exerted by A on B” and “force exerted by B on A” describe opposite members of an interaction pair.
Establish the object boundary before translating any arrow
The first reading question is: what body has been isolated? In a free-body diagram, arrows represent external forces acting on that chosen body, or on the explicitly defined system. The body may be represented as a box, point, circle, or simple outline. Its artistic appearance is secondary. Its identity is central. A description should start “For the cart,” “For the hanging mass,” or “For the two-block system,” rather than jumping straight to “an arrow points right.”
If a diagram labels two adjacent blocks A and B but isolates A in one panel, translating an arrow on A as a force on B changes the problem. When the diagram treats two connected masses as one system, forces internal to that combined system may be omitted even though each individual mass experiences interactions. Explain which convention the picture uses rather than filling omissions by guesswork. OpenStax’s free-body diagram guidance emphasizes identifying the object of interest and including forces acting on it.
Distinguish the real force arrow from nearby motion information
An arrow may represent force, displacement, velocity, acceleration, or a coordinate direction. A textbook page can show several of these beside the same object. Their meanings come from the legend, labels, caption, and diagram type—not from their arrowheads alone. Translating every arrow as “force” can make a correct source image into an incorrect target explanation. Conversely, saying “the object moves to the right” when a force arrow points right mistakes cause for observed motion.
A block could move right while friction points left. A descending lift could be slowing, so its acceleration points upward. A ball thrown upward can be moving upward while its weight acts downward. Preserve this distinction explicitly. A reliable written description says “The velocity arrow is rightward, while the friction-force arrow is leftward,” when both are shown. When the picture contains only forces, avoid inventing motion. Translation must express what the diagram encodes, not what a casual viewer expects.
Read arrow direction relative to a named coordinate frame
“Up,” “down,” “left,” and “right” are convenient only when the drawing’s orientation is clear. Many mechanics figures use horizontal x and vertical y axes, but inclined-plane problems often rotate the axes so one direction runs along the slope. The same physical force can then have one component along the slope and another perpendicular to it. A translator who changes “positive x” into “rightward” without checking the rotated axis may reverse the intended sign.
Describe direction in two layers where necessary: the real-world orientation and the adopted axis. For example: “Weight points vertically downward. Its component parallel to the incline points down the slope, corresponding to the negative x direction in this diagram.” Keep compass, page, and coordinate words distinct. If an arrow is ambiguous because the source image is low resolution, state the uncertainty and request a clearer source. A confident but unfounded direction is worse than an honest unresolved label.
Interpret arrow lengths cautiously
Many textbook diagrams draw longer arrows for larger force magnitudes. Others use merely illustrative lengths and explicitly warn that the diagram is not to scale. Without a scale or caption, an arrow drawn a little longer does not always license “the force is twice as large.” This issue matters when the target language demands comparative adjectives. “Longer arrow” is an observation about the graphic; “greater force” is a claim about the physical model.
If magnitudes such as 12 N and 8 N appear beside arrows, those numbers control the comparison. If only arrow lengths are visible, describe the apparent graphic distinction but qualify its status: “The upward arrow is drawn longer; the image does not state whether lengths are proportional to magnitude.” Maintain units with figures and preserve significant quantities. Do not round a value to sound natural or replace newtons with a culturally familiar non-equivalent. A measured quantity must remain measured.
Keep the force label attached to the correct arrow
The letter N may name a normal force or denote the unit newton when placed after a number. T may denote tension, while W or mg may label weight; another book may use F with subscripts. The translator must interpret position and notation before changing the surrounding words. A subscript such as F_AB can distinguish the force exerted by A on B from the reverse interaction. Removing subscripts for readability can erase the source’s most important distinction.
Create a local legend before writing: source label, physical meaning, force source, object receiving the force, and arrow direction. Keep mathematical symbols unchanged unless a documented target-language convention requires a different notation and the entire document follows it consistently. If the diagram’s caption defines a notation unusually, follow that definition rather than substituting a preferred textbook style. Translate the explanation, not the mathematical identity of its labels.
Weight is vertical even when the surface is tilted
Weight is the gravitational force acting on an object, often represented by mg or W. Near Earth’s surface in routine mechanics problems, its arrow points vertically downward regardless of whether the object rests on a flat table, a ramp, or a moving platform. One common translation error turns “downward” into “down the ramp” because the learner sees an incline. Those are not the same direction.
For an incline, the component of weight parallel to the surface points down the slope, but the full gravitational force remains vertical. If the diagram shows both the full weight vector and its components, distinguish them in every language version. A useful paraphrase is: “The diagram resolves the downward weight into a component along the slope and a component perpendicular to it.” Do not call either component a new separate physical interaction. Components represent one force in a chosen coordinate system.
Normal force means perpendicular contact force
In mechanics, a normal force is the contact force exerted perpendicular to a surface. “Normal” here does not mean ordinary, typical, morally acceptable, or statistically average. Several languages have everyday adjectives that could mislead a literal translation. Choose the established physics term and, where readers are beginners, add a small explanatory phrase: “the surface’s perpendicular contact force.”
On a level surface the normal arrow often points vertically upward, but that is a special case, not its definition. On a tilted plane the arrow is perpendicular to the plane, which is neither vertical nor necessarily aligned with a page margin. In a two-contact problem there may be two different normal forces on one body. Name the surface that exerts each. A translation such as “the ground pushes up” might be pedagogically useful for one picture, yet it must not become the generic definition.
Friction opposes relative motion or its tendency, not every applied force
Friction is frequently translated using vague words like resistance. In a detailed free-body diagram, distinguish static friction, kinetic friction, and any specified model of rolling resistance. Its direction is tied to relative motion, or the tendency to slip, between surfaces. It is not always automatically opposite the object’s velocity relative to the ground, and it is not necessarily leftward because an applied force points rightward.
Consider a person walking forward: the ground’s static friction on the foot can point forward while the foot pushes backward on the ground. For a block being pulled up an incline, kinetic friction points down the slope if the block slides up relative to the surface. If the diagram only says “friction” without specifying its direction or regime, preserve what is shown and avoid deciding the problem for the reader. Record the physical contact pair and any stated assumption.
Tension points along the pulling string or cable
A taut ideal string or cable exerts a tension force along its length, pulling an attached body away from the attachment in the direction of the string. It does not push an attached mass along the string. In translation, a word equivalent to “strain” or “stress” may be inappropriate if it names material deformation rather than the pulling force in a mechanics problem.
Tension labels become especially delicate around pulleys and multiple masses. The force acting on the left body may point up its vertical string segment, while the force acting on a right body points up a different segment. An ideal-pulley assumption might make tension magnitudes equal, but the diagram must still preserve each direction and the body receiving the force. If pulley friction or cable mass is significant, equal tensions may not be justified. Translate the assumptions explicitly rather than silently importing an ideal model.
Applied force, spring force, drag, thrust and buoyancy
Not every arrow in a force diagram has the same everyday-language counterpart. An applied force may be a push or pull supplied by a person or machine. A spring force responds to deformation and typically acts toward equilibrium in a simple Hooke’s-law model. Fluid drag generally opposes an object’s motion relative to the fluid. Thrust is a force produced by propulsion, while buoyancy is the upward force associated with a pressure difference in a fluid.
These definitions have exceptions and modeling details, so the source scenario remains decisive. A parachutist diagram may label upward drag and downward weight; its arrows do not by themselves tell whether the person rises or falls. A submerged object might experience buoyancy, weight, and tension simultaneously. Instead of choosing one broad target word for all arrows, build a glossary that distinguishes interaction mechanism, direction, and source. The goal is a stable conceptual mapping, not colorful synonym variation.
Prevent Newton’s third-law pairs from crossing bodies
Newton’s third law concerns equal and opposite forces that different objects exert on one another. The normal force of the table on a book and the force of the book on the table form an interaction pair, but they belong on the free-body diagrams of different objects. Weight and normal force on a resting book may balance, yet they are not a third-law pair because both act on the book.
This distinction is easy to damage in languages that omit subjects or place agents after verbs. Prefer explicit phrasing at least once: “The table exerts an upward normal force on the book.” Then describe the reaction separately: “The book exerts a downward contact force on the table.” Preserve which object acts and which receives. A bilingual reviewer should be able to point to the corresponding arrow on the appropriate free-body panel for every sentence.
Do not add a separate net-force arrow to the force inventory
The net force is the vector sum of the external forces acting on the isolated body. Some teaching materials show a resultant vector beside or below the original diagram to summarize their effect. That summary arrow is not an additional interaction force to count alongside weight, normal, tension, and friction. If the source distinguishes a force inventory from a resultant, preserve that division. Otherwise a reader may accidentally double-count the net force.
When a figure labels “net force = 0,” it means the vector sum is zero, not that no forces exist. A stationary book on a table has a gravitational force and a normal force even when they balance. Translate “balanced forces,” “equilibrium,” and “zero resultant” carefully. They describe a relation among forces. Do not replace them with “no forces.” The same caution applies to a body moving at constant velocity: zero net force does not mean zero motion.
Resolve vectors without inventing extra physical forces
A diagonal force can be expressed through x and y components. The small component arrows in an instructional diagram are mathematical representations of the same original force. Their labels, signs, and angles are tightly linked. If the source says F_x = F cos θ and F_y = F sin θ, copying those expressions is safer than verbally swapping sine and cosine according to a remembered shortcut. The correct form depends on where the angle is measured.
A translation should identify the reference axis, angle definition, and sign convention before explaining any component. Suppose a 10 N force acts at 30 degrees above positive x. Its horizontal component is positive and its vertical component is positive; the values can be checked against basic trigonometry. If the force points into a different quadrant, signs change. Translators need not solve the full mechanics exercise, but they should use simple reconstruction checks to detect a swapped component or reflected arrow.
Preserve units, decimal separators and mathematical notation
Force magnitudes usually appear in newtons, abbreviated N. A label such as 2.5 N must not become 25 N because a decimal point is lost during localization. Decimal commas in some language communities require deliberate handling. Use consistent notation in the target text and do not alter the number inside a source diagram if the image is not being edited. When the caption and the diagram use different conventions, explain the connection rather than creating apparent contradictions.
Mass is commonly written in kilograms and force in newtons. These are not interchangeable. “A five-kilogram weight” can be ambiguous in casual speech, but technical translation should distinguish a mass of 5 kg from its gravitational weight. If a problem adopts g = 9.8 m/s² or g = 10 N/kg, retain the stated approximation. An error in one symbol can propagate into every subsequent calculation, so numerical checks deserve their own proofreading pass.
Handle negative signs and direction words with precision
A force component marked –4 N along an x axis is not automatically a “negative force” in the colloquial sense. The minus sign identifies direction relative to the chosen positive axis. Translating it as a weakness, reduction, or absence of force changes the idea. The clearer explanation is “a component of magnitude 4 N in the negative x direction,” assuming the diagram’s labels support it.
Signs may also appear in equations for acceleration and displacement elsewhere on the page. Do not harmonize them casually. The coordinate frame might change between panels, or one diagram might use down as positive to simplify a falling-body problem. A disciplined translator records each panel’s axis convention and repeats it when necessary. When readers can trace a sign from an arrow through a sentence to an equation, they can detect errors independently. Clear language is a tool for verification, not decoration.
Example: a book resting on a level table
Imagine a simple drawing of a book on a horizontal table. One arrow labeled W points down from the book, while an arrow labeled N points up. The problem states that the book is at rest and that air resistance is negligible. An accurate translation reads: “The free-body diagram for the book contains two forces: its weight acting downward and the table’s normal force acting upward. The forces balance in this situation.” That preserves the object, directions, physical sources, and equilibrium claim.
A weak description says “the book has an up force and a down force,” because it omits the sources. A wrong description says “the table has an upward force acting on it,” because the arrow acts on the book. Another wrong description would claim that the book has no forces because it is still. Use this simple case as a baseline exercise: if learners cannot distinguish balance from absence, they will struggle with inclined planes and connected systems.
Example: a block pulled across a rough floor
Consider a crate pulled to the right by a rope angled upward. Its free-body diagram shows downward weight, upward normal contact force, diagonal tension along the rope, and leftward kinetic friction if it slides right. The translation should name each force and its source. It should also specify that the tension has a vertical component as well as a horizontal one, which helps explain why the normal force may differ from the weight.
Avoid the shortcut “the pull equals friction” unless the source states constant velocity or another condition leading to that result. Likewise do not say that the crate necessarily accelerates right simply because tension points rightward; the net horizontal force depends on magnitudes. In a multilingual teaching passage, separate the observation of the arrows from the calculation of the resultant. This makes it easier to compare words with the graphic without solving a problem that the teacher intended the student to solve.
Example: an object on an inclined plane
A block on a slope is the classic test of diagram literacy. The correct free-body diagram may show weight vertically downward, normal force perpendicular to the plane, and friction parallel to the plane. Some diagrams add a pulling tension along the slope. An explanatory translation should describe these geometric relationships, because “up,” “left,” and “right” change meaning when the slope is redrawn in another orientation.
A good text alternative might state: “The block is on a plane rising to the right. Weight acts vertically down. The plane exerts a normal force perpendicular to its surface. Friction is shown parallel to the plane, directed down the slope, consistent with the block moving or tending to move upward relative to the plane.” The last clause must be adapted to the stated condition rather than assumed. This case tests whether the translator preserves the object’s relation to the surface, not merely the names of arrows.
Example: an accelerating elevator or lift
An elevator diagram often shows two vertical forces on the car or a passenger: upward tension or normal force and downward weight. If an elevator accelerates upward, the upward force must exceed the downward force in the chosen system. However, an elevator moving upward at constant speed has zero vertical acceleration, while an elevator descending and slowing has upward acceleration. Motion direction and acceleration direction are not interchangeable.
Translate the diagram’s specified state separately from the net-force inference. “The lift is traveling downward but slowing” is different from “the lift accelerates downward.” If the figure contains an upward acceleration arrow, mention it explicitly as acceleration rather than force. If the problem asks readers to determine apparent weight, do not pre-empt the question by adding a numerical answer. The translator’s role is to preserve conditions and relationships so the target-language learner can carry out the intended reasoning.
Example: two bodies connected by a pulley
In a two-mass pulley exercise, the page may contain a picture of the physical setup plus one free-body diagram for each mass. The physical illustration might show a rope looping over a pulley; the free-body drawings isolate each mass and show upward tension and downward weight. The two downward weight arrows need not have equal magnitude. Whether both tension labels denote one common value depends on the stated idealizations.
A robust translation identifies the panel before identifying an arrow: “Panel A shows the forces acting on mass m1; panel B shows the forces acting on mass m2.” It then names each tension and weight. If one mass descends and the other rises, preserve the motion statement without treating its arrows as additional forces. Confusion often comes from copying the left panel’s labels into the right panel. A bilingual side-by-side audit should track m1, m2, arrow direction, and net-force equation independently.
Example: a turning object and the meaning of centripetal
Some diagrams of circular motion show a force arrow toward the center of the path, alongside tangential velocity. “Centripetal force” is often a description of the net inward force required for circular motion, not necessarily a distinct new interaction. For a mass on a string, tension may supply that inward force. For a car turning, friction may supply it. Translating the inward arrow as a newly invented physical source can create double-counting.
A careful description says “The net radial force points toward the center,” or “Tension acts toward the center,” depending on the diagram. Velocity is tangent to the trajectory, not generally toward the center. When the diagram contains labeled components, keep radial and tangential directions distinct. Avoid casually adding an “outward centrifugal force” to an inertial-frame free-body diagram unless the source explicitly analyzes a rotating reference frame. This is a place where explanatory paraphrasing can cause more damage than the original notation.
Translate for novice readers without removing the technical model
A beginner-facing version can define terms briefly at first encounter: weight as gravity’s force, normal as perpendicular contact, tension as string pull, and friction as tangential contact force resisting relative slipping or its tendency. Those definitions should be accurate enough to remain useful in later physics learning. Replacing everything with “pushes and pulls” makes early reading easier but prevents learners from distinguishing interaction types when problems become complex.
Keep the sequence stable across languages: identify the object, name the arrows, state their directions and sources, then explain the relationship or task. For multilingual learners, paired terminology can support transfer when related scientific words exist across languages. Yet a familiar cognate may be false or only partly equivalent. The eduKateSG guide to cross-linguistic vocabulary transfer explains why prior language knowledge can help while still requiring verification.
Build a usable glossary, not a pile of synonyms
A physics glossary should include each term’s meaning, the symbol used locally, a concise example, and an explicit note where everyday usage differs. Include “force,” “mass,” “weight,” “tension,” “normal force,” “static friction,” “kinetic friction,” “resultant force,” “component,” “equilibrium,” and “reference frame.” Many languages distinguish general pressure from contact force, and some use different names for “reaction.” Source and target reviewers should agree on domain terminology before translation begins.
Consistency matters more than stylistic variety. If a target term for normal force appears one way in the caption and another way in the worksheet, the learner may believe two forces are being discussed. Do not change variables in equations to match translated initials: F remains F when the document uses F as a defined symbol. The broader eduKateSG discussion of translation ambiguity in vocabulary helps explain why finding a dictionary equivalent is only the beginning.
Prepare an accessible long description in a logical order
An accessible description of a complex diagram may need more than a brief alternative-text label. Begin with the isolated object and the layout, then list each force in a stable order, such as clockwise or from vertical to horizontal. State any visible axis orientation, values, angles, and named relationship. Preserve the distinction between the drawing and the prose problem. A useful short label could be “Free-body diagram of a crate with weight, normal force, rightward pull, and leftward friction”; the longer text can explain sources and relative directions.
The W3C WAI guidance on complex images explains the role of short identifiers and longer descriptions of essential information. This approach also helps readers without visual disabilities, because the written inventory is easier to search, compare, and translate. Do not create an invented illustration to fill a missing image. If the original source is unavailable, label the text as a general example rather than a description of a nonexistent diagram.
Use controlled language before machine translation
Technical content becomes easier to localize after its source sentences are clarified. Replace “it acts up there” with “the normal force acts perpendicular to the ramp, away from the surface.” Replace “F is opposite to it” with the two named forces and the axis. Resolve pronouns, preserve notation, and avoid describing a rotated diagram with an unqualified spatial phrase. This is controlled source writing: not simplified physics, but simpler language about the same physics.
Feed the verified text description and a term glossary into a translation workflow. Compare the target text against each labeled arrow rather than simply trusting fluent-looking output. A language model may make plausible inferences about a familiar textbook scenario, but it cannot always discern small subscripts, crowded arrowheads, or whether a dashed line is an auxiliary construction. Human review of the source graphic remains necessary, especially in exams, safety material, and published textbooks.
Review technical equations separately from prose
Translation proofreading often focuses on grammar, yet the greatest physics errors can live in small mathematical marks. Compare every coefficient, exponent, Greek letter, subscript, angle sign, unit, and equality symbol between source and target. If the source uses sum F_x = ma_x, the translated paragraph must preserve what x denotes, not change it into a generic statement that all forces equal mass times speed.
Set up two independent passes. First, a bilingual editor checks terminology, referents, and comprehensibility. Second, a subject-aware reviewer reconstructs force arrows from the target description and verifies equations. This review is more reliable than asking one person whether the result “reads naturally.” An apparently elegant target paragraph can omit a force, imply a wrong direction, or erase a qualifying assumption. A valid translation must survive reconstruction, not merely sound fluent.
A practical seven-stage translation workflow
Start by capturing the complete source: the graphic, title, caption, legend, problem statement, and any equation immediately beside it. Next identify the object or system boundary. Third, make an arrow inventory that records label, orientation, type, source, magnitude, units, and uncertainty. Fourth, write a concise source-language description without explaining beyond the evidence. Fifth, translate with a fixed terminology sheet and consistent variable names. Sixth, test the target version by sketching the forces from its words. Finally, compare the reconstructed sketch with the source and record unresolved issues.
This workflow should be repeated for each panel of a multi-panel illustration. Small shortcuts create the largest errors at the boundaries: an arrow copied to the wrong mass, a body misidentified, or a component mistaken for an external force. Where the caption contradicts the picture, flag the discrepancy rather than silently repairing it. Editorial honesty preserves the information needed for a responsible correction by the original author.
Quality assurance: questions that reveal hidden mistranslations
Ask whether a reader can identify the isolated body without seeing the figure. Ask whether every named force has a physical source and an object it acts upon. Confirm whether coordinate directions are described in the same frame as the source. Examine every phrase containing “opposite,” “equal,” “larger,” “up,” “down,” “left,” or “right”; these words are common locations for silent reversal. Check whether any conclusion about acceleration has been inferred from velocity or from one arrow alone.
Then test numbers and notation. Does each magnitude retain its unit? Are source subscripts and Greek letters intact? Are dashed construction lines treated as components rather than additional forces? Is the net force separated from the force inventory? Would two competent readers produce the same sketch from the translated description? This reconstruction test is decisive: if two materially different sketches are possible, the language may still be too vague.
Common errors and how to correct them
One mistake translates the normal reaction as “the usual force”; correct it with perpendicular contact force. Another calls the gravitational component down the incline “weight”; distinguish the vertical weight from its components. A third treats velocity direction as force direction; identify the vector type. A fourth presents every visible arrow as a separate external interaction; classify components and net-force indicators. A fifth interchanges the agent and receiver in a third-law pair; write “A on B” explicitly.
A sixth failure assumes an arrow’s length is quantitatively scaled when no scale is given. A seventh removes subscripts or minus signs. An eighth normalizes a decimal separator incorrectly. A ninth replaces an unresolved abbreviation with a confident guess. A tenth writes an elegant paragraph without identifying the chosen object. These errors look minor in typography but change the mechanics. Building an error log from actual diagrams is more useful than memorizing generic advice to be careful.
Practice activity: make one diagram reversible
Choose a clear mechanics figure from an openly accessible educational source. Without solving the problem, write a source-language description that includes the isolated body, every external force, directions, labels, magnitudes, axis conventions, and any stated idealizations. Give the text to a colleague who cannot see the image and ask them to draw the free-body diagram. Compare drawings and mark every mismatch. Then translate the improved description into the target language and repeat the reconstruction.
For a more advanced activity, choose a figure with two panels and different body boundaries. Ask a second reviewer to identify all third-law pairs across panels and to distinguish them from balanced forces on one body. Keep a terminology sheet and record ambiguities with screenshots or line references rather than guesses. Such exercises make translation a demonstrable skill: success is measured by preservation of structure, not just similarity of wording.
How this topic connects with other visual translation tasks
A free-body diagram belongs to a wider family of technical images whose arrows and labels encode relationships. Compare electrical circuit diagrams, where lines represent electrical connections rather than applied forces; optical ray diagrams, where arrows track light paths; and statistical graphs, where axes represent measured variables. These distinctions prevent a translator from applying one diagram’s conventions indiscriminately to another.
Language learners can also consult How English Works: Translation and Meaning Across Languages and Why Translation Helps Language Learners. The important transferable habit is the same: understand what the source actually means, account for context and specialized vocabulary, and verify that the target expression preserves it.
Frequently asked questions about translating free-body diagrams
Can an automatic translator understand the whole force diagram?
It may extract visible labels and produce useful preliminary descriptions, but small subscripts, rotated axes, arrowheads, and distinctions between force and motion remain failure points. Treat generated text as a draft that needs comparison with the actual figure. A fluent answer without explicit verification should not be presented as a checked scientific interpretation. If a key arrow or unit is unreadable, mark it as unresolved rather than guessing.
Should I translate the letters and equations too?
Translate explanations and terminology where appropriate, but normally retain defined symbols, mathematical relationships, subscripts, and values. A target-language glossary can explain their meaning. If local educational convention differs, document the convention and update all associated labels consistently with subject review. A symbol should never change merely because its English name begins with a different letter from its target-language name.
How long should the written description be?
Long enough to preserve the problem’s essential physical information, short enough to be navigable. A simple book-on-table diagram may need a few sentences. A pulley system with multiple bodies, force components, and sign conventions may require several ordered paragraphs. The correct length follows information density, not a fixed word target. An accessible long description should allow another reader to reconstruct the forces without extraneous speculation.
What if the source diagram itself seems wrong?
Record the discrepancy specifically: name the arrow, axis, equation, and conflicting caption. Do not silently replace the source picture with an imagined corrected version. An editor or subject expert should decide whether the publication needs an erratum. For student work, explain that a possible conflict requires clarification and, where applicable, follow the textbook or instructor’s stated convention until resolved.
Final principle: preserve interactions before polishing sentences
A free-body diagram is a compact explanation of which forces act on which object, in what directions, under what assumptions. Translating it easily means understanding that structure before attempting fluent target-language prose. The reliable test is whether the translated account preserves every body boundary, force source, label, axis, component, magnitude and stated uncertainty. If it does, readers can learn the physics in their own language without inheriting a changed problem.