Code Monkey home page Code Monkey logo

flarum-translations's Issues

Delete unnecessary branches and incompatible extensions

After rob006-software/flarum-translations-builder#10 and rob006-software/flarum-translations-builder#8 some extensions are no longer treated as valid.

Unnecessary (?) components:

  • manelizzard-notify
  • tituspijean-auth-ssowat - #244

Unnecessary branches:

Outdated extensions cleanup

This was announced at https://discuss.flarum.org/d/20807-simplify-translation-process-with-weblate/20. I will left this list for a week for review, then remove listed extensions from Weblate.

List of extensions to remove

Extensions incompatible with Flarum beta 14/15 (you can't install them the due to constraints in composer.json):

Old unsupported extensions (although you can install them with Flarum beta 14/15, they does not seems to be maintained and probably will not work):

I'm a language pack maintainer, how this affects me?

You won't be able to translate these extensions using Weblate anymore (assuming that you would want to). And that is it. The bot does not remove translations from the language pack, so if you translated some of these extensions already, translations will still be available in your language pack. If some of these extensions will be updated and added again, I will restore old translations, so you will not need to translate the same thing again (although you may need to mark translations as verified).

Switch CI from Travis to GitHub Actions

Travis still works because I have a pool of initial credits, but in long run we should migrate to GitHub Actions - Travis no longer support open source projects.

Weblate complains about translations - "Things to check" infobox

Title is very abstract, so let me describe details.

Trailing stop

When translate wny word or sentence, there are situations that using different "stop".

e.g.
image

How this can be solved or, should I force to use same "stop"?

Unchanged translation

you might know there are arrow translations like this:
image

Sometimes this is not correct. But there's way same word should be used.
How this can be solved or, should I force to translate them?

XML markup

Uhhh, sorry I don't know what's happening. Could you tell me which is incorrect?
image


Finally thank you for making the lots of translation in one place. This is kinda important to translating anything.

Consider disabling Travis cache

Right now travis builds are enabled only for PRs - only config changes are tested, so it does not make much sense to run tests on every push to master (most of them are translations data changes).

But because of the way how Travis cache works, every new PR starts with new cache, so cache is virtually useless for PRs with only one commit. It gives small boost for PRs on next commit, but this is quite rare situation here.

Consider removing branches tracking and sync translations only from last release

Since beta 12 there is English fallback for missing translations - translating unreleased version does no have much sense now. It is also a little confusing, since new phrases are fetched, but changed phrases are ignored, so you can't complete translation before release anyway.

Fallback does not work for official extensions (see flarum/framework#2020 (comment)), so we probably should track branches for them (at least for now).

Removing translation files of the-turk extensions from weblate

Turkish translation

We can support 2 people for the Turkish translation of the package. Where do we upload the translations? Can you explain?

What is the commit frequency?

After weblate submits the latest translation to this repository, how long does it take to synchronize to the language pack repository?

Based on past records, it seems to be within 10 minutes.

Spanish Language Pack

Hello! we are currently working on a new Spanish language pack (https://github.com/FlarumES/lang-spanish) for Flarum made by the verified community FlarumES.com.

I would like to add the repo but first I would like to say that we are working on different branches that can be selected from the extension, initially for Formal and Informal Spanish but in the future for other Spanish dialects (Mexican, Argentinian, Chilean...) is it possible to manage these branches from Weblate?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.