TempoLife › Features › Help translate TempoLife › lv

Latvian — Latviešu

0 of 5 320 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.

0translated

5 320total strings

0.0%coverage

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

Page 89 of 89 · 5 320 strings listed.
Key	English	Latvian
`wt.save`	Save	missing
`wt.save_target`	Save	missing
`wt.saved`	✅ Weight saved	missing
`wt.see_all`	See full history	missing
`wt.set_target`	Set target weight	missing
`wt.src_hc`	Google Health	missing
`wt.src_manual`	Manual	missing
`wt.status_creeping_up`	Weight is slowly creeping up	missing
`wt.status_dropping`	Weight is dropping	missing
`wt.status_gaining`	Weight is rising — mass gain is working!	missing
`wt.status_gaining_bad`	Weight is rising — but your goal is weight loss	missing
`wt.status_losing`	Weight is dropping — you're on track!	missing
`wt.status_losing_bad`	Weight is dropping — but your goal is mass gain	missing
`wt.status_stable`	Weight is stable	missing
`wt.status_stable_good`	Weight is stable — excellent!	missing
`wt.streak`	day streak	missing
`wt.subtitle`	Weight, BMI and trend	missing
`wt.target`	Target	missing
`wt.target_analysis`	Target analysis	missing
`wt.target_bmi`	Target BMI	missing
`wt.target_bmi_will_be`	BMI at target weight	missing
`wt.target_cleared`	Target weight removed!	missing
`wt.target_kg`	Target (kg)	missing
`wt.target_saved`	Target weight saved!	missing
`wt.target_weight`	Target weight	missing
`wt.title`	Weight tracking	missing
`wt.to_gain`	To gain	missing
`wt.to_lose`	To lose	missing
`wt.today`	today	missing
`wt.trend`	7-day trend	missing
`wt.trend_14d`	14-day trend	missing
`wt.trend_down`	Falling	missing
`wt.trend_stable`	Stable	missing
`wt.trend_up`	Rising	missing
`wt.underweight`	Underweight	missing
`wt.weeks`	weeks	missing
`wt.weeks_est`	Estimated time	missing
`wt.weight`	Weight	missing
`wt.weight_kg`	Weight (kg)	missing
`wt.weight_lb`	Weight (lb)	missing

← Previous Page 89 of 89

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

All languages