TempoLife › Features › Help translate TempoLife › de
German — Deutsch
0 of 5 217 TempoLife strings are translated into German (0.0%). Browse the string list, see the English source next to the current text, and suggest a better one.
Not started. German compounds are long, so button and tab strings need particular care.
The string list
Every row is one string in the app. The English column is the source; the German 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 | German |
|---|---|---|
nutr.meal_times | 🕐 Meal times | missing |
nutr.meal_times_hint | Set when you usually eat. Photos and quick logs file into the nearest meal, and your fast… | missing |
nutr.micro_all_covered | All key micronutrients covered this week | missing |
nutr.micro_b12 | Vitamin B12 | missing |
nutr.micro_calcium | Calcium | missing |
nutr.micro_cov | {pct}% covered | missing |
nutr.micro_iron | Iron | missing |
nutr.micro_magnesium | Magnesium | missing |
nutr.micro_omega3 | Omega-3 | missing |
nutr.micro_title | Micronutrient gaps this week | missing |
nutr.micro_vitamin_d | Vitamin D | missing |
nutr.no_frequent | No frequent foods yet | missing |
nutr.now_meal | Next up: {meal} | missing |
nutr.over_target | {kcal} kcal over target ({target}) | missing |
nutr.per_100g | /100g | missing |
nutr.plan_ad_body | AI builds today’s meals and shows you how to cook them. | missing |
nutr.plan_ad_title | AI meal plan + recipes | missing |
nutr.plan_ai | AI meal plan | missing |
nutr.plan_ate | Ate & log | missing |
nutr.plan_ate_this | I ate this — log it | missing |
nutr.plan_gen | Generate | missing |
nutr.plan_title | Meal plan | missing |
nutr.plan_vs_actual | plan {plan} · ate {actual} | missing |
nutr.proj_after | {kcal} kcal projected ({target} target) | missing |
nutr.prompt_calories | Calories per 100g: | missing |
nutr.prompt_carbs | Carbs per 100g (g): | missing |
nutr.prompt_fat | Fat per 100g (g): | missing |
nutr.prompt_food_name | Food name: | missing |
nutr.prompt_protein | Protein per 100g (g): | missing |
nutr.protein | Protein | missing |
nutr.protein_pace | {eaten}/{target} g protein | missing |
nutr.protein_short | P | missing |
nutr.proteins | protein | missing |
nutr.qty | Quantity | missing |
nutr.rec_all_good | Everything is balanced! Your nutrition is healthy and on target. | missing |
nutr.rec_consistent | Amazing consistency! Food logging gives the best health overview. | missing |
nutr.rec_deficit_fail | To lose weight, you should stay under your calorie limit. You're currently eating too muc… | missing |
nutr.rec_deficit_good | Great! You're within your weight loss target — keep up the pace! | missing |
nutr.rec_eat_less | You're eating {pct}% of your target on average. Reduce portions or swap calorie-dense foo… | missing |
nutr.rec_eat_more | You're eating only {pct}% of your target on average. Add more food — your body needs fuel! | missing |
nutr.rec_good_fiber | Excellent fiber intake! Keep up the healthy choices. | missing |
nutr.rec_high_fat | Fat intake is high. Prefer healthy fats (nuts, avocado, olive oil). | missing |
nutr.rec_high_protein | Protein is very high. Not harmful, but balance your other macros too. | missing |
nutr.rec_log_more | You're logging food rarely — try logging daily for more accurate recommendations. | missing |
nutr.rec_low_fat | Fat is too low — your body needs healthy fats for hormones and vitamins. | missing |
nutr.rec_low_fiber | Fiber is low! Add vegetables, fruits, whole grains, and legumes. | missing |
nutr.rec_low_protein | Protein is too low! Add meat, fish, eggs, dairy, or legumes. | missing |
nutr.rec_surplus_fail | To gain mass, you need to eat more. Increase portions and add snacks. | missing |
nutr.rec_surplus_good | Good! You're within your mass gain target — keep it up! | missing |
nutr.rec_trend_falling | Calorie intake is falling — eat more to support mass gain. | missing |
nutr.rec_trend_rising | Calorie intake is rising — make sure your weight loss goal isn't compromised. | missing |
nutr.recent | Recently added | missing |
nutr.recommendations | Recommendations | missing |
nutr.remaining | remaining | missing |
nutr.save_error | Error saving | missing |
nutr.scale_error | Could not adjust portion | missing |
nutr.scaled | Portion adjusted | missing |
nutr.scanning | Searching product... | missing |
nutr.scanning_barcode | Scanning barcode | missing |
nutr.search_empty | Food not found. Add your own ↓ | missing |
← Previous Page 62 of 87 Next →
What makes a good German 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 German 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