<re_irc>
<@adamgreig:matrix.org> the wg repo now has bors removed, but also the dummy workflow from before, and PRs can just be merged as required; we tested it with the GHMQ and that also seems to work fine (but isn't really required for the wg repo)
<re_irc>
<@therealprof:matrix.org> Ah. Probably need to revise the checklist instructions for new repos then.
<re_irc>
<@romancardenas:matrix.org> : This PR should work withboth ghmq and bors
<re_irc>
<@almindor:matrix.org> i think the riscv PR for GHMQ looks good, happy to merge
<re_irc>
<@therealprof:matrix.org> Is there a howto somewhere describing how to switch from bors to GHMQ in a straight forward way?
<re_irc>
<@adamgreig:matrix.org> not yet - I think we still want to work out exactly what that looks like
<re_irc>
<@adamgreig:matrix.org> yea, there's really very little to it - delete bors.toml, tick "require merge queue" in repo settings, and finally make sure relevant workflows are triggered on merge queue commits
<re_irc>
<@adamgreig:matrix.org> that last part is the only fiddly bit I think
<re_irc>
<@romancardenas:matrix.org> And the merge_queue thing in the workflows
<re_irc>
<@therealprof:matrix.org> : Does that require super permissions or can maintainer do that? Thinking of the dozens of repos in the stm32-rs group.
<re_irc>
<@adamgreig:matrix.org> yea, the "merge_group" trigger on the workflow files is what I meant by making sure they were triggered
<re_irc>
<@adamgreig:matrix.org> it requires normal admin permissions on the repo I believe
<re_irc>
<@therealprof:matrix.org> +any
<re_irc>
<@romancardenas:matrix.org> I tried to activate it on riscv and I had the permissions. I'll probably do it later today (or maybe can do it)
<re_irc>
<@adamgreig:matrix.org> cool, I think let's see how that one goes and look to do the same on cortex-m or e-h next to try it out and write up the process a bit
<re_irc>
<@adamgreig:matrix.org> but yea, so far no obvious showstoppers
<re_irc>
<@adamgreig:matrix.org> currently translations are a fork of the repo onto the translator's github account, where they push a translated version of each markdown file, and publish the result, and we link to it
<re_irc>
<@almindor:matrix.org> done
<re_irc>
<@adamgreig:matrix.org> the PR proposes instead using gettext/PO files and an mdbook extension to use them, so translators would basically translate each paragraph using standard translation tooling/software, and all languages would be hosted in our repo and published to our main page, with a language select box basically
<re_irc>
<@therealprof:matrix.org> That is going to be a boatload of work...
<re_irc>
<@adamgreig:matrix.org> which seems nicer in many respects - other people can more easily help with translation now and in the future, it's all hosted in one place and one website, we control what gets published more easily, and you can use all the existing translation tooling to do translation work
<re_irc>
<@adamgreig:matrix.org> but I don't know exactly how much more or less work that is for translators than forking and editing a bunch of markdown files one by one, and it might be a lot of work to move existing translated content into the new format, and it also means translators are limited to translating paragraphs at a time, they can't restructure or reorganise anything
<re_irc>
<@therealprof:matrix.org> Been there before...
<re_irc>
<@adamgreig:matrix.org> it is also a bit different when the english version is updated - currently people reading a translation would still see the old translated content, and it may be a long time until any commits are moved to the translated repo, whereas this way, I believe the updated parts would render in english until re-translated, but are always up-to-date
<re_irc>
<@therealprof:matrix.org> No objections to going this route but I believe we should have a few volunteers signed up before.
<re_irc>
<@adamgreig:matrix.org> for porting the existing translations?
<re_irc>
<@therealprof:matrix.org> In general for doing translations.
<re_irc>
<@adamgreig:matrix.org> we don't have to port them, or anyway not immediately - we can maintain the list of links to external translations, open an issue on those repos saying they could swap to po files in our repo if they like, and say for new translations please use the po files
<re_irc>
<@therealprof:matrix.org> We should have at least a partial translation to implement that. Otherwise the new mechanism might lie dormant due to people not knowing how to do that.
<re_irc>
<@adamgreig:matrix.org> the PR includes a (very) partial translation into danish
<re_irc>
<@adamgreig:matrix.org> are you saying we should have a partial translation before even merging the pr adding support for translations, though?
<re_irc>
<@therealprof:matrix.org> Yes.
<re_irc>
<@adamgreig:matrix.org> how do we get that before we support having it?
<re_irc>
<@jamesmunns:beeper.com> : There are some translations of the embedded book iirc?
<re_irc>
<@therealprof:matrix.org> Well, that's why I said some volunteers interested in using that mechanism to do translations would be nice.
<re_irc>
<@adamgreig:matrix.org> not in the pofile format being added in this pr
<re_irc>
<@romancardenas:matrix.org> I could help with Spanish, but I won't be available until mid June probably
<re_irc>
<@therealprof:matrix.org> The first big whoop is important. I get that this approach makes it easier to do translations but without a sufficiently complex example we won't get a lot of drive-by translations.
<re_irc>
<@therealprof:matrix.org> Plus: This puts the responsibility for the translations on us and for some languages it might be hard to find speakers to actually sanity check the PRs.
<re_irc>
<@juliand:fehler-in-der-matrix.de> Is lack of translations an actual issue here? Personally, I get along much better with an up to date English example than an outdated translation. So is it worth the effort already now?
<re_irc>
For getting started with embedded Rust (knowing "normal Rust" and embedded C) my biggest problem was getting a rough overview of how things are connected (e-hal, embassy, cortex-m, esp32, probe, etc). Like there is a lot of great tooling, but it feels a bit overwhelming too navigate through it.
<re_irc>
<@therealprof:matrix.org> : ... my Korean is pretty much non-existent, though better than my Farsi. 😅
<re_irc>
<@adamgreig:matrix.org> I guess it's hard to know, presumably people who would most need a translation are unlikely to talk about it here (or anywhere I can read...)
<re_irc>
<@adamgreig:matrix.org> in any event several people have made translations
<re_irc>
<@therealprof:matrix.org> I'm having a very strong déjà vu. That's pretty much exactly how the GIMP documentation started 20 years ago.
<re_irc>
<@juliand:fehler-in-der-matrix.de> : Sure, I'm only concerned about outdated translations that cause frustration when you follow the instructions and then nothing works
<re_irc>
<@juliand:fehler-in-der-matrix.de> In the end it's better than having none, though 👍🏻
<re_irc>
<@burrbull:matrix.org> We could announce "translation week". Similary to driver initiative. People like events.
<re_irc>
<@adamgreig:matrix.org> yea, that's fair! the current setup has that problem because the translations are forks that may or may not get updated, but the new setup would not, I think, because changes to the english text would mean that part shows up in english until it's re-translated, as i understand it
<re_irc>
<@therealprof:matrix.org> The tools certainly have gotten tons better than way back then but the story is exactly the same. First there was English, then there were full translations into a few languages, then we moved over to gettext.
<re_irc>
<@therealprof:matrix.org> That's the currect state of affairs BTW: https://docs.gimp.org/
<re_irc>
<@adamgreig:matrix.org> ah interesting
<re_irc>
<@adamgreig:matrix.org> so, it seems like a fairly viable approach?
<re_irc>
<@adamgreig:matrix.org> we should briefly cover the last couple of agenda points, so let's revisit translations next week, but in the meantime would you mind writing up your thoughts briefly on the PR (https://github.com/rust-embedded/book/pull/356)?
<re_irc>
<@burrbull:matrix.org> need also automatize po/pot files update. The PR does not cover this.
<re_irc>
<@jannic:matrix.org> Looking at the percentages on the gimp docs is not very encouraging. I guess there a lot more gimp users, and a bigger percentage interested in translations.
<re_irc>
<@adamgreig:matrix.org> I suspect it's not helped by each paragraph becoming untranslated whenever there's a change to the english text?
<re_irc>
<@9names:matrix.org> The gimp docs are also much larger, 1 person would make less impact on the numbers
<re_irc>
<@adamgreig:matrix.org> ie clone repo, generate/update po files in the repo, commit result. except that middle step involves software that supports po files, I guess
<re_irc>
<@adamgreig:matrix.org> check them out if you've been following the discussion around the DelayUs thing, and we can discuss them in more detail next week
<re_irc>
<@adamgreig:matrix.org> thanks everyone!
<re_irc>
<@therealprof:matrix.org> : Viable certainly but only with enough community fuel. 😉
<re_irc>
<@juliand:fehler-in-der-matrix.de> : I mean if there is a repo connected that has a full working setup, one can still figure things out. CI should be able to make sure of that :D
<re_irc>
<@ragarnoy:matrix.org> : damn wow thanks
<re_irc>
<@nvsd:matrix.org> Does anyone know how to get rid of "can't find crate for "test"can't find crate" in nvim? I see solutions for vscode using a rust-analyzer config but I'm unsure how to solve it in nvim.
<re_irc>
<@nvsd:matrix.org> * 'test' can't
<re_irc>
<@nvsd:matrix.org> I believe it's related to no-std