Slovak translation (draft, for review)

[somansch]

Slovak, both halves of it, as a draft for @petersoniq to correct. Closes #7 once it is reviewed.

What is in here

File	Strings	Where they came from
custom_components/annuals/translations/sk.json	257	114 are yours, word for word. Your upload in #7 was cut off mid-string at 44% of the file, so the other 143 are filled in here.
custom_components/annuals/frontend/annuals-card.js	459	All new. The card carries its own copy of every language and falls back to English without an sk block, so sk.json on its own would have given you a Slovak dialog and an English card.

What has been checked, and what has not

Verified mechanically: both files have exactly the same keys as English (257 and 459, none missing, none extra), every {placeholder} is present and identical, the long descriptions keep their line structure, and the card still parses with the block inserted.

Not verified: whether it is good Slovak. That is the entire point of this branch.

Three keys in the card are code rather than text, and are not literal translations:

inDays: (n) => `o ${n} ${n < 5 ? "dni" : "dní"}`,   // o 2 dni / o 5 dní
daysAgo: (n) => `pred ${n} dňami`,
possessive: (name) => name,
ordinalParts: (n) => ({ num: `${n}.`, sup: "" }),   // 27. — no raised suffix

The timeline sentence follows the Czech one and uses a dash instead of a verb — {possessive}: {ordinal}{sup} {type} — {when} — which sidesteps the case and gender agreement a literal "is" would need. Say so if a Slovak reader would phrase it differently.

One thing to decide

Your strings use two words for the product: the title is „Výročia", the hub is „Centrum Ročenky", and VIP annual became „VIP ročenka". Your wording is untouched, and the new strings follow whichever you had used nearby — but it should be one or the other, and it is your call.

What to do

Open the Files changed tab above. On any line that reads translated rather than written:

1. Hover the line and click the blue +, then use the ± button in the comment box to write a suggestion. That puts your wording in as a proposed change, and it goes in with one click from here. This is the easiest way and needs nothing installed.
2. Or just comment with the correct sentence, if a suggestion block is fiddly on a long line.
3. Or, if you would rather work through whole files: fork the repo, edit sk.json and the sk: block, and open a pull request against this branch (sk-translation).

No rush, and no need to go through all 716 strings if only some read wrong — anything you leave uncommented I will take as acceptable. Nothing ships until you have had a look.

Thanks for starting this off.