WeblateOrg
Translatable and fixable blog
https://betaweb.weblate.org/en/news/archive/weblate-docker-container-changes/ contains some errors, (that are now hard to fix) and should be translatable. Possibly:
In case you are using it, you will probably →Those using it will have to adjust their setups.
For sure:
after upgrade → after upgrading it's → its the dash → should be an em dash (without spaces) or (better?) a semicolon should have from → should have had from
First of all I should be writing the posts without somebody reviewing them :-). Most of recent posts were written by @orangesunny and I believe those are better. This time I wanted something out fast and the errors are result from that. I've just applied your suggestions.
As for the translation, we're not really ready for that. Both technically (Weblate doesn't support translating database backed content) and process wise (we typically write announcements on last moment, what gives translators zero time to translate). But eventually we should get there.
:-) The sources could reside here, to be easily fixable.
Is it the integration back and forth or the format that is unsupported? In my head just the links need placeholders if it was markdown, and it seems that would work?
It's already written markdown. I'm not saying it's not possible to implement that, it's just some work that needs to be done and there are currently more important things to work on.
As this is actual again because of #5744, I declare that I will ask @comradekingu for help if I need it. Thanks.
Somehow I remembered making this, searched for it, and came up short. Short of translatable, fixable should be within reason anyhow. For as little effort as it takes, it certainly is a much improved look. @orangesunny https://github.com/comradekingu/posts/commit/594d32d1d1dc6bbaa67565d17a16928aa4d01749 are sensible changes to the first blogpost. Maybe you can get that in. Working on the second now.
Edit: blog 2 https://github.com/comradekingu/posts/commit/3ded5c409d4438c1a0225bdf5ceadc318757073c
@orangesunny comradekingu/posts@594d32d are sensible changes to the first blogpost. Maybe you can get that in. Working on the second now.
@comradekingu I will think about this one after I finish another work. But don’t send any other, we are not going to fix ancient blog posts. People hardly read them and wrong grammar or spelling is not a security issue, nor blocking someone’s work. It’s unneeded work.
Also, it shows how Weblate grows :)
@orangesunny
To quote, you
I will ask @comradekingu for help if I need it.
I am not sending any, it is my own repository. Presumably you could have fixed it in the time you took to contemplate whether to do so, and then formulating some sort of defence beyond that.
Weblate is where it is because of contributor effort. That is why you are where you are, discarding it.
Your reasoning is particularly weak. It can't be both that something is shown to much of anyone, if hardly anybody is reading it. Acknowledging something is broken, and then not fixing it, when other people do the work for you does what exactly?
If anyone is interested in the historical aspect, there is a whole archive in https://blog.cihar.com/archives/weblate/
To my knowledge you don't work on security issues. I got this idea from https://weblate.org/nb/about/
If you want to operate a profitable outfit, make sure it doesn't squander translations of, and language at large, for something that pertains to help other people fix theirs…
I did some much needed work, https://github.com/comradekingu/posts/commit/51df4ea632459a025be85f25b882a0a42faa8073
Which 3 blogposts do you think people are likely to read once they click themselves onto https://weblate.org/about/ ?