Winding Up a Day: When the Pun Inverts the Meaning
You are localizing a productivity app's onboarding flow from Spanish (Spain) into English (US). The headline is «Dale cuerda a tu día»; the subtitle reads «Organiza tus tareas, respira y empieza con buen pie»; the primary button says «Empezar ahora». Design specifies a hard 12-character limit on the button and two lines of 40 characters for the headline. The marketing lead writes: “Keep the pun - that's the whole campaign. And stay literal where you can.” The Spanish uses «tú» throughout with a warm, playful voice; the US brand guide says friendly but never cute and bans exclamation marks. The home screen displays a literal winding-key icon.
1. Can the pun in «Dale cuerda a tu día» be kept literally? Evaluate the brief and propose a direction.
Read the worked answer
No - and the reason is a semantic trap, not a stylistic preference.
Analysis: dar cuerda means to wind a mechanism, and figuratively to egg someone on. The obvious English calque is “wind up,” which in English means to finish or end. A literal rendering would tell the user to end their day on a screen designed to start it. That is an accuracy failure disguised as fidelity.
What the pun is doing: it is not carrying information; it is carrying tone and the icon image (a winding key). So the translation unit is the function - energize, set in motion, get momentum - not the wordplay.
Proposals to table with rationale: “Wind up your day” (reject, inverted), “Get your day moving” (keeps the mechanism image, fits 40 chars, no pun), “Start your day on a roll” (new pun, different image), “Give your day a jump start” (mechanism, idiomatic).
Brief conflict to flag: “keep the pun” and “never cute, no exclamation marks” pull in opposite directions. Ask which constraint wins; recommend function-first and offer the pun as an option with risk noted.
2. The button must fit 12 characters. How do you choose, and what do you ask design?
Read the worked answer
First, question the constraint. “12 characters” is usually a proxy for pixel width. “Get started” (11 characters) is typographically wider than “Start now” (9) because of the d/t pair and the space. If the limit is really width, the candidate set changes entirely. Ask for the font, weight, size, and whether the limit is characters or px - this takes one email and prevents a truncated button on launch day.
Candidates against «Empezar ahora»:
- Start now (9) - mirrors the imperative and ahora's urgency; the least marked US option.
- Get started (11) - the idiomatic US onboarding label; drops the urgency nuance but the subtitle's «empieza» carries it.
- Let's go (8) - most playful; clashes with never cute.
- Begin (5) - safe, cold.
Decision: if the limit is characters, Get started fits and reads as native onboarding; if pixels, likely Start now. Either way the button must match the headline's register, so decide the headline first and let the button follow. Log the choice and note expansion risk for other locales.
3. A colleague suggests the subtitle line should read “Organize your tasks, breathe, and get off on the right foot,” but the client glossary forbids “get off” and mandates “task” over “to-do.” Resolve.
Read the worked answer
Separate the two objections.
The idiom: «empezar con buen pie» = to start well / get off on the right foot. The English idiom is an exact functional match and fits the 40-character line. Keeping it is defensible and better than a flat “start well.” The glossary objection is likely about register (the phrase can read casual), not about a technical term, and glossaries exist to fix terminology, not to veto idioms. Escalate the specific entry rather than the sentence.
«Tareas»: here the glossary is right and applies. “Tasks” is the product's own UI label; if the screen behind the subtitle says Tasks, using “to-do” in the copy creates a mismatch between what the user reads and what they see. Terminology consistency beats synonym variation.
Result: “Organize your tasks, breathe, and get off on the right foot.” Flag the idiom entry to the glossary owner for a ruling, and note in the delivery which constraint you treated as binding. When style guide and readability conflict, name the conflict in writing rather than resolving it invisibly.