Hello. I would like to add a new language pack - Turkmen language pack. Could someone please tell me what is the difference in maintaining manually and via Weblate?
The Flarum Language Project
Kotosov I added Turkmen language to Weblate and created a repository for language pack:
https://weblate.rob006.net/languages/tk/flarum/
https://github.com/flarum-lang/turkmen
I can add you as maintainer (I need your Weblate and GitHub usernames), but you can translate without it through Weblate.
Kotosov I granted you maintainer permission on Weblate and GitHub (you need to accept invite on GitHub).
Kotosov Is there any guide about how to translate without Weblate? Thx
I'm not sure if there is a guide for that, since it is far less convenient than maintaining language pack through Weblate. But in general this is just composer package with YAML files, so you can edit these directly (please do not do this on https://github.com/flarum-lang/turkmen, since all your changes may be overwritten with state from Weblate).
Is there any reason you don't want to use Weblate?
- Edited
Hello @rob006 Can I have maintainer permissions for the Turkish lang? The updates for missing/improper translations are waiting for a while. Currently, there is only one maintainer ( @tolgaaaltas ) and he is performing his military duty. I can help to improve review/release progress. github&weblate: selmanozturk
- Edited
selmanozturk I have granted you maintainer permissions on GitHub, you should be able to tag new releases when you accept invite.
I haven't granted you any additional permissions on Weblate, as I would prefer to avoid granting extra privileges without @tolgaaaltas comment in this matter - I expect he would want to review new translations when he ends his military service, and another person marking translations as verified could make it harder. But but if you encounter any problems related to lack of permissions on Weblate, let me know - I can grant you maintainer permissions also on Weblate if it would make your work noticeable easier.
Kotosov Is there any specific feature/permissions missing that would require a maintainer role? Anyone can contribute translations, so if he wants to translate, maintainer role is not needed. I'd prefer the number of maintainers to be as small as possible, as usually it generates less conflicts and maintainer does not have much to do anyway.
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?
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.
- Edited
Hello! I'm making a forum for the toki pona community. toki pona is a constructed language of only around 120 words, and we have a very dedicated community. Because of this, we'd like to make a toki pona language pack for Flarum so we can enjoy our forum experience in our language. We have an ISO code under "tok" and toki pona should be supported with Weblate.
I am tech savvy enough for making a language pack myself, but I think most people who would be willing to contribute aren't, so it would be handy to have a Weblate category dedicated to us.
It would be greatly appreciated if you could give us this opportunity. Thank you!
My GitHub username is mazziechai
, and my Weblate is mazzie
.
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.
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.
joanaranda Translations do not need to be approved, they will be exported to language pack even without an approval, so this is not a blocker. But suggestions to existing translations are different story, they need to be approved by maintainer.
@pepoliveras can you take a look at https://weblate.rob006.net/translate/flarum/-/ca/?q=has:suggestion#suggestions . Do you have time to maintain this language pack? I could mark @joanaranda as new maintainer to push this project forward.