Open patogit opened 6 years ago
@Nikerabbit for untranslated items, for example in line 24 here: https://github.com/patogit/lime-docs/blob/testing-JSON/Booklet-01-Networks/json/01.fr.json#L24 Would it be okay to delete line 24 completely, or do you prefer that we leave it there with the empty translation?
Line 24 is now translated, but in general untranslated lines should not be present in the json. Empty values are treated as empty translations, not as a missing translation.
Updates? Is this issue fixed?
No updates from my side. Are further clarifications needed?
Yes! Thanks for reaching out. Will be writing to you hopefully this week.
El 7 de octubre de 2019 4:16:37 GMT-05:00, "Niklas Laxström" notifications@github.com escribió:
No updates from my side. Are further clarifications needed?
-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/libremesh/lime-packages/issues/257#issuecomment-538911627
-- Enviado desde mi dispositivo Android con K-9 Mail. Por favor, disculpa mi brevedad.
Seems that the last manual sync happened in 2019 by @nicopace in this repo https://github.com/LibreRouterOrg/docs/commits/master and in this one https://gitlab.com/librerouter/docs/-/commits/master but since then many more translations have been performed here https://github.com/translation-bridge/lime-docs/commits/master, is this right???
Can anyone with access to https://github.com/LibreRouterOrg organization take the role to update the documentation with the priceless contributions from TranslateWiki?
@G10h4ck @spiccinini @luandro @nicoechaniz
@ilario for me is ok to give commit access to TraslateWiki, what is the process to do that?
I cannot remember what was discussed in the many comments here (maybe I miss some obvious issue), but I suppose that:
I cannot remember what was discussed in the many comments here (maybe I miss some obvious issue), but I suppose that:
* someone with access to the target repository should manually update it with the last years of translations
@nicopace can you do that?
* we should get the username of TranslateWiki on Gitlab (most likely https://gitlab.com/translatewiki ) * someone with access to the target repository should add that user to the ones with access to that repo
@G10h4ck or anyone else with access to https://gitlab.com/librerouter/docs, can you give push rights to https://gitlab.com/translatewiki?
@ilario , I did the initial setup and coordination between LibreMesh and TranslateWiki. I think that the steps to take now are beyond my control, and belong to @nicopace and @G10h4ck as you say. If there is any way I can help, please let me know.
@ilario are you suggesting only pushing documentation translations? What about interface translations?
@ilario are you suggesting only pushing documentation translations? What about interface translations?
Nope, I am not entering in details. I just want the translations made by volunteers to not be wasted.
@G10h4ck and @nicopace are you willing to fix this? A huge amount of volunteers' work is getting lost here (the only entity that is taking advantage of their work is Microsoft Copilot, that is surely not why you asked for their help on TranslateWiki)!
@ilario i wrote a PM to you
Can you confirm that the app translations from https://github.com/translation-bridge/lime-app/tree/issue-119/i18n/translations have been integrated? I don't see them in https://github.com/libremesh/lime-app
@selankon @fnbellomo @luandro can any of you manually copy and paste the newest translations and give access to @translatewiki to directly push there the next translations?
(Continuing the conversation from PR #254)
@nicopace and @Nikerabbit (and anyone else who's interested), let's see if we can agree on how to arrange commit access for translation files from TranslateWiki. I imagine that whatever we work out here can apply to the LiMeApp too ( @gmarcos87 ), and maybe other repos if they're ready to translate before January.
How about if commits go to a protected branch for the first two months, and then we revisit the idea of TranslateWiki having direct push commit access?
In other repos, @TranslateWiki makes about one commit per month (usually on a Monday or Thursday). So after two commits maybe there will be more confidence to allow direct push... or maybe the LibreMesh development flow really depends on translations going through protected branches just like all the other code.
@Nikerabbit, would that work for you? Do you have other ideas?