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
Looking for language maintainers #3919
Comments
|
@danielmartinez we're just building the teams. |
Of course, I'll translate defines into Galician :-) |
@jbrazio of course, I can help with Spanish |
@jbrazio Of course! |
@jbrazio ok, i can help with italian.. |
We have a lot of hard coded English strings. Especially in Marlin_main.cpp. (Just look at the M48: code. I'm the guilty party on that one!) We might want to clean that up too. |
We will maintain Czech language as we did. |
@jbrazio We have complete Czech language with no problem. All translates on time. Please use @clexpert and @petrzjunior for Czech language as sufficient solution. You can tick this language. |
Dear @Roxy-3DPrintBoard |
@jbrazio |
@jbrazio |
@jbrazio |
This will result in a lot of clutter and complexity. By that same thinking, we will need Code-Maintainers-PreProcessor-Bugs as well as Code-Maintainers-Header-Files etc. etc. I'm not trying to be overly negative, but lets see if we have too many messages going to the Language-Team. If so, we certainly can rethink this. But my guess is even if you are not involved in a particular language's support, you might want to see what the issues are and what the decisions are in the other languages. Right? |
Pleas avoid that overhead. Indeed the unbearable German language file, from ending 2014 was the first thing i wanted to change and was the reason for beginning with Marlin programming. :-) |
I plan to have all the people related with language on a "global" language team as I agree with Roxy and Andreas, it will be a clutter for now and usually when we need to add a new string, it must be added to all languages. @AnHardt may I add you for German then ? :-) |
@jbrazio |
Should we translate in the RCBugFix branch? Marlin or MarlinDev repo? I miss a little translator guide (excuse me if it already exists O:) in order to assist new maintainers and non git-ninjas... |
MarlinDev is going away. RCBugFix is the correct place because what ever is there is going forward. And just for right now, during this release cycle, the RC branch is acting as 'Stable' and probably doesn't get the change applied to it. |
So now, I think it's the right time to discuss some future plans. |
Usually we need to translate a new string when a new feature is added.. up to now the developer adds the string into the English file and (which I do not agree) adds the same define in English on all other languages. The ideia is when a new string is added on the PR we just ping @MarlinFirmware/language-team informing there is a new string that must be translated. |
This is specifically designed to annoy language maintainers into fixing it. 😝 But also, helps ensure the strings are in the same relative position in all language files. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
We need your help, Marlin has a lot of language packs and we need to create a language team that will be responsible for having the translations up to date. Please answer to this issue with the language you would like to maintain, but be aware we prefer native speakers. We would like to have at least three people per supported language.
When a developer adds a new English string, he should ping the language team by tagging @MarlinFirmware/language-team.
The text was updated successfully, but these errors were encountered: