The Flarum Language Project

rob006 I guess it would make sense to put things in writing. I also don't believe a multitude of maintainers are required, although I can imagine a maintainer and co-maintainer to be helpful for each language. I also think the maintainer needs to agree on the choice of co-maintainer. We can then promote the co-maintainer to maintainer in case the maintainer has become unresponsive for a while.

What are your opinions?

rob006 I understand the risks of having lots of maintainers. In my case, I would like him to have the ability to approve translated strings, so he could back me up if I won't be able to work on the project.

Kotosov In my case, I would like him to have the ability to approve translated strings, so he could back me up if I won't be able to work on the project.

You don't really need mark translations as approved - unapproved translations are also exported to language pack and can be used right away by installing dev-master version (or when maintainer releases new version). Technically language pack can function without maintainer and with community contributions only. The main responsibility of maintainer is to review contributions to keep them consistent, and it is actually harder to do this if you have multiple people responsible for this.
If you still insist, I'll grant him maintainer permissions. But I feel that this request comes from misconception that you need to be maintainer to translate (he doesn't have any translations so far: https://weblate.rob006.net/user/LateNever/).

luceos What would be difference between co-maintainer and maintainer in terms of permissions?

Personally I think that it would be more efficient to react ad hoc on maintainer inactivity (we just did that for Turkish language pack), instead of adding "backup maintainer" that may loose interest in project before he will be needed. We already have some language packs with multiple maintainers, and most of them looks like maintained by single active maintainer anyway.

rob006 I guess that makes sense. It would be helpful to have people actually actively contribute on weblate, so that we have candidates to take over (or be suggested as) the active maintainer should the current one be unavailable.

mazzie the level of geekness is just amazing; I think this is a great idea

mazzie I created repository for language pack and added support for this language in Weblate:

https://weblate.rob006.net/languages/tok/flarum/
https://github.com/flarum-lang/toki-pona

You should also have maintainer permissions (you need to accept invite in GitHub). It may take a while until language pack will be available in Packagist, so you won't be able to install it right now, but you can already start translating.

rob006 Thank you!

I've just recently started to contribute to the catalan translation since I've seen that only a small number of strings were translated so far. I already signed up with weblate, translated my first strings and today I've seen that some of my stuff seems to be available already in github, which is great news. Is there any additional step that I need to make or any further information that I need to know before digging even more into this initiative?

I've finished the translation of the core to Catalan... but I am alone in that project, so I am stuck as all the stuff that I translated is not approved, but pending review... from nobody I guess! Similarly, I have also suggested some changes for a few old translations, but I don't think that there is anybody on the other side to accept or reject them. I'm eager to start with the translation of the extensions but, first of all, I think I it worthwhile to have a complete approved and functional translation of the core.

Hello, I apologize for being a bit disconnected due to personal and work reasons, but I believe I can now catch up! Thanks for the heads up @rob006 ! @joanaranda , thank you for your contributions! I'm delighted to receive help and collaborate together. As you might have noticed, over 90% of the core application's translation to Catalan was already done – I did that myself. I still needed to work on the extensions, so if you want to take that on, that would be great. I also found it a bit challenging to understand the workings of Weblate and the Git repository at first In any case, I simply wanted to contribute my part to the community, as this is a 100% community-driven, open-source project. Thk's a lot! Moltes gràcies Joan qualsevol cosa parlenne! ^_^

Hi @pepoliveras! Glad to know that you are still onboard. I saw that your last commits in Flarum's github at https://github.com/pepoliveras?tab=overview were dated in February, so I assumed you had abandoned the project. Sure, let's collaborate and make a significant boost!

Mmm... What is concerning me is what you said that you already translated 90% of the core. The figures that appeared to me when I joined the project is that the percentage was below 50%. No intention to discuss your numbers but I fear there may have been some overlap and that we may be overwritting translations each other. In weblate, your statistics say you have been built 401 translations (https://weblate.rob006.net/user/pepoliveras/) and I did 439 (https://weblate.rob006.net/user/joanaranda/). Not sure, maybe you were doing something directly in github while all what I have done has been through weblate. We should clarify this before investing more long hours on this, as we should avoid wasting effort. But certainly, I'd like that we close some pending suggestions and style refinements in the core and start working together in the extensions. What's the best way we can interact and agree on next steps?

By the way, thank you @rob006 to warn me about the possibility that @pepoliveras was still onboard!

Hi @joanaranda, initially, I started working directly on GitHub, but then I fully understood that the system, as it's implemented, automatically updates through Weblate. So, it's sufficient to work directly from there. Regarding the numbers, okay, I don't want to create any disputes – I probably wasn't accurate enough, as I don't recall the exact percentage, apologies. However, I can say that I had advanced significantly with the core application's translation and was concurrently working on the plugins that I use.

The plugins I'm currently translating are as follows:
FoF Ban IPs
FoF Best Answer
FoF Default Group
FoF Default User Preferences
FoF Filter
FoF Gamification
FoF Impersonate
FoF Masquerade
FoF Merge Discussions
FoF Night Mode
FoF Polls
FoF Pretty Mail
FoF Reactions
FoF Split
FoF Terms
FoF Upload
FoF User Bio
FoF User Directory
FoF reCAPTCHA
Author Change
Auto Moderator

Please feel free to proceed with any of these or others if you prefer.

Regarding translation criteria, I've tried to adhere to the recommendations from IEC. The only matter that seems potentially open to interpretation, I believe, would be the use of the second person in singular or plural form. For my part, I've aimed for a more formal translation, using "vostre" (your - formal) instead of "teu" (your - informal). But from here, we can agree on what might be more suitable.

Thank you for everything! Seguim!

Hi, @pepoliveras

Oh, no. There is not going to be any dispute for sure. My only fear when I read your numbers was the risk that I might be overwritting through weblate most of the stuff that you might have been creating from github. No intention at all to discuss who has been contributing the most. Let me check which are the extensions that I am more interested about, which are the ones that I am already incorporating into the forum that I am building. If there is overlap, we can help each other. And otherwise, we can progress faster with the double of plugins. Regarding the formal/informal tone, you are absolutely right! I tried to potentiate the informal tone because I would like to target a younger population and also because I think that an informal athmosphere potentiates the interactions. But I think that the most effective thing is that we talk directly and clarify the details. My email address is my username adding gmail.com if you want that we start some direct conversations (I am writing it this way to avoid robots stealing my email). If you don't mind, let's agree on a common available timeslot and let's have a short call or video meeting and let's deep dive into the details.

Som-hi!

@pepoliveras @joanaranda We have a solution for formal vs informal form in language pack, and it is already used by German and Spanish language packs: language pack contains 2 sets of translations (formal and informal) and forum admin may choose which set he want to use in extension settings. On Weblate we have translations separated into two languages (informal as a base and formal as an additional variant): informal is exported as informal, and formal is generated from informal translations overwritten by formal translations - in that way for formal translation you only need to translate phrases that differs from informal variant.

So you don't need to choose formal vs informal, you can have both.

Hi @rob006. Thank you for raising it. Tomorrow @pepoliveras and I will met and discuss how we want to cooperate from now on. What you are proposing really is a very valid solution, although we may prefer to focus the energy in translating many of the pending extensions, instead of prioritizing to keep two different versions of the core. In any case, this is just a guess. Let's see tomorrow. What you are proposing certainly is a very relevant topic to discuss.

@rob006, for your info, @pepoliveras and I already met and we think we are fully aligned. Let's go for it and let's have a fully solid catalan version of Flarum asap!

Hello @rob006 . My friend was working on Turkmen Language Pack for FOF Upload recently and now we got an error "The translation is temporarily closed for contributions due to maintenance, please come back later. The translation was automatically locked due to following alerts: Could not merge the repository." I've read the faq on weblate, but didn't understand it fully. Could you, please, help me resolve the issue? )

Kotosov
I believe there might be a small issue at the moment, and I am unable to maintain the translation either. However, I believe it will be resolved soon.