TempoLife › Features › Help translate TempoLife › es
Spanish — Español
0 of 5 217 TempoLife strings are translated into Spanish (0.0%). Browse the string list, see the English source next to the current text, and suggest a better one.
Not started. The largest audience on this list, and the one with the most regional variation to decide on.
The string list
Every row is one string in the app. The English column is the source; the Spanish column is what ships today, or missing when nothing does. Open a row to see it in the other languages and to suggest a change.
All strings Missing only
| Key | English | Spanish |
|---|---|---|
nutr.breakfast_short | 🌅 Breakfast | missing |
nutr.camera_shortcut_title | Take a food photo | missing |
nutr.carbohydrates | carbs | missing |
nutr.carbs | Carbohydrates | missing |
nutr.carbs_short | C | missing |
nutr.choose_meal | Choose meal | missing |
nutr.code | Code | missing |
nutr.composition | Where today's calories come from | missing |
nutr.connection_error | Connection error | missing |
nutr.cooked_add_portion | Log one portion | missing |
nutr.cooked_bank_borss | Borscht | missing |
nutr.cooked_bank_kanapasta | Chicken pasta | missing |
nutr.cooked_bank_puder | Porridge | missing |
nutr.cooked_btn | Home-cooked dish | missing |
nutr.cooked_estimate | Estimate | missing |
nutr.cooked_evidence | Matched ingredients | missing |
nutr.cooked_hint | List the ingredients — AI matches them to foods and we compute the macros | missing |
nutr.cooked_ingredients | Ingredients (e.g. 200 g chicken, 1 cup rice) | missing |
nutr.cooked_logged | {name} portion logged | missing |
nutr.cooked_name | Dish name (optional) | missing |
nutr.cooked_per_portion | {g} g per portion | missing |
nutr.cooked_recomputed | Macros recomputed from food database | missing |
nutr.cooked_servings | Servings | missing |
nutr.cooked_short | dish estimate | missing |
nutr.cooked_title | Estimate a home-cooked dish | missing |
nutr.days_logged | days logged | missing |
nutr.days_short | d | missing |
nutr.delete | Delete | missing |
nutr.deleted | Deleted | missing |
nutr.dinner | Dinner | missing |
nutr.dinner_short | 🌆 Dinner | missing |
nutr.double | Double | missing |
nutr.eat_window | Eating window today | missing |
nutr.enter_amount | Enter amount | missing |
nutr.error | Error | missing |
nutr.fat | Fat | missing |
nutr.fat_short | F | missing |
nutr.fats | fat | missing |
nutr.food_added | {name} added ({cal} kcal) | missing |
nutr.food_added_db | "{name}" added to database | missing |
nutr.food_items | food items | missing |
nutr.frequent | Frequent | missing |
nutr.ghost_day | Usual picks for an empty day | missing |
nutr.halve | Halve | missing |
nutr.in_meal | logged in this meal | missing |
nutr.insights_days_logged | {n} days analysed | missing |
nutr.insights_late | {pct}% of calories after 20:00 on {days} logged days | missing |
nutr.insights_meal_variance | {meal} is your most regular meal (median {time}, spread ±{min} min) | missing |
nutr.insights_missed | {meal} skipped {n}× | missing |
nutr.insights_title | Eating regularity | missing |
nutr.insights_weekend_earlier | Weekend eating shifts {min} min earlier | missing |
nutr.insights_weekend_later | Weekend eating shifts {min} min later | missing |
nutr.invalid_weight | Enter a valid weight (20–500 kg) | missing |
nutr.invalid_weight_imp | Enter a valid weight (44–1100 lb) | missing |
nutr.kcal_100g | kcal/100g | missing |
nutr.kcal_eaten | kcal eaten | missing |
nutr.kcal_left | {kcal} kcal left | missing |
nutr.kcal_target | kcal target | missing |
nutr.lunch | Lunch | missing |
nutr.lunch_short | ☀️ Lunch | missing |
← Previous Page 61 of 87 Next →
What makes a good Spanish string here
Keep the placeholders. Anything in curly braces is replaced with a real value before the string is shown. Drop {n} and the sentence loses its number; rename it and the replacement silently fails. They can move within the sentence, but they must all still be there and spelled exactly as in the English.
Watch the length. Most of these strings live in a fixed space: a tab label, a button, a stat tile under a big number. A translation half again as long as the English will be clipped or will push a layout apart on a small phone. When the natural translation is much longer, a shorter and slightly blunter phrasing is the right answer.
Use the app's own vocabulary consistently. The same concept should read the same way everywhere — one word for a logged meal, one for a fast, one for a streak. Consistency matters more than variety; a synonym used once reads as a different feature.
Do not translate health claims into advice. Several strings deliberately describe a number without telling anyone what to do about it. A translation that turns "your resting rate is above your baseline" into "see a doctor" changes what the app claims, which is not a translation decision.
How this list is built
The list is parsed from the app's own translation files at the moment you load the page, so it cannot drift from what ships. Strings the parser could not read in a single pass are left out entirely — 0 lines in the Spanish files fell into that category — rather than being shown with a guessed value.
Source: TempoLife app translation files (assets/js/i18n*.js), parsed at page render · checked 2026-09-02