Welcome Translators! Coordination & Help #20
Replies: 11 comments 14 replies
-
|
We can't get more context for the terms, can we? I think it is often hard to (correctly) translate term without more context, because often I don't know where this word is used and for what. |
Beta Was this translation helpful? Give feedback.
-
|
I know this part would be a little tricky in some cases. Let me give you some ideas that might help. For the dashboard, it is probably the most challenging. Here is what I might try: Idea 1:
Now when you look a the dashboard, it will show err- so you know that that is referencing. Of course you don't have to clear out the entire file like I did, you could just remove the keyname in question, and that will cause the err- to appear. 
Idea 2:
Idea 3:
Note, the templates are complex, so this may be more difficult than I'm making it seem. 
_Reminder, you can always use the dashboard tool to regenerate the dashboard if you change the text in the cards for texting. I really appreciate you spending time on this, hopefully those get you pointed in the right direction, but if not, ask questions and I"ll try to help. Whatever we figure out works well here to help the future translators, so if you find something that works well, please share. THANK YOU! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the hints, I'll have a look when I find the time. Glad I can help with this awesome project. |
Beta Was this translation helpful? Give feedback.
-
|
I understand how overwhelming it can be. That's really how I felt when I got about 1/2 way through trying separate all the backend and frontend code from using standard strings. 😫 That gave me a whole new appreciation for how much effort this can really be... and I"m really happy to see you were able to get through a first pass at the dashboard and notifications! 
That said, don't feel like you need to complete every single translation in the main integration file which is like 17,000 words... That one has all kinds of error message and such that are probably good enough... I would focus the time you do spend on the user facing items which should help reduce that down significantly. The good thing about the main integration translation file, is that you do have context for each translation. For instance, in the screenshot below you'll notice I underlined the specific config flow step and field that this shows in. If you aren't familiar, the config flow is the group of steps that walks you through the initial setup of the integration, while the options flow is the group of steps and menus that you interact with for all other integration configurations. With that in mind, I would focus in this order: config.step.* - initial configuration flow the users see Note that entity sensors are best viewed with attributes by going to developer tools and searching for those entities. be sure to bring up the more-info box to see them, that is where the translations show when you look at detailed attributes, etc. 
Thanks again! |
Beta Was this translation helpful? Give feedback.
-
|
Also, I did a small maintenance release 1.0.1 that includes your work to date. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Great to see that my work is already taken in :) |
Beta Was this translation helpful? Give feedback.
-
|
Hi every one, I translated 80% off my dashboard to french .
"Steal" here = "Rob" or means "Always" / "again" ? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Mickbab65! Thanks for reaching out. First, let me explain the "Steal" concept, as it is a gamification mechanic! In ChoreOps, "Steal" means taking a chore that is assigned to someone else so you can earn the points/tickets instead of them. For example, if it is my turn to take out the trash, but I forget and the chore becomes overdue, a "steal window" opens. My housemate can then do the chore and "steal" the reward. steal_window_open: The specific time period (window of time) when a chore is allowed to be stolen by another user. steal_available: The status showing that a chore is currently able to be stolen. (same as steal window open) at_due_date_allow_steal: A configuration rule that allows someone to steal the chore the exact moment it becomes overdue. Regarding your translations: However, those built-in French translations are currently machine-generated, so they likely sound a bit unnatural (which might be exactly why you are re-translating your dashboard!). If you have already put the time into fixing up the French text, would you be interested in contributing your work so all French users can benefit from it? We have a Crowdin project set up specifically for this, or you can simply share your updated fr_dashboard.json file with me here and I can merge it in for everyone. Let me know if the "steal" concept makes sense now, and if you'd be open to sharing your translations with the community! |
Beta Was this translation helpful? Give feedback.
-
|
Hello :) I was just about to propose my help for the French translation (need to check how things work first) if you and @Mickbab65 need some help :) |
Beta Was this translation helpful? Give feedback.
-
|
Hi @ccpk1 and @thegreatlizzyator , |
Beta Was this translation helpful? Give feedback.
-
|
Here is a link if either / both of you would like to help with translations. Once you register, I think I will need to approve your access but I will do that within 1/2 day of when you request and ensure you have what you need. As mentioned in the discussion above, it is best if you focus your time in the priority order you see listed since those are most user facing, but feel free to fix and approve anything you think needs adjusted. Also, some instructions are above to help you with individual testing, but the changes you make will not generally be available to the public until I do a release. If you feel like get enough completed it makes sense to do a release focused on it, I'll probably be willing to do that. Otherwise, I will just do it as part of the normal fix and feature releases. https://crowdin.com/project/choreops-translations/invite?h=669f88e2a8c949753dd555652c60a7bb2718124 Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Hi,
Integration is in progress ( a little bit long for this part XD) |
Beta Was this translation helpful? Give feedback.
-
|
I've finished translating all the files. I hope I haven't missed any words or sentences that needed more clarification. However, when I replaced words or sentences, everything was validated instantly. |
Beta Was this translation helpful? Give feedback.
-
|
@Mickbab65 - That's great! I can see the translation change you made, as well as the one translation done by @thegreatlizzyator. One thing you didn't do, was to mark your changes as approved. In addition to what you changed, if the existing translations you looked at were correct, also marking those as approved so anyone else helping knows those have already been reviewed and approved. (They can always be adjusted further in the future.) I went ahead and marked approved on everything you changed today, but if you are comfortable that everything else in the dashboard, notifications, and reports is well translated, can you mark all of those strings as approved too? (You can select all of them and just click the approve button.) Below you can see the progress, when I just approved the items I could see you changed. The % will go up further if you mark the remaining dashboards, notifications, and reports as complete. 
|
Beta Was this translation helpful? Give feedback.
-
|
Hi, I changed some words again to be more accurate in the file "dasboard", and I marked as approved. |
Beta Was this translation helpful? Give feedback.
-
|
Also, I just updated to release 1.0.5 https://github.com/ccpk1/ChoreOps/releases which includes all the German and French work to date! Reminder you will need to regenerate your dashboards to see all updates. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Great! I might need to revisist some of the dashboard translations as the German language tends to be overly long sometimes, compared to English. Some descriptors tend to be a bit too long and overlap with other content. |
Beta Was this translation helpful? Give feedback.
-
|
Hi! I’d like to help with the Polish translation ( I can help review and improve the existing machine translations, preserve placeholders and formatting syntax, and test the translated files directly in Home Assistant. Please assign Polish to me if it is currently available. |
Beta Was this translation helpful? Give feedback.
-
|
ChoreOps Translations (pl).zip |
Beta Was this translation helpful? Give feedback.
-
|
Can you confirm this is where you are trying to download from and maybe screenshot the error message? 
|
Beta Was this translation helpful? Give feedback.
-
I tried downloading it from every possible place, but the translation panel clearly shows that the download option is disabled for me.
|
Beta Was this translation helpful? Give feedback.
-
|
I think I found the project setting that was blocking translators from downloading. Can you try again when you get time and let me know? Thanks |
Beta Was this translation helpful? Give feedback.
-
|
It works, thanks. |
Beta Was this translation helpful? Give feedback.
-
|
FYI - I just released 1.0.6 which brings all the translation work you've all been doing to current. Even the Polish updates that it appears @CodekExplor was working hard on today. Thank you! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Welcome Translators! Coordination & Help
First, thank you to everyone helping translate ChoreOps. This discussion is here to give us one place to coordinate translation work, ask questions, and resolve issues that come up during the process.
A few important notes
Machine translations are only a starting point
The project has been seeded with machine-generated translations for an initial pass. Please review them carefully and correct anything that reads awkwardly, inaccurately, or unnaturally.
Keep syntax exactly intact
Some strings include placeholders and formatting symbols such as
{variables},%, or other special characters. These must remain unchanged so Home Assistant can insert values correctly.Crowdin suggestions are welcome
If you have more Crowdin experience and see a better way to organize or manage translations, please say so. Feedback on workflow or setup is useful.
Dashboard translations have a separate internal flow
Some dashboard-related translation content is maintained in the ChoreOps dashboard repository first and then synchronized into the integration. This is handled on the project side, so it is not something translators need to manage manually, but it is worth noting in case you notice dashboard translation content following a slightly different update path.
How updates and testing work
As translations are updated and approved, they will be included in future releases automatically.
If you want to test your language changes right away:
custom_components/choreops/translationscustom_components/choreops/translations_custom[lang].json[lang]_notifications.json[lang]_report.json[lang]_dashboard.json[lang]should be replaced with your language code.Dashboard translations follow a separate source and sync flow
Dashboard-visible translation copy is authored from the dashboard side first, with the English source maintained in
choreops-dashboards/translations/en_dashboard.json. Those dashboard translation assets are then synchronized into the integration’s runtime dashboard asset location undercustom_components/choreops/dashboards/translations.Why they are stored there at runtime
This is done so the ChoreOps integration can serve dashboard-localized strings directly through its backend dashboard translation system. In other words, the dashboard repo is the authoring source, but the integration must still contain the synchronized runtime translation assets so Home Assistant can load them for the dashboard UI.
Why dashboard translations are handled this way
You do not need to worry about a separate translation workflow in practice, because everything is still managed in the same place in Crowdin. The reason dashboard translation source content is maintained through the dashboard release pipeline is so new dashboard releases can be published for download without requiring a full integration update. If a dashboard release adds new translations, Home Assistant will still need to be restarted or upgraded before those new strings are served by the integration. For local testing, you can simply download the translated dashboard file, place it in the integration’s dashboard translations directory, and restart Home Assistant.
How updates and testing work
As translations are updated and approved, they will be included in future releases automatically.
If you want to test your language changes right away:
custom_components/choreops/translationscustom_components/choreops/translations_customcustom_components/choreops/dashboards/translations[lang].json[lang]_notifications.json[lang]_dashboard.jsonIf you are new to Crowdin, this guide may help:
https://support.crowdin.com/for-translators/
Thanks again for helping make ChoreOps more accessible to more families.
Current language coverage
Coordination notes
Beta Was this translation helpful? Give feedback.
All reactions