Update Croatian translation

[milotype]

• Update Croatian translation with current .pot file
• Some minor changes in already translated strings

[RayBB]

@milotype could you share the exact command you used to generate the initial changes (before adding your translations)?

I’m asking because the diff is quite large, and when I run the commands from https://docs.openlibrary.org/1_Everyone/Internationalization.html, I get a different result.

That said, I’m not very familiar with our i18n setup, so it’s possible I’m doing something incorrectly.

When I run:

docker compose run --rm web ./scripts/i18n-messages update hr

I see a ~1000-line diff.

One thing that stands out is at the top of the diff:
it changes from "Generated-By: Babel 2.7.0\n" to "Generated-By: Babel 2.12.1\n".

I’m wondering if the Babel version difference could be affecting the generated output.

[milotype]

@RayBB Hi, yes I also see that the huge number of diffs. But I doubt that the Generated-By: Babel X.X.X is a problem. As you can see in the diffs, the item Generated-By: Babel 2.7.0 didn't change between my last and my current .po file.

I'm not a programmer, but maybe Babel is used to generate the .pot file itself. Looking back in my history of my translation files, in both .po and .pot files, this item has allways been there.

These are the headers from my translation back in 2020.

Header of my Croatian .po file:
msgid "" msgstr "" "Project-Id-Version: Open Library VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" "POT-Creation-Date: 2020-03-15 22:35-0400\n" "PO-Revision-Date: 2020-11-15 13:43+0100\n" "Language-Team: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 2.7.0\n" "X-Generator: Poedit 2.4.2\n" "Last-Translator: Milo Ivir <mail@milotype.de>\n" "Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n" "%10<=4 && (n%100<12 || n%100>14) ? 1 : 2);\n" "Language: hr\n"

Header of the original .pot file:
msgid "" msgstr "" "Project-Id-Version: Open Library VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" "POT-Creation-Date: 2020-03-15 22:35-0400\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 2.7.0\n"

Generally my workflow is as follows:

1. I download the current Croatian .po file
2. I download the current .pot file
3. I open the current Croatian .po file with the app Poedit
4. I update the .po file with the .pot file
5. I update old strings and translate new strings
6. I add only the year of my edits in the beggining of the .po file, for instance:

Croatian translation for Open Library. Hrvatski prijevod za Open Library.
Copyright (C) 2020 Internet Archive
This file is distributed under the same license as the Open Library project.
Translators:
Milo Ivir <mail@milotype.de>, 2020., 2022., 2023., 2025., 2026.

It seems to me that most of the reason of the huge number of diffs is that a huge number of keys of the former and current .pot files have been changed.

[RayBB]

Thanks for explaining! I think we'll be tuning this process soon to make it easier with smaller diffs. Appreciate your contributions 👍

[tfmorris]

Since this has already been merged, I guess it's too late for review feedback, but for future updates like this, I would suggest using multiple commits to separate mechanical updates from actual translation changes.

It seems to me that most of the reason of the huge number of diffs is that a huge number of keys of the former and current .pot files have been changed.

Actually I don't think the keys changed so much as the entire file was reordered by this commit beb87d8 . It might have made sense to update all the .po files at the same time that the .pot file was completely reordered, but I don't know if it makes sense now.

[RayBB]

@tfmorris that's great feedback and good eye connecting it to that commit.

Would love your input on what workflow you think would make the most sense for this change Mek is proposing.

#11835