How do you translate wayfinding signs, public-transport information and passenger directions correctly when the reader may have only a few seconds to decide where to go? The safest method is to translate the journey, not merely the words. Identify the traveller’s current state, the decision they must make next, the destination or service they are trying to reach, the symbol or colour system that supports the text, and the physical place where the message appears. In multilingual wayfinding, a translation is successful when a person can move through the same space with the same confidence, timing and safety as a reader of the source language.
People searching for wayfinding translation, multilingual signage, public transport translation, airport signage translation, train station signs, passenger information translation, transport localization and multilingual wayfinding systems are dealing with a special form of translation: very short language embedded inside architecture, maps, pictograms, platform numbers, colour codes, digital displays and real-time operating information. The text may be only two words long, but the operational context around those two words can be enormous.
This guide develops a repeatable method for translating public signs, route information, station messages, airport directions, interchange notices, accessibility information and other wayfinding content. It covers first principles, sign hierarchy, destination naming, arrows, icons, line names, platform information, dynamic messages, emergency changes, accessibility, transliteration, abbreviations, character limits, maps, testing and release. The goal is not to produce elegant isolated phrases. The goal is to keep people oriented.
The visible problem: a short sign can control a long journey
Wayfinding language is unusually compressed. A paragraph gives a translator room to explain. A sign may offer one noun, one arrow and one colour. Yet that tiny unit can decide whether a passenger catches a train, enters the correct security queue, changes platforms in time, reaches an accessible lift, exits at the right street, or follows an evacuation route.
This creates a paradox. The fewer words a source contains, the more context the translator may need. “Connections” can mean connecting flights, onward trains, interchanges, transfers between terminals or network links. “Exit” may refer to a station exit, emergency exit, terminal exit or road exit. “Gate closes” and “boarding closes” may have different operational meanings. The translator cannot safely work from the phrase alone.
The first rule is therefore simple: locate the sign inside the journey before choosing the target wording.
First principle: wayfinding is a decision system
A good wayfinding system helps a person answer recurring questions: Where am I? Where is my destination? Which direction should I take? What should I do at the next decision point? How will I know I have arrived? Translation must preserve those answers.
Think of a station as a chain of decisions. Enter station. Find line. Choose direction. Locate platform. Board train. Transfer if required. Find exit. Reach street destination. Every sign belongs somewhere in that sequence. A target phrase should be judged by whether it supports the intended decision, not whether it resembles the source wording.
This is why physical context matters more in wayfinding than in ordinary prose. The same source word may need different target forms depending on whether it labels a place, commands an action, identifies a service or confirms arrival.
Step 1: map the passenger journey before translating labels
For a small project, sketch the journey in plain language. For a large airport, railway or hospital, use a formal journey map. Identify entrances, ticketing points, security or access gates, decision nodes, vertical circulation, transfer zones, waiting areas, platforms, gates, exits and destination confirmations.
Attach each source sign to one node. A translator should know whether “Transfer” appears above a corridor, beside a ticket machine, on a platform screen or inside a route planner. This prevents a generic target term from being used everywhere when the real function changes.
Journey mapping also exposes missing context early. If a sign reads “Northbound,” the translator must know whether the network officially uses compass direction, terminal destination, line direction or another convention in the target-language system.
Step 2: identify the sign function
Not every sign does the same job. A useful working taxonomy is: identification, direction, confirmation, regulation, warning, information and service status.
An identification sign names a place: “Platform 3,” “Arrivals,” “Taxi Stand.” A directional sign tells the reader where to move: “Gates 20–35 →.” A confirmation sign reassures the traveller that the route remains correct. A regulatory sign states what is allowed or prohibited. A warning communicates risk. A service-status sign reports a change such as delay, closure or platform alteration.
Translate according to function. A label should be noun-like and scannable. A warning may need stronger wording. A status update may need a time reference. Function determines grammar.
Step 3: build a destination-name register
Destination names should not drift. Create a controlled register for station names, airport terminals, districts, landmarks, lines, gates, platforms, concourses and interchange names. Record official spelling, local-language form, approved translation if one exists, transliteration if used and any abbreviation.
Place names are identity anchors. A passenger who sees one spelling on the map and another on a platform sign may hesitate at exactly the wrong moment. Search systems also depend on consistency: the destination on the ticket, journey planner, station map and sign should converge.
When an official local form exists, prefer that authoritative form rather than creating a fresh literal translation. Transliteration and translation serve different purposes and should not be confused.
Step 4: preserve the hierarchy of information
Wayfinding systems deliberately rank information. A line name may be more prominent than a platform number. A final destination may be more important than intermediate stops. A terminal identifier may dominate a descriptive phrase. Translation should preserve that hierarchy even when target words are longer.
Do not let a secondary explanatory phrase become visually dominant because the target version expands. Work with designers when necessary. Sometimes a shorter approved term is better because it preserves scan order. Sometimes the layout should change instead of compressing language unnaturally.
The correct question is not “Can this fit?” but “Can the traveller still see the primary decision first?”
Step 5: treat arrows as grammar
Arrows are not decoration. They are part of the sentence. “Platforms 1–4 ↑” means something different from “↑ Platforms 1–4” in some layouts because placement can imply whether the arrow governs one line, a group of destinations or an entire panel.
When translated text changes length or reading direction, arrow relationships can become ambiguous. Check the final sign composition, not just the translated phrase list. Right-to-left languages may require layout decisions that cannot be solved by word substitution alone.
During QA, inspect every directional sign with its arrow. Ask: what exactly does the arrow point to, and could the translated layout make it appear to point to another destination?
Step 6: keep pictograms and words synchronized
Public transport increasingly relies on universal or semi-universal pictograms: toilets, lifts, stairs, baggage, information, accessibility, trains, buses and exits. The translated label must refer to the same concept as the icon.
A mismatch is surprisingly easy. The source may use one umbrella term for “accessible route” while the pictogram specifically depicts a lift. Or a target language may distinguish “toilet,” “washroom” and “restroom” by convention. Check the actual symbol set and local usage.
Icons can reduce language load, but they do not eliminate the need for precise wording. They work best when text, symbol and physical destination all agree.
Step 7: use the target transport system’s established vocabulary
Public transport has conventional language. “Platform,” “track,” “stand,” “bay,” “concourse,” “interchange,” “transfer,” “connection,” “service,” “line” and “route” may have specific local equivalents. Search authoritative transport operators, airport authorities and target-language maps rather than relying only on general dictionaries.
The dictionaries, corpora and parallel-text method is especially useful here. Comparable target-language station maps and airport signs reveal the standard phrase users already recognize.
Naturalness matters because familiar wording reduces decision time.
Step 8: distinguish translation from transliteration
Translation transfers meaning. Transliteration represents a name or word in another writing system. A station name may need transliteration so travellers can match it to tickets, addresses or spoken announcements. A generic instruction such as “Exit” usually needs translation, not transliteration.
Some systems show both local script and romanization. Others use bilingual official names. Establish the project policy before production. Inconsistent transliteration creates search problems and makes names difficult to match across maps and navigation apps.
If several romanization standards exist, follow the authority responsible for the place or transport system.
Step 9: protect numbers, codes and line identifiers
Line numbers, platform numbers, gate numbers, terminal identifiers, exit codes and stop IDs are often the strongest navigation anchors in a multilingual environment. Preserve them exactly unless the system has a formal localization rule.
Do not let typography make “O” and “0,” “I” and “1,” or similar characters ambiguous. If a line is officially “T3” or “EWL,” do not translate the identifier as ordinary text.
Numbers also interact with words. “Platform 2” and “Gate B2” are different structures. The target order may change, but the identifier must stay attached to the correct object.
Step 10: translate route direction using the network convention
Networks describe direction in different ways: compass direction, terminal station, destination city, inbound/outbound, clockwise/anticlockwise, uptown/downtown or branch name. Do not replace one system with another merely because the target language commonly uses a different pattern.
If the source network defines direction by terminal station, preserve that operational convention. If an explanatory translation is necessary for visitors, it should remain consistent across maps, signs and announcements.
Direction is a network concept, not a free-standing vocabulary item.
Step 11: keep line colours and names aligned
Colour is a powerful wayfinding cue, but colour alone should not carry all meaning because of accessibility and display constraints. Translations should preserve official line names and identifiers alongside colour systems.
Check whether the source calls something the “Green Line,” “Line 2,” “East–West Line” or another official name. A literal colour translation can be wrong if the public brand uses a fixed untranslated title.
Maps, platform signs, mobile apps and audio announcements should use the same naming policy.
Step 12: handle exits as destinations, not merely doors
Station exits often have letters or numbers connected to street names and landmarks. A traveller may choose an exit several minutes before reaching street level. Translate the destination information, not only the word “Exit.”
Landmark names require the same discipline as station names. Preserve official naming and recognizable local forms. If a landmark is well known internationally under one name but locally under another, the signage policy should decide whether both appear.
Exit information is the bridge between the transport network and the outside city.
Step 13: make transfers explicit
Transfers are cognitively expensive because passengers must leave one route and enter another. Ambiguous words such as “change,” “connection,” “transfer” and “interchange” can describe different relationships.
Identify what the passenger must do. Change trains on the same platform? Walk to another line? Exit fare gates and re-enter? Take a shuttle? Move between terminals? The translation should support that action.
If local transport vocabulary has a standard word for interchange, use it consistently. Do not choose a casual synonym that users may interpret differently.
Step 14: translate timing information with operational precision
“Last train,” “next train,” “boarding closes,” “gate closes,” “service ends,” “doors closing” and “final call” are not interchangeable. Each refers to a different event in time.
Preserve absolute times, relative times and conditions. If the source says “Boarding closes 15 minutes before departure,” do not compress it to “Arrive 15 minutes early.” The latter changes both action and threshold.
Use the local time format consistently and check day-boundary information for late-night services.
Step 15: dynamic passenger information needs a message library
Digital displays create repeated status messages: delayed, cancelled, diverted, platform changed, not stopping, suspended, replaced by buses, congestion, lift unavailable. Build an approved bilingual message library rather than translating each alert from zero.
The library should include placeholders for line name, destination, time, platform and reason. Protect placeholders during localization. A message template that works grammatically in one language may require reordered variables in another.
Dynamic content is software-like. It needs linguistic design as well as translation.
Step 16: distinguish planned changes from unplanned disruption
“Planned engineering works” communicates something different from an unexpected incident. Passengers use this distinction to judge reliability, urgency and alternative routes.
Translate service-change categories consistently. If the operator distinguishes planned closure, partial closure, delay, severe delay and suspension, preserve those states. Do not reduce them all to “service disruption.”
A status taxonomy helps digital systems and human readers make the same distinction.
Step 17: emergency messages must prioritize action
Emergency wayfinding is related to, but distinct from, ordinary signage. During an evacuation or safety incident, the user needs an immediate action, route and restriction. Long explanations can come later.
Translate imperatives accurately: leave, do not enter, use stairs, do not use lifts, proceed to assembly point, follow staff instructions. Preserve negation and sequence. The emergency alerts and evacuation translation owner provides the deeper warning-language route.
Wayfinding translation should link to that safety system without duplicating it.
Step 18: accessibility information is functional information
“Step-free access,” “accessible toilet,” “hearing loop,” “priority seating,” “boarding assistance” and “lift to platform” describe features people may depend on, not optional amenities.
Use established disability-access terminology in the target language. Avoid vague euphemisms that make the service harder to identify. Check whether symbols and text match.
Accessibility routes should be tested as complete journeys. A correct translation at one lift is not enough if the next sign uses another term or omits the accessible continuation.
Step 19: account for reading time
A passenger walking through a corridor or approaching a junction does not read like someone sitting with a document. Translation must remain scannable. Shorter is often better, but only after meaning and function are secure.
Remove unnecessary words, not necessary distinctions. “Train to City Centre” may be clearer than a literal phrase that preserves source syntax but delays the destination. Use the target language’s conventional compact forms.
Test at realistic viewing distance and movement speed whenever possible.
Step 20: manage character expansion without damaging meaning
Target languages may expand substantially compared with the source. A fixed sign panel, mobile display or LED board may not have enough space.
Create a short-form policy before random abbreviations appear. Decide which terms may be abbreviated, how abbreviations are formed and where full forms remain necessary. Never invent opaque abbreviations simply to make text fit.
If the target cannot fit safely, change layout, line breaks or panel design. Physical constraints should not silently erase information.
Step 21: line breaks can change interpretation
Wayfinding text is often stacked. A line break may separate one destination from another or divide a phrase. In translation, longer wording can force new breaks that accidentally suggest new groupings.
Review signs visually. Ask whether two lines look like two destinations, whether an arrow seems to govern both, and whether punctuation is needed to preserve grouping.
Text segmentation is part of meaning in a spatial system.
Step 22: multilingual order should follow a policy
Which language appears first? Are languages stacked, side by side or rotated? Is the order fixed or location-dependent? These are governance questions, not translator improvisations.
Consistent language order helps users learn where to look. It also prevents perceived hierarchy from changing randomly across a network. The policy may be based on official-language requirements, user needs, space and operational context.
Translators should receive the policy rather than making case-by-case decisions.
Step 23: maps need terminology QA separate from prose QA
Maps contain dense labels, abbreviations, legends, direction indicators and route names. A single wrong label can affect thousands of users.
Perform a dedicated map pass. Check every station name, legend term, symbol label, interchange marker and footnote. Compare with the destination-name register. Do not assume a term translated correctly in a guidebook was copied correctly into the map artwork.
Maps should be reviewed at final size because truncation and overlap can appear only after layout.
Step 24: audio announcements must match visible language
Passengers combine what they hear with what they see. The announced station name, line name, platform and direction should match the sign system closely enough to be recognized as the same information.
If pronunciation or transliteration differs, users may fail to connect the audio and visual forms. Maintain a pronunciation guide for proper nouns and unusual technical terms.
Audio translation also requires timing and clarity. A long target announcement may overlap the next operational message.
Step 25: do not translate brand names as ordinary words
Transport networks contain branded service names, fare products, travel cards, lounges, express services and named routes. Verify official localized forms before translating them.
A literal translation can create a product that does not exist in the passenger’s app or ticket machine. When a brand remains untranslated, nearby explanatory language may still need localization.
Identity and explanation should be separated deliberately.
Step 26: fares and ticketing need terminology consistency
“Single,” “return,” “day pass,” “stored value,” “contactless,” “fare cap,” “concession,” “zone” and “validation” can have system-specific meanings. A visitor may make a financial decision based on one small label.
Use the fare authority’s official terminology where available. Preserve eligibility conditions and time limits. Do not simplify a fare rule so aggressively that the passenger buys the wrong product.
For complex public-service eligibility, route readers to the dedicated public-service translation methods rather than overloading wayfinding signs.
Step 27: abbreviations must be learnable
Transport systems love abbreviations because space is scarce. But unfamiliar travellers cannot decode internal shorthand. Translate only approved public abbreviations.
Where a line acronym is a fixed brand, keep it. Where a generic term is abbreviated in the source because English is compact, the target may need a different abbreviation or a full word.
Test abbreviations with real users who do not already know the system.
Step 28: respect local address and landmark conventions
A station exit may point to street, district, building, block number or landmark. The ordering of address elements differs across languages and countries.
Translate the address presentation according to local convention while protecting proper names and numbers. If the target audience is international, avoid a format that looks natural but hides the most useful landmark until the end.
Wayfinding is about retrieval speed as much as grammatical correctness.
Step 29: consider tourists without writing only for tourists
Public transport serves regular commuters, older adults, students, disabled users, workers and visitors. A multilingual system should not become tourist-only language that confuses local riders.
Use stable network terminology, clear icons and predictable naming. Where an explanatory phrase benefits newcomers, ensure it does not replace the official term they will see elsewhere.
The strongest system lets a first-time user learn the network while remaining familiar to a daily user.
Step 30: avoid false friends in transport vocabulary
Words resembling each other across languages can be dangerous when they refer to different transport concepts. A familiar-looking word may mean station in one language but stop in another, or platform in one system but track in another.
Verify with target transport sources. The false friends owner gives the general linguistic method.
In wayfinding, terminology errors become movement errors.
Worked example 1: “Connections” at an airport
Suppose a sign after immigration says “Connections.” The translator should ask: connecting flights only, or all onward transport? Does the airport use a specific term in its target-language website? Is there a transfer desk, security re-screening or terminal shuttle on the route?
A generic dictionary equivalent for “connection” may be too broad. The correct target wording should match the airport’s operational concept of flight transfer. Then check that the same term appears in terminal maps and digital displays.
The word is short; the context is not.
Worked example 2: “Exit A — Museum District”
This sign has three anchors: exit concept, exit identifier and destination landmark. The exit code must remain exact. The museum district may have an official local name. The target language may place the identifier before or after the word for exit.
Build the target from function: first help the reader identify the exit, then confirm the destination. Check that the map and street-level confirmation sign use the same landmark form.
A correct sign should remain correct across the entire exit journey.
Worked example 3: “Trains do not stop at Central after 23:30”
The message combines route, negation, destination and time condition. Missing “not” reverses the instruction. Misplacing “after 23:30” can make the restriction appear to apply to the wrong service.
Translate the logic explicitly. Then test whether the target fits the display. If a shorter form is necessary, preserve all four information units before removing anything else.
Operational messages should be reducible only after their logical structure is mapped.
Worked example 4: lift outage on an accessible route
“Lift to Platforms 3–4 unavailable. Use accessible route via Exit C.” The target must identify the affected lift, the platforms, the status and the alternative route. A vague “Lift unavailable” does not give enough information to a passenger who depends on step-free access.
Check whether “accessible route” has a standard term and icon. Confirm that Exit C actually carries the translated destination onward.
Accessibility information should close the loop, not merely announce a failure.
Worked example 5: multilingual evacuation route
“Emergency exit only. Alarm will sound.” The message has regulation and consequence. A literal translation that makes “only” modify “alarm” instead of “exit” can distort the rule.
Use short, conventional emergency wording and verify it with the icon and door function. If a legal or fire-safety standard defines the wording, follow that standard.
High-stakes signs should be reviewed by qualified local stakeholders as well as linguists.
A repeatable wayfinding translation workflow
- Inventory every sign, map label, display message and announcement.
- Attach each item to a physical or digital location.
- Assign a function: identify, direct, confirm, regulate, warn, inform or update status.
- Build the destination-name and terminology register.
- Research authoritative target-language transport usage.
- Translate with arrows, icons, codes and layout context visible.
- Check character limits and line breaks.
- Review all dynamic templates and variables.
- Run map, audio and accessibility consistency passes.
- Test representative journeys with target-language users.
The workflow moves from space to language and back to space. That is the defining feature of wayfinding translation.
Failure mode: translating a sign list without locations
A spreadsheet containing only source phrases strips away the context that gives wayfinding language meaning. “Arrivals,” “Transfer,” “Services,” “Stop,” “Stand” and “Gate” can all be mistranslated when the translator cannot see where they appear.
At minimum, add location, screenshot, sign type and destination notes. Better still, provide plans or photographs. The translator should be able to reconstruct the passenger decision.
Context is not a luxury input. It is part of the source.
Failure mode: overexplaining
A translator may correctly understand a term but produce a sentence where the source has a two-word label. The explanation may be linguistically excellent yet unusable at walking speed.
Separate sign text from explanatory content. Keep the sign compact, and place detail in maps, apps or help pages where appropriate.
Wayfinding quality is partly the art of preserving meaning under severe attention limits.
Failure mode: copying source-language word order
Directional panels often use fragments rather than full sentences. Copying source order can bury the destination or make several arrows hard to match.
Use natural target-language scanning order. Preserve the destination, direction and relationship, not the source sequence.
The long and complex sentence method helps with structure, but short signs require the same principle in compressed form: rebuild the target around function.
Failure mode: inconsistent station names
One station name may appear in several romanizations, translations or abbreviations across legacy materials. Choosing different forms from different sources fragments the user experience.
Establish one authority and one approved register. Where legacy variants remain in public use, document them as aliases for search, not as uncontrolled sign variants.
Consistency turns separate signs into one navigable system.
Failure mode: assuming icons are universal
Many pictograms are widely understood, but not all meanings are universal. A symbol may be culturally unfamiliar or interpreted differently. Text can disambiguate, and user testing can reveal problems.
Do not remove useful wording merely because an icon exists. Conversely, do not overload signs with text when an established symbol already does the work.
Translation and visual communication should share the load.
Failure mode: localizing one channel but not the others
A passenger may see a translated map but hear an untranslated announcement, or see a localized app label that does not match station signage. The result is cross-channel friction.
Create a shared terminology source for physical signs, websites, apps, audio scripts, help desks and journey planners. The same destination and service should remain recognizable across channels.
Multilingual wayfinding is an ecosystem, not a collection of signs.
Testing: run real journeys, not only proofreading
Linguistic QA can catch grammar and terminology errors. It cannot prove that a traveller will choose the correct corridor at a junction. Test representative journeys.
Give target-language users goals: reach Platform 4 from the street; transfer from Line A to Line B; find the accessible exit; locate baggage reclaim; recover from a platform change. Observe hesitation, wrong turns and questions.
A translation problem may appear as behaviour before anyone can describe the wording problem.
Test under time pressure
Wayfinding users often make decisions while walking, carrying luggage, watching children or worrying about departure time. Testing at a desk can overestimate comprehension.
Measure whether users can scan and act. If they repeatedly stop to read a long target phrase, the wording or hierarchy may need revision.
The aim is not speed for its own sake. It is sufficient clarity at the speed the environment demands.
Test unfamiliar users
Staff and translators know the system too well. They fill gaps unconsciously. Recruit users who resemble first-time passengers and do not already know the building or network.
Ask them to explain what they think a sign means before telling them the intended answer. Their interpretation reveals whether the target language actually carries the intended decision.
Expert familiarity can hide navigation defects.
Practice exercise for students: translate one station journey
Choose a public transport map in a source language you know. Create a fictional journey with entrance, ticketing, platform, transfer and exit. Extract only the signs needed for that journey.
Translate them, then place them in journey order. Check whether terminology remains stable. Ask another learner to reconstruct the journey from your target signs alone.
This exercise teaches that translation quality is relational: each sign is easier to judge when connected to the next.
Practice exercise: compress without losing action
Take five long passenger messages and write a full accurate translation first. Then produce a display-length version under a strict character limit. List the information you kept and removed.
You may shorten politeness, repetition or explanatory phrasing, but not destination, condition, time, negation or required action.
This builds disciplined compression rather than arbitrary shortening.
Practice exercise: terminology from comparable systems
Select one concept such as interchange, step-free access or baggage reclaim. Search three authoritative target-language transport systems. Record the terms each uses, context, region and sign examples.
Choose the best term for your project and explain why. The point is not to find one universal answer but to learn how convention depends on network and audience.
This is translation research applied to a physical interface.
How vocabulary knowledge supports wayfinding translation
Even short signs depend on semantic precision. Near-synonyms such as entrance, access, entry, exit, departure, connection and transfer may overlap in everyday speech but separate important operational concepts.
The Vocabulary Learning Hub helps learners build the sense, collocation and register knowledge needed to distinguish these terms. Deep vocabulary knowledge reduces the temptation to choose the first dictionary equivalent.
In wayfinding, vocabulary precision becomes spatial precision.
How grammar supports wayfinding translation
Signs often omit articles, subjects and verbs. Yet grammar still controls scope: “No entry except staff,” “Passengers for Terminal 2,” “Trains to Airport,” “Lift access to Platforms 1–2.”
The How English Works route helps learners see how prepositions, modifiers, negation and phrase structure organize meaning. That knowledge is valuable when source signs are fragments.
Short language is still structured language.
How machine translation can help—and where it fails
Machine translation can accelerate large inventories and suggest consistent phrasing, especially when a validated termbase exists. But isolated sign strings are exactly the kind of content that can lack enough context for reliable automatic disambiguation.
Provide metadata: sign function, location, screenshot, product term, character limit and neighbouring text. Then review every operationally important message. A fluent machine output is not proof that the user will go the right way.
Automation should inherit context, not replace it.
Release control for multilingual signage
Before release, freeze the destination register and message library for the version being installed. Track which sign artwork or digital string belongs to which revision.
Physical signs are expensive to replace. Dynamic systems are easier to update but can propagate errors quickly. Both need version control.
Record approval from language reviewers, transport operations, accessibility stakeholders and safety specialists where relevant.
After launch: treat wrong turns as data
Wayfinding can be improved after deployment. Repeated staff questions, missed transfers, crowding at a junction or unusual path choices can reveal that a sign is unclear even when no one reports a translation error.
Compare behaviour across language groups where possible. The problem may be wording, placement, hierarchy, pictogram choice or a combination.
Translation quality can therefore be monitored through real movement.
Frequently asked questions
What is wayfinding translation?
Wayfinding translation localizes the language used to help people orient themselves and move through places such as stations, airports, hospitals, campuses and public buildings. It includes signs, maps, digital displays, route messages, announcements and accessibility information.
Why is wayfinding translation different from normal translation?
Because the text is short, spatial, time-sensitive and integrated with arrows, symbols, colour, architecture and live operational information. The translator must preserve a physical decision, not only sentence meaning.
Should place names be translated?
Use the official naming policy. Some names have established translated forms, some are transliterated, and some should remain unchanged. Consistency across maps, tickets, apps and signs is critical.
How do you translate signs with very little space?
Translate the full meaning first, identify the essential destination, action and condition, then use approved compact target-language wording. If necessary, change layout rather than deleting critical information.
Can machine translation be used for public signs?
It can assist with drafts and repeated message libraries, but context-poor strings, safety instructions, place names and directional language require human verification and testing in the actual environment.
How should multilingual signs be tested?
Use linguistic review plus real journey testing with target-language users. Ask people to reach destinations, make transfers and recover from service changes without coaching.
Contextual next routes
For the general semantic foundation, continue with Translate Meaning, Not Just Words. For register and audience, use Use Context, Tone and Register. For terminology research, use Dictionaries, Corpora and Parallel Texts. For public-service forms and eligibility, continue to Public-Service Forms, Eligibility Rules and Official Notices.
The principle to keep
Wayfinding translation is successful when the target-language reader does not have to solve the language before solving the journey. The destination is recognizable. The arrow points clearly. The platform or gate identifier is stable. The transfer term matches the network. The emergency message preserves its force. The accessible route remains continuous. The digital update matches the physical system.
Translate the route, not merely the sign. A two-word label can carry an entire chain of movement, and the translator’s job is to keep that chain intact from entrance to destination.