Separate language pack for core and 3rd party extensions

rob006

Moving discussion from https://discuss.flarum.org/d/22802-italian-language-pack-extended/10

luceos this has become the de facto standard recently. Splitting translations for core and extensions is easier to manage overall. In addition there's a bug that loads all translations into flarum even for extensions that aren't enabled. Splitting translations up helps a little.

It does not help at all: core + official extensions lacks a lot of features, you need to install at least several 3rd party extensions to provide some essential features. Core-only installations ale probably super rare.
I'm also not sure how maintaining two extensions may be simpler than maintaining only one. There is no case when it will save you some work - you need to do release anyway, and with two extensions you may need to do 2 releases instead of one. I've even seen bugs because of this separation - "core" and "extensions" language packs have translations for the same extension (one of them was outdated) and outdated one overwritten current one.

From user perspective this is just ridiculous that you need to install 2 language packs for the same language to translate your forum. I really hope that we get rid of this convention after moving forward with flarum/core2020 and moving English translations from English language pack to respective extensions.

tolgaaaltas

rob006 From user perspective this is just ridiculous that you need to install 2 language packs for the same language to translate your forum.

Turkish users are happy with this.

luceos

rob006 I hope so too. I never expected the translators to come up with their own conventions even though they are disputable.

rob006

tolgaaaltas Turkish users are happy with this.

Yeah, right... Because users love unnecessary complexity... 😆

tolgaaaltas

rob006 Most Turkish users don't know English, and most of them use Google Translate. So, maybe they don't figured out what is that package. And at that time I hadn't released my Core Package.

rob006 A little missed mistake.

rob006

I've even seen bugs because of this separation - "core" and "extensions" language packs have translations for the same extension (one of them was outdated) and outdated one overwritten current one.

BTW: @tolgaaaltas I was taking about your extensions here:
https://github.com/tolgaaaltas/flarum-lang-turkish/blob/0.11.2/locale/spamblock.yml
https://github.com/tolgaaaltas/flarum-ext-turkish/blob/0.1.58/locale/fof-spamblock.yml

rob006

tolgaaaltas Most Turkish users don't know English, and most of them use Google Translate. So, maybe they don't figured out what is that package.

They would not need to figure out this if there was one complete language pack. Installing two language packs in counterintuitive.

tolgaaaltas A little missed mistake.

It wouldn't exist if there was one complete package. This separation is just unnecessary complexity that affect both users and maintainers.

tolgaaaltas

rob006 Maybe they just need to read what's written to understand. It's not too hard.

rob006 It wouldn't exist if there was one complete package. This separation is just unnecessary complexity that affect both users and maintainers.

This is your opinion. As I said, a little mistake. It's not a big mistake.

I separated these packages because if there is an official language pack, I only have to abandon it the current core package.

tolgaaaltas

rob006 unnecessary

I separated because i want it. Is this ok for you? If this way too complex for them, they can use another Turkish language package.

rob006

tolgaaaltas Maybe they just need to read what's written to understand. It's not too hard.

You're talking like a bureaucrat. The goal should be creating good user experience for Flarum users. Unnecessary rules and twisted conventions will not help with that.

rob006

tolgaaaltas This is the exact attitude I was talking about...

No one will forbid you to create hundreds of separate language packs (separate for each extension), same as no one will forbid me to have a strong opinion about this. It is unnecessary complexity that hurts UX.

tolgaaaltas

rob006 It is unnecessary complexity that hurts UX.

This is your opinion and i don't agree.

askvortsov

Is there anything that's stopping 3rd party language pack devs from including core in their main pack?

Also, I would be in favor of moving the bundled extension english translations to the extensions themselves for improved maintenance and as that's the convention for all extensions in general.