Skip to content
40 changes: 20 additions & 20 deletions ghost/i18n/locales/hr/comments.json
Original file line number Diff line number Diff line change
Expand Up @@ -8,52 +8,52 @@
"Add comment": "Dodaj komentar",
"Add context to your comment, share your name and expertise to foster a healthy discussion.": "Dajte kontekts vašem komentaru, podijelite vaše ime i znanje za unaprijeđenje svake rasprave.",
"Add reply": "Dodaj odgovor",
"Add your expertise": "",
"Add your expertise": "Dodaj svoje područje stručnosti",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 AI: I think there is a typo in "Dajte kontekts vašem komentaru" in the value for "Add context to your comment, share your name and expertise to foster a healthy discussion.": should "kontekts" perhaps be "kontekst"?

"Already a member?": "Već si član?",
"Anonymous": "Anonimus",
"Are you sure?": "",
"Are you sure?": "Jesi li siguran?",
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Feb 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

"Jesi li siguran?" uses masculine singular — consider a gender-inclusive form.

As the PR author noted, informal Croatian defaults to the masculine form when gender is unknown. "Jesi li siguran?" will appear to address only male readers. A formal plural is grammatically gender-neutral: "Jeste li sigurni?", though it shifts the register from informal to formal.

Since the PR raises the open tone question, it's worth settling this before merging — the gender inconsistency is directly observable here.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@ghost/i18n/locales/hr/comments.json` at line 14, The Croatian translation for
the key "Are you sure?" currently uses the masculine singular "Jesi li
siguran?"; replace that value with the gender-neutral/formal plural "Jeste li
sigurni?" (i.e., change the string value for "Are you sure?" from "Jesi li
siguran?" to "Jeste li sigurni?") and ensure this choice matches the locale's
overall tone.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As mentioned earlier, Croatian is highly gendered. I would keep this as-is for now because it matches the rest of the file. ‘Već si član?’, ‘Postani član’, ‘Osnivač’, ‘Voditelj’, and ‘Neurokirurg’ all use the default masculine form, and most of the file uses an informal tone, with a few inconsistencies.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pleibner, that makes perfect sense — maintaining consistency within the file is the right call for now. I appreciate you pointing out those other masculine forms throughout; a piecemeal change here would indeed introduce inconsistency. Looking forward to the comprehensive tone/formality cleanup in your planned follow-up PR! 👍


✏️ Learnings added
Learnt from: pleibner
Repo: TryGhost/Ghost PR: 26531
File: ghost/i18n/locales/hr/comments.json:14-14
Timestamp: 2026-02-22T17:47:26.893Z
Learning: In Croatian translations for Ghost (ghost/i18n/locales/hr/), maintain consistency with the existing tone and gendered forms within each file. The project currently uses masculine forms by default for gender-neutral contexts (e.g., "Jesi li siguran?", "Već si član?", "Postani član"). Tone and formality inconsistencies should be addressed comprehensively across files rather than in individual changes.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

"Become a member of {publication} to start commenting.": "Postani član {publication} za mogućnost komentiranja.",
"Become a paid member of {publication} to start commenting.": "Plati pretplatu na {publication} za mogućnost komentiranja.",
"Best": "",
"Best": "Prvo najbolji",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 AI: For the sort label "Best" you have "Prvo najbolji". I suspect something like "Najbolji" or "Najbolje ocijenjeni" would be clearer and more idiomatic, and would still work well as a dropdown option. What do you think?

"Cancel": "Prekini",
"Comment": "Komentar",
"Commenting disabled": "",
"Commenting disabled": "Komentiranje onemogućeno",
"Complete your profile": "Dovrši svoj profil",
"Contact support": "",
"Contact support": "Kontaktiraj podršku",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 AI: For "Contact support" you used "Kontaktiraj podršku" (informal), whereas many other strings in hr (e.g. in portal.json) use formal forms ("Kontaktirajte podršku", "Molimo vas…"). Would you like to align this to the same formality level across files?

"Delete": "Obriši",
"Deleted": "",
"Deleted": "Obrisano",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 AI: Similarly, for "Delete" / "Obriši" and other commands here you tend to use informal singular, while in portal/ghost many CTAs are formal plural. Do you want to standardise on one form (formal or informal) across the Croatian UI?

"Deleted member": "Obrisan član",
"Deleting": "",
"Deleting": "Brisanje u tijeku",
"Discussion": "Rasprava",
"Edit": "Uredi",
"Edit this comment": "Uredi ovaj komentar",
"edited": "uređen",
"Enter your name": "Unesite vaše ime",
"Expertise": "Stručnost",
"for more information.": "",
"for more information.": "za više informacija.",
"Founder @ Acme Inc": "Osnivač Acme Inc",
"Full-time parent": "Full-time Roditelj",
"Head of Marketing at Acme, Inc": "Voditelj marketinga Acme, Inc",
"Hidden for members": "",
"Hidden for members": "Skriveno za članove",
"Hide": "Sakrij",
"Hide comment": "Sakrij komentar",
"Jamie Larson": "Jamie Larson",
"Join the discussion": "Pridruži se raspravi",
"Just now": "Upravo sada",
"Load more ({amount})": "",
"Load more ({amount})": "Učitaj još ({amount})",
"Local resident": "Lokalni stanovnik",
"Member discussion": "Rasprava članova",
"Name": "Ime",
"Neurosurgeon": "Neurokirurg",
"Newest": "",
"Oldest": "",
"Once deleted, this comment can’t be recovered.": "",
"Newest": "Prvo najnoviji",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 AI: Similarly to "Best", for "Newest" translated as "Prvo najnoviji", would a simpler "Najnoviji" (or "Najnovije") work better as the sort option label?

"Oldest": "Prvo najstariji",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 AI: For "Oldest" translated as "Prvo najstariji", do you think just "Najstariji" would feel more natural as a sorting label, parallel to "Najnoviji"?

"Once deleted, this comment can’t be recovered.": "Jednom kad se obriše, ovaj komentar se ne može vratiti.",
"One hour ago": "Prije jednog sata",
"One min ago": "Prije jedne minute",
"removed": "",
"Replied to": "",
"removed": "uklonjeno",
"Replied to": "Odgovor na",
"Reply": "Odgovori",
"Reply to": "",
"Reply to": "Odgovor na",
"Reply to comment": "Odgovori na komentar",
"Report": "Prijavi",
"Report comment": "Prijavi komentar",
Expand All @@ -67,14 +67,14 @@
"Show comment": "Prikaži komentar",
"Sign in": "Prijava",
"Sign up now": "Registriraj se sada",
"Sort by": "",
"Sort by": "Sortiranje",
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Feb 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

"Sort by""Sortiranje" drops the relational "by".

"Sortiranje" means sorting (a noun/gerund), while the source string is a label meaning "Sort by [criterion]". A closer rendering would be "Sortiraj po" or "Razvrstaj po".

🌐 Suggested fix
-    "Sort by": "Sortiranje",
+    "Sort by": "Sortiraj po",
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"Sort by": "Sortiranje",
"Sort by": "Sortiraj po",
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@ghost/i18n/locales/hr/comments.json` at line 70, The translation for the JSON
key "Sort by" is currently "Sortiranje" which removes the relational "by";
update the value for the "Sort by" key to a phrase that preserves the "by"
relationship such as "Sortiraj po" or "Razvrstaj po" so the label reads
correctly as "Sort by [criterion]".

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is intentional, considering how this dropdown label would read with the dropdown options (best, newest, oldest). Since the options are not distinctive categories, like “price,” using a noun here is more appropriate.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pleibner, thank you for the clarification! That makes sense—using the noun form "Sortiranje" as a standalone label is more natural when the dropdown options themselves complete the meaning. I appreciate the context about how it reads with the options.

🐰💭
(_(\
(='.'=)
(")_(")


✏️ Learnings added
Learnt from: pleibner
Repo: TryGhost/Ghost PR: 26531
File: ghost/i18n/locales/hr/comments.json:70-70
Timestamp: 2026-02-22T16:26:49.641Z
Learning: In Croatian translations for Ghost, when translating "Sort by" labels for dropdowns where the options are adjectives (like "best", "newest", "oldest") rather than distinct categories, using the noun form "Sortiranje" is preferred over the verb phrase "Sortiraj po" because it reads more naturally with the dropdown options.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

"Start the conversation": "Pokreni razgovor",
"The linked comment is no longer available.": "",
"The linked comment is no longer available.": "Povezani komentar više nije dostupan.",
"This comment has been hidden.": "Ovaj komentar je skriven",
"This comment has been removed.": "Ovaj komentar je maknut",
"Upgrade now": "Nadogradite sada",
"View in admin": "",
"View in admin": "Pogledaj u admin sučelju",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 AI: For "View in admin" you used "Pogledaj u admin sučelju" with informal imperative. If the overall tone for Croatian is intended to be formal (as it seems in portal.json), perhaps "Pogledajte u administratorskom sučelju" would be more consistent?

"Yesterday": "Jučer",
"You can't post comments in this publication.": "",
"You can't post comments in this publication.": "Ne možeš komentirati na ovoj stranici.",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 AI: In "Your request will be sent to the owner of this site.", the translation "Vaš zahtjev će se poslati vasniku ovih web stranica." seems to contain a typo: is "vasniku" meant to be "vlasniku"?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 AI: Also, "ovih web stranica" is grammatically fine, but Ghost tends to refer to a single site; would "ove web stranice" or simply "ove stranice" fit the product context better, in your opinion?

"Your request will be sent to the owner of this site.": "Vaš zahtjev će se poslati vasniku ovih web stranica."
}
30 changes: 15 additions & 15 deletions ghost/i18n/locales/hr/ghost.json
Original file line number Diff line number Diff line change
Expand Up @@ -26,50 +26,50 @@
"Keep reading": "Nastavi čitati",
"Less like this": "Manje ovakvih",
"Manage subscription": "Upravljaj pretplatom",
"Manage your preferences": "",
"Manage your preferences": "Upravljajte svojim postavkama",
"Member since": "Član od",
"More like this": "Više ovakvih",
"Name": "Ime",
"New comment on {postTitle}": "",
"New reply to your comment on {siteTitle}": "",
"Or use this link to securely sign in": "",
"Or, skip the code and sign in directly": "",
"New comment on {postTitle}": "Novi komentar na {postTitle}",
"New reply to your comment on {siteTitle}": "Novi odgovor na vaš komentar na {siteTitle}",
"Or use this link to securely sign in": "Ili koristite ovaj link za sigurnu prijavu",
"Or, skip the code and sign in directly": "Ili preskočite kod i prijavite se direktno",
"paid": "plaćeno",
"Please confirm your email address with this link:": "Molimo vas da potvrdite adresu e-pošte klikom na ovaj link:",
"Secure sign in link for {siteTitle}": "Sigurni link za prijavu na {siteTitle}",
"See you soon!": "Vidimo se uskoro!",
"Sent to {email}": "Poslano na {email}",
"Sign in": "Prijava",
"Sign in now": "",
"Sign in now": "Prijavite se sada",
"Sign in to {siteTitle}": "Prijava na {siteTitle}",
"Sign in to {siteTitle} with code {otc}": "",
"Sign in to {siteTitle} with code {otc}": "Prijavite se na {siteTitle} s kodom {otc}",
"Sign in verification": "Verifikacija prijave",
"Someone just replied to your comment": "",
"Someone just replied to your comment on {postTitle}.": "",
"Someone just replied to your comment": "Netko je upravo odgovorio na vaš komentar",
"Someone just replied to your comment on {postTitle}.": "Netko je upravo odgovorio na vaš komentar na {postTitle}.",
"Subscription details": "Detalji pretplate",
"Tap the link below to complete the signup process for {siteTitle}, and be automatically signed in:": "Završite registraciju na {siteTitle} klikom na ovaj link i automatski se prijavite:",
"Thank you for signing up to {siteTitle}!": "Hvala vam na registraciji na {siteTitle}!",
"Thank you for subscribing to {siteTitle}!": "Hvala vam na pretplati na {siteTitle}!",
"Thank you for subscribing to {siteTitle}.": "Hvala vam na pretplati na {siteTitle}.",
"Thank you for subscribing to {siteTitle}. Tap the link below to be automatically signed in:": "Hvala vam na pretplati na {siteTitle}. Prijavite se klikom na ovaj link:",
"This email address will not be used.": "Ova adresa e-pošte neće biti korištena.",
"This message was sent from {siteDomain} to {email}.": "",
"This message was sent from {siteDomain} to {email}.": "Ova poruka je poslana s {siteDomain} na {email}.",
"trialing": "probni period",
"Unsubscribe": "Otkaži pretplatu",
"Unsubscribe from comment reply notifications": "",
"Unsubscribe from comment reply notifications": "Odjavite se od obavijesti o odgovorima na komentare",
"Upgrade": "Nadogradi",
"Upgrade to continue reading.": "Nadogradite pretplatu kako biste nastavili sa čitanjem.",
"View comments": "",
"View comments": "Pogledajte komentare",
"View in browser": "Pogledaj u pretraživaču",
"Welcome back to {siteTitle}!": "Dobro došli na {siteTitle}!",
"Welcome back to {siteTitle}! Your verification code is {otc}.": "",
"Welcome back! Here's your code to sign in to {siteTitle}": "",
"Welcome back to {siteTitle}! Your verification code is {otc}.": "Dobro došli natrag na {siteTitle}! Vaš verifikacijski kod je {otc}.",
"Welcome back! Here's your code to sign in to {siteTitle}": "Dobro došli natrag! Ovo je vaš kod za prijavu na {siteTitle}",
"Welcome back! Use this link to securely sign in to your {siteTitle} account:": "Dobro došli! Prijavite se na {siteTitle} klikom na ovaj link:",
"When:": "Kada:",
"Where:": "Gdje:",
"You are receiving this because you are a <strong>%%{status}%% subscriber</strong> to {site}.": "Primili ste ovu poruku jer ste <strong>%%{status}%% pretplatnik</strong> na {site}.",
"You can also copy & paste this URL into your browser:": "Uvijek možete kopirati ovaj URL i otvoriti ga u vašem pregledniku:",
"You can unsubscribe from these notifications at {profileUrl}.": "",
"You can unsubscribe from these notifications at {profileUrl}.": "Možete se odjaviti od ovih obavijesti na {profileUrl}.",
"You just tried to access your account from a new device.": "Upravo ste pokušali pristupiti svom računu sa novog uređaja.",
"You will not be signed up, and no account will be created for you.": "Nećete biti registrirani i vaš račun neće biti kreiran.",
"You will not be subscribed.": "Nećete biti pretplaćeni.",
Expand Down
Loading