Hello. I'm currently doing a translation for Flarum korean extension. I tried to use several translations by other guys but I think it's not enough, missing a lot and sometimes inaccurate. Yes I understand they have no time to correct it so I'm just started to create the best korean translations with our company's professional translation team since we are planning to use Flarum as a company official forum.

So what I want to ask is:
1) https://github.com/flarum/lang-english
Should we base on above link for the base or other?
2) What plugins are popular and useful? We have a plan to do them also.
3) If translation and cross checking are completed from our team, is it possible to apply as a Flarum's official language pack? Of course, we will constantly update it.

Thank you everyone. From Volistx Team's Translation Group.

      UndeadLime welcome to Flarum!

      1) The English language pack can definitely be used as an example and is the authoritative list of translation keys. Make sure you check the GitHub tags as the master branch will contain translations for future features and might be missing translations for features that will be removed in the next Flarum version.

      Copying another language pack is also a good starting point, just be respectful with the licensing/attribution if you decide to keep some already-translated strings or additional code/images that might be bundled in it.

      2) Extiverse is a good place to get a rough popularity sort based on downloads https://extiverse.com/?sort=-downloads Just keep in mind those are lifetime statistics, so there are some obsolete/abandoned extensions in there that might not see much use anymore. Some have also been forked into new packages.

      You could also take a look at which extensions do the other language packs translate. You can also look up on Extiverse which are the most downloaded language packs to get a starting point on that.

      3) While we did some experiments regarding managed translations in the past, I believe that's currently on hold. I'll let someone else from the team comment on that though.

          Thank you for your help. So if I add fof-custom-footer.yml to my translation based on eng, it will apply to that extension. Is that right?

            Thank you for your reply. Will ask in this thread if I have more questions 🙂

            4 days later

            UndeadLime language packs can include a config.js file that configures MomentJS for a different language, for example in the French pack https://github.com/qiaeru/lang-french/blob/master/locale/config.js

            Most of the time there's no need to write that file yourself, you can find it in MomentJS source code https://github.com/moment/moment/tree/develop/locale I haven't checked which version of MomentJS Flarum is using at the moment, maybe you need to use an older version of those files to match what Flarum is using.

                askvortsov beta 13 uses MomentJS, and I think it's what's relevant here.

                We'll include details on the move to DayJS in the developer guide for beta 14.

                  Actually, I checked Russian language pack and they even don't have any config.js. But that language pack works just fine. That's why I'm curious about it. If you have any idea for it, please let me know and for "flarum-locale" in composer.json, should I set "code" to "kr" or "ko"? Thank you.

                  https://github.com/marketplace-flarum/flarum-l10n-ext-russian

                  You can check my project here.
                  https://github.com/Cryental/flarum-l10n-ext-korean

                  If you want to test my package, you can run

                  composer require cryental/flarum-l10n-ext-korean --dev

                  No problem. I fixed that issue by adding config.js to locale folder. Thank you 🙂