search

icabetong / fokus-android

Reminder app for tasks and events tailored specifically for students
MIT License
241 stars 24 forks source link

initializing fastlane structures #7

Closed IzzySoft closed 4 years ago

IzzySoft commented 4 years ago

Fastlane somehow got the standard for metadata of Android and iOS apps. It's used a.o. by F-Droid, by my repo – but also to deploy to Google Play. Thought to get you started with it, and hope you find this "minimal kit" useful.

You might wish to move other metadata into this structure as well, e.g. your screenshots from the art directory. For a quick guide, be welcome to use my cheat sheet.

IzzySoft commented 4 years ago

Thanks for merging! Should you move the screenshots in or add e.g. changelogs, please let me know so I tell my updater to fetch them as well.

7RST1 commented 4 years ago

Randomly noticed while checking language code for Norwegian; Shouldn't the German language code be de-DE instead, or doesn't it matter? Saw the code here. I know nothing about fastlane, just happen to notice the difference in language code.

IzzySoft commented 4 years ago

Shouldn't the German language code be de-DE instead

If it's specific to the German as spoken in Germany (as opposed to e.g. de-AT spoken in Austria), yes. But that would mean our Austrian fellows would fall back to en-US unless they explicitly specified they wanted to have de-DE. Usual browser setups for a German speaking user in Austria are rather "de-AT, de, en". Hence, as no language specific to any given region was used, only "de" is fine – and our Austrian friends could supply de-AT in addition if they feel like (similar to other de-*).

TL;DR: just using "de" makes it eligible for all German speaking countries. Specifying the region as well (de-DE) would not. "en-US" is a stupid exception as that's the fall-back for many tools (who ever made it that should be punished; "en" would have been much more sane).

Saw the code here

which is totally incomplete, if I might say so, and thus rather gives examples. What stands behind those codes is ISO-639 and ISO-3166-1 (see the alpha-2 code column there), also consult Language code (the second row in that table, "IETF language tag", sums it up). So basically, it's <language>[-<region>], with the region being optional.