Retrosprings legacy locales file is down to 37 lines (from 400+)

so I'm probably able to finish getting rid of those and localizing the few hardcoded things that are left

it took so long :blobcatsadreach:

People that work on (web) apps:

Do your translations properly the first time, if you mess them up it will take years to refactor stuff how does one do translations/localisations in the first place? :akko_woozy:

@amolith I in general mean the system of preparing for localization/translation.

the biggest, biggest thing needs to be that you need to mind eastern languages and their word order

a lot of projects to something like

[translation string 1] {{ variable }} [translation string 2]

which, if you are english speaking, fixes the word order for other languages and so either it ends up being completely impossible or they need to form really weird sentences to get somewhat close

@amolith so, people need to get familiar with their translation systems that their frameworks offer, like passing variables into localization strings etc. pp.


@amolith another thing that can be overlooked is counts of stuff and pluralization.

Some frameworks offer text handling and you can just pluralize a string, but they don't work with non-english languages at times

so doing "{count} pluralize("word", count)"

would get you "1 word, 2 words" etc. but will it get you "2 語s" in other languages

when I did the initial translations for Retrospring in 2015 all these mistakes summed up and made translating for Japanese people quite the pain.

Sign in to participate in the conversation

Welcome to, pixeldesu's personal Mastodon instance!