-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prune unmaintained languages #3772
Prune unmaintained languages #3772
Conversation
Aww… I love being able to tell people Marlin supports "dozens" of languages. |
Well these are non mainstream languages.. |
@jbrazio It probably will happen that after 1.1.0 release, the language maintainers will appear with patches. But maybe not before. Have you messaged the individuals who made the most recent commits to these languages already? |
@thinkyhead All of them have been pinged, if no reply within a week this PR should be merged. |
Galician syncronized at the moment. Thank you for pinging to me 👍 |
Thank you for your contribution @rafacouto ! |
@jbrazio Should we add a header to maintained translations with the care taker(s) like in https://github.com/MarlinFirmware/Marlin/blob/RC/Marlin/example_configurations/K8200/Configuration.h#L23 ? So it would be easier to find natives for the next update... |
I like the idea, but how about using github teams ?
Or have a unique @Roxy-3DPrintBoard |
In my opinion the unmaintained languages should be kept in. |
I am going to give it a try to this script: https://github.com/nevik/gitwatch Another option could be a webhook to watch changes on the main language file and send an email to the maintainers declared in the header of the language files (@CONSULitAS ' idea). |
Closing due the creation of @MarlinFirmware/language-team. |
Removes unmaintained Spanish language variations:
language_an.h
)language_eu.h
)language_ca.h
)language_gl.h
)For now we still keep unmaintained:
Closes: #3357, #3354, #3349, #3347
This PR has the side effect of move
example_configurations/Felix/Configuration_DUAL.h
into its ownDUAL
folder and renaming it toConfiguration.h
. This is so the config file can be catched when doing mass edits based onfind . -name Configuration.h | xargs <something>
.