The Flarum Language Project

comseong

Justoverclock How can I let the Uzbekistan Flag show in the administration panel when I will enable it?

Justoverclock

comseong you need to modify this
https://github.com/flarum-lang/uzbek/blob/master/composer.json#L32

simply place an icon.svg file in the root 🙂

i will do this for you if you want

comseong

Justoverclock I saw you placed the icon.svg Thanks. I committed some info to composer.json. Pls review and merge it!

comseong

Justoverclock I saw you uploaded some files and made a new release, v0.1.1. But when I tried to update by Composer, it said "Nothing to install, update or remove". When can I use the new release by Composer?

And right now I approved 100% translation of many extensions including "fof-upload" and committed and pushed in Weblate. I want to see the new version of "fof-upload" which is applied by Uzbek translation asap. Thanks.

datlechin

comseong I saw in Packagist the Uzbek language pack has not been updated to the latest version.

Justoverclock

datlechin odd, auto update is enabled, but now is ok

comseong

Justoverclock Right, now it's ok. By the way, when will what is pushed in Weblate be merged to the github repository? Because it's not merged yet since I pushed it in Weblate yesterday. And when will a new release from github to be merged be released? Is not an automatic process? If not, how many period do you have for merge to release?

Justoverclock

comseong when you translate on weblate, the bot will automatically push your translations to GitHub after 1 hour, after than you need to go on GitHub and tag a new release. That’s all 🙂

comseong

Justoverclock My understanding was same as you mentioned. But the automatic push was not worked over 10 hours by a bot since I had pushed the translations in Weblate. Now I saw this commit msg, "Sync translations with main repository. robbot006 and camalow committed 3 hours ago". Was this a manual push? Additionally, I have no permission to tag and release a version in the repository. Pls give me a permission. Thanks.

Justoverclock

comseong @rob006 can u check?

rob006

comseong My understanding was same as you mentioned. But the automatic push was not worked over 10 hours by a bot since I had pushed the translations in Weblate.

Can you point which translation was not pushed automatically? I compared Weblate activity log and commits log and it seems to be fine.

Note that translations are exported to language pack regardless of translations status - marking translation as approved will not affect language pack.

Also, if you want to test your language pack, you probably should install it using composer require flarum-lang/uzbek:dev-master - in that way you could test it before tagging new release.

comseong

rob006 Yesterday I approved translations and also committed and pushed at the same time in the menu of Repository maintenance of Manage in Weblate. But as @Justoverclock mentioned it, the translation was not to merged to the github repo after 1 hour. If I have misunderstanding, pls let me know. And who's responsible for tagging and releasing the new version? When will the new version be released periodically? Thanks.

comseong

rob006 Now I compared Weblate activity log and commits log. Even over 1 hour after committing in Weblate have passed, the commit is not committed to main repo. Could you let me know if it's normal or not?

comseong

rob006 Thank you for you help. I met another issue. I installed the lang package with dev-master for a test it before tagging new release. But when I installed, why the commit(dev-master 473ff5e) of the package points to the 6th commit after the latest commit(dev-master 3d5c93), not the latest one?

Package operations: 1 install, 0 updates, 0 removals

Installing flarum-lang/uzbek (dev-master 473ff5e): Extracting archive

And I think the Update command doesn't work also. Even though more newer commits in repo exist, when I tried to update the dev-master by this command, Composer update flarum-lang/uzbek, it doesn't work.

Justoverclock

comseong you are responsible to tag a new version, yesterday i've tagged a new release for you, but this is up to you

comseong

Justoverclock I don't have a permission to make a release in github repo. Pls give me the permission.

Justoverclock

comseong what is your username on github?

you need to accept the invite

comseong

Justoverclock Thanks I got the permission!

rob006

comseong You need to be more specific. Which phrase is translated on Weblate but not available on https://github.com/flarum-lang/uzbek ?

comseong

Right, the repo. Because of the difference btw the committed time on the Weblate activity log and the committed time on commits log in repo, I thought the translation will not be applied to the repo. But it was not.

Note that translations are exported to language pack regardless of translations status - marking translation as approved will not affect language pack.
=> It means I need not approve a translation of my team members any more? Whenever they translate it, it'll be committed to the repo automatically??

rob006

comseong => It means I need not approve a translation of my team members any more? Whenever they translate it, it'll be committed to the repo automatically??

You don't need to approve translations. Bu this is useful as review tool - anyone can translate on Weblate and contributions may use different styles and have different quality. It is usually a good thing to review all new translations by one person - with "approved" status you can easily find translations that has not been reviewed yet, and fix them (and then tag new release, so users using stable releases will always have verified translations). But if your marking translations as approved without even checking them, then this is pretty much pointless.

Also, I recommend to read https://github.com/rob006-software/flarum-translations/wiki/How-to-start#whats-next

« Previous Page Next Page »