TempoLife › Features › Help translate TempoLife › lv
Latvian — Latviešu
0 of 5 210 TempoLife strings are translated into Latvian (0.0%). Browse the string list, see the English source next to the current text, and suggest a better one.
Not started. Nothing is translated yet, so every string here is an open one.
The string list
Every row is one string in the app. The English column is the source; the Latvian 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 | Latvian |
|---|---|---|
heart.tour_hero | This is your latest reading and the day summary. | missing |
heart.tour_next | Next | missing |
heart.tour_skip | Skip | missing |
heart.tour_tabs | Views: today, trends, recovery and workouts. | missing |
heart.trimp_days | days | missing |
heart.trimp_neutral | No clear link between training load and sleep yet. | missing |
heart.trimp_note | TRIMP = zone-weighted training-load minutes. An observational pattern from your own histo… | missing |
heart.trimp_recover_less | After heavier training days your sleep tends to be shorter. | missing |
heart.trimp_recover_more | After heavier training days your sleep tends to be longer. | missing |
heart.trimp_sleep_title | Load & sleep | missing |
heart.trimp_title2 | Load and next-night sleep | missing |
heart.unusual_above | Today's resting heart rate is above your own baseline ({n} BPM). | missing |
heart.unusual_below | Today's resting heart rate is below your own baseline ({n} BPM). | missing |
heart.unusual_note | Compared only with your history — not a medical alert. | missing |
heart.usual_week | usual week | missing |
heart.vs_baseline | vs baseline | missing |
heart.wake_rise_delta | rise in the first hour awake | missing |
heart.wake_rise_note | How fast your heart rate climbs after waking, across recent nights. | missing |
heart.wake_rise_title | Wake-up rise | missing |
heart.weather_city_ph | Location (city) | missing |
heart.weather_cooler_lower | On cooler days your heart rate tends to be slightly lower. | missing |
heart.weather_empty | At least 4 days of weather and heart-rate data are needed. | missing |
heart.weather_neutral | No clear link between weather and heart rate so far. | missing |
heart.weather_not_found | Location not found | missing |
heart.weather_note | Weather data: Open-Meteo (no API key). Observational, not causal. | missing |
heart.weather_saved | Weather synced | missing |
heart.weather_sync | Sync | missing |
heart.weather_title | Weather & heart rate | missing |
heart.weather_warmer_higher | On warmer days your heart rate tends to be slightly higher. | missing |
heart.week_summary_title | Week summary | missing |
heart.workout_avg | Average BPM | missing |
heart.workout_cycling | Cycling | missing |
heart.workout_hiking | Hiking | missing |
heart.workout_peak | Peak BPM | missing |
heart.workout_running | Running | missing |
heart.workout_samples_missing | Not enough heart-rate samples for zones and recovery. | missing |
heart.workout_strength | Strength training | missing |
heart.workout_swimming | Swimming | missing |
heart.workout_yoga | Yoga | missing |
heart.workouts_empty | Synced workouts with heart-rate samples will appear here. | missing |
heart.workouts_title | Workout zones and recovery | missing |
heart.ws_active | Active min | missing |
heart.ws_avg | Week avg | missing |
heart.ws_load | Load · TRIMP | missing |
heart.ws_max | Week max | missing |
heart.ws_nights | Nights | missing |
heart.ws_resting | Resting | missing |
heart.ws_vs_last | vs last week | missing |
heart.zone_1 | Rest | missing |
heart.zone_2 | Light | missing |
heart.zone_3 | Moderate | missing |
heart.zone_4 | Hard | missing |
heart.zone_5 | Max | missing |
heart.zone_add_birthday | Add your birthday in Profile to calculate personalized zones. | missing |
heart.zone_goal_active_days | active days | missing |
heart.zone_goal_empty | Set a weekly zone-minutes goal. | missing |
heart.zone_goal_left | {n} min left | missing |
heart.zone_goal_met | Goal met! 🎉 | missing |
heart.zone_goal_ph | Goal (min) | missing |
heart.zone_goal_save | Save | missing |
← Previous Page 45 of 87 Next →
What makes a good Latvian 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 Latvian 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