Travel conversation guide

Keep an address intact when translating a request

Copy the address from the venue or booking, preserve its original spelling, and translate the request around it. Check the map pin and entrance separately.

Android release in preparation

Quick Translate and experimental Live Interpreter are the current foundation. This website will link to the official Google Play listing when it is public. Product previews and examples are illustrative.

See launch status →

Make a destination card

FieldUseCheck
Venue nameThe name used by the venueA translated nickname may not identify it.
AddressOriginal spelling and scriptKeep building and unit numbers intact.
Map pinA saved link or clearly labelled mapCheck that it points to the intended building.
EntranceThe venue’s own directions if suppliedA rear entrance can differ from the main address.
RequestOne short task such as “Please take me here”Keep the task separate from the address text.

Use the confirmation card to present a value clearly. The card copies your entry; it does not validate an address or translate an arbitrary sentence.

Preserve the text that identifies the place

Do not replace a person’s name, building name or local script with a guessed translation. If your booking supplies both a local address and a romanized version, keep them labelled. A person reading the local script may find it more useful than a phonetic approximation.

Fictional example: a hotel confirmation includes a street address and “Entrance on the courtyard side.” Put the address on one line and the entrance note on another. Do not merge the courtyard instruction into the official street name.

Check spoken and written understanding separately

  • Show the destination while you make the request.
  • Ask the other person to identify the same place on the map.
  • Resolve a branch, building or entrance mismatch before moving on.
  • Keep any new meeting point distinct from the original address.

A translator can produce a plausible sentence while still substituting a place name. Read the name and numbers on screen. If you cannot read the destination script, compare it with the original source rather than editing it from memory.

Show only the detail needed

A destination screenshot does not need your full booking code, passport details or private messages. Prepare the card while you have time, then keep the original booking available if authorised staff need it. Read the privacy checklist for deciding what to enter into a translation service.

Sources and scope

For taxi travel in Japan, JNTO recommends keeping the destination written in Japanese, especially for a less familiar place. The destination-card fields, entrance example and privacy checklist here are editorial preparation guidance; the source does not validate an address, map pin or universal travel procedure.

Practical examples are editorial exercises, not recordings, measured app results or claims about a currently released feature.

Help us improve Pocket’s website

Allow Google Analytics and Ahrefs Web Analytics to measure visits to Pocket’s website? Google also measures scrolling, outbound links and tool activity. You can decline and change your choice below at any time.

What is measured

With your permission, Google receives website activity and browser/device information. Ahrefs receives page visits and browser/device information, and uses IP addresses to estimate location. This measurement excludes URL query strings, fragments, form contents, email addresses and app conversations. Ahrefs does not receive referring URLs. Advertising personalization is disabled. Google Analytics cookies last up to 90 days; Ahrefs uses no analytics cookies. Your choice is saved on this device for 180 days. Provider privacy information: Google and Ahrefs. Contact Pocket support with website data questions.