i18n - String improvement megathread

This issue is to keep track of strings which need improvements, please keep discussion on topic. It is not a place to request new languages to be added to the Crowdin project!

Mention the string ID
Why is it bad
What improvement(s) would make it easier to translate.

If you're here looking to translate Modrinth, you can do so here.

settings.display.theme.sync-across-devices.sign-in-tooltip (Sign into Modrinth to sync theme)
app.behavior-settings.sync-across-devices.signed-out-tooltip (Sign into a Modrinth account to sync settings.)

These strings are used in similar scenarios. I think they should be consistent:

use either into Modrinth or into a Modrinth account
end with . or not

The "Actions" column in the blocked users table should adapt to longer buttons (or use an icon instead of text)

I've used "Разблокировать" (a literal Russian translation of "Unblock") in this screenshot:

The spacing of the ads consent popup is broken.

In Serbian (Latin), texts generated by i18n functions use Cyrillic instead of Latin script.

All strings under app.settings.game-options.choice.* should have duplicates based on where they are used

Namely "All" and "None", but also others under the same subkey.

String ID: app.settings.game-options.choice.all

Issue: Need plural/gender support for the string "All" in French (i18n)

Description:
The standalone string "All" requires plural and gender agreement in French depending on what it refers to (e.g., "Tous" for masculine/mixed items vs. "Toutes" for feminine items).

Could this string be given additional context or split into specific keys based on where it is used so it can be localized accurately?

dashboard.creator-withdraw-modal.tremendous-details.search-category-placeholder should have an icu-select instead

I think the sidebar toggle should not be called "Next image"

Yeah that should be called "Open Sidebar"

Replace ALL strings having variables using strings with ICU-selects. Not having any, and limiting translators to NOT use any because they won't be accepted inside Modrinth, limit the translations greatly.

time-frame-picker.last-timeframe-prefix should give the translators the ability to change the order of the elements.
Something like this: In the last <amount></amount> <unit></unit>

installation-settings.linked-instance.title
for the languages that have the variable first, the first letter should be capitalized

files.create-modal.header, files.upload.drag-and-drop.drop-to-upload These strings should use an ICU tag

String ID: 7539

Why is it bad?

This string previously used an ICU select expression directly in the source, allowing translators to translate the entire sentence according to their language's grammar.

For example, the original format was similar to:

Search {projectType, select, ...}...

This made it possible to produce natural translations in languages such as Hungarian, where the word order differs from English (e.g. "Modok keresése..." instead of the literal "Keresés modok...").

The string has since been split into multiple translation entries (Search {projectType}... and separate strings for each project type). While this works well in English, it makes natural translations much harder—or impossible—for languages with different grammar or word order.

Additionally, using the original ICU select syntax in the translation no longer seems to work. The Modrinth website and app display the English text instead of rendering the translated ICU expression.

This approach worked correctly in the past. However, after the strings were split, translated ICU select expressions no longer appear to be processed correctly.

What improvement(s) would make it easier to translate?

Ideally, this string should remain as a single ICU MessageFormat string with a select expression, or another solution should be used that allows translators to control the entire sentence instead of assembling it from separate translated fragments.

This would improve localization not only for Hungarian, but also for other languages whose grammar or word order differs from English.

I used this format, but it didn't work:

{projectType, select, mod {Modok} forráscsomag {Forráscsomagok} adatcsomag {Adatcsomagok} shader {Shaderek} modcsomag {Modcsomagok} bővítmény {Bővítmények} szerver {Szerverek}} keresése...

forráscsomag = resource pack
adatcsomag = data pack
modcsomag = modpack
bővítmény = plugin
szerver = server

(better yet, make every string that is filled by another string an ICU select - or to just enable translators to make their own)

Navigation Menu

Repository navigation

i18n - String improvement megathread #5734

55 remaining items

Why is it bad?

What improvement(s) would make it easier to translate?

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

i18n - String improvement megathread #5734

Description

Activity

Andre601 commented on Apr 1, 2026

creeperkatze commented on Apr 1, 2026

Jerozgen commented on Apr 3, 2026

Laxan3000 commented on Apr 13, 2026

Daylight-MC commented on Apr 13, 2026

creeperkatze commented on Apr 13, 2026

creeperkatze commented on Apr 13, 2026

Andre601 commented on Apr 13, 2026

lumiscosity commented on Apr 26, 2026

Jerozgen commented on Apr 27, 2026

55 remaining items

Jerozgen commented on Aug 23, 2026

Jerozgen commented on Aug 23, 2026

creeperkatze commented on Sep 3, 2026

Cookai1205 commented on Sep 5, 2026

Cookai1205 commented on Sep 9, 2026

Laxan3000 commented on Sep 9, 2026

moi-le-chat commented on Sep 9, 2026

Laxan3000 commented on Sep 12, 2026

Ceebug commented on Sep 24, 2026

Laxan3000 commented on Sep 30, 2026

Laxan3000 commented on Sep 30, 2026

Laxan3000 commented on Oct 5, 2026

Laxan3000 commented on Oct 5, 2026

SzabAndris10 commented on Oct 13, 2026

Why is it bad?

What improvement(s) would make it easier to translate?

Laxan3000 commented on Oct 13, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions