about refactoring user guides and moneropedia entries. I've been making some tests and checked things. I'm drifting away from the idea of refactoring the markdown documents to make them use the i18n plugin we use right now. Mostly because it's a crazy amount of work and because would be better to keep the markdown files, since weblate could be supporting parsing md files in the future and that would make things so

,much easier.

So right now i'm considering either converting the markdown files to html and then feed those to weblate, or use some scripting instead. Where we leave the markdown files as they are and we produce separate files that weblate will parse. This could be done using pandoc and/or po4all

Directly converting to html files would be more reliable and would allow us to tweak the html to make it as less invasive as possible, but we would have to convert all files and people will have to work on html instead of markdown. Which is not ideal.

I will make some experiments with po4a and po4a + pandoc. That should be smarter when creating the .po files to feed to weblate, and could avoid a lot of issues. beside, not directly touch the markdown files would be good.

po4a is well known and very stable: github.com/mquinson/po4a

Probably the versioning system will need to be refactored or rethought completely, because in the current state i'm not sure will be compatible with any of these systems.

.merge+ #1203

Added

someone mentioned in #monero-community that the BTC donation qrcode does not correspond to donation address. Probably qrcode wasn't updated together with address at some point.

Address shown 1KTexdemPdxSBcG55heUuTjDRYqbC5ZL8H is correct, so a corresponding qrcode should be created

Does it go to an address the core team previously controlled ?

looks like it, is is also listed here: bitcointalk.org/index.php?topic=700400.msg7914927#msg7914927

and in an old version of repo README.md

but core can answer that better :P