-
Notifications
You must be signed in to change notification settings - Fork 0
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
New translations 16 Oct 2023 #182
Comments
Hey @auracles @hugopeixoto @jbethune @muminpappa, we could use some more translations (French, Portuguese, Danish & Swedish). A few text snippets have changed, some new ones have appeared. Please check out this issue’s description for a detailed overview and how you could help us out. As we are planning to go live with the tool possibly this Wednesday already, we’d be really happy if you could do the translation as soon as possible. But, no pressure, if you can’t make it then we’ll launch with the old versions or fall back to English. If you don’t have time to help us out right now, please just let us know so that we can try looking for someone else. |
I'm waiting for #191 to be merged, before I push the danish version. Late edit: Note about the closing event that is listed next: Seems like the Portugese translation had a close-issue association, which is wrong, because that's only a partial solution. |
In support for #182 I've followed the swedish translations as closely as reasonable. I also updated the strings for for call.home.description.[0,1]
Nonsense, this is not finished. |
translated and changed indicated paragraphs
it's a bit late now but I translated the changed paragraphs of the privacy policy mentioned above |
Linking #219 for the french translation |
The only thing missing here are the following French translations:
|
I’ll take care of the French translations within the next week! |
Sorry @auracles, that wasn't meant as a passive-aggressive "we still need this from you…!", but just as a summary/recap, as we're planning to release an open source version soon. More like "we should try getting these couple of messages translated by someone until then". But if you'd like to help us out again, I'd appreciate it a lot :) |
no worries! I didn’t take it that way, apologies if my reply came across this way. is the deadline ‘end of the week’ alright or do you need the translation sooner? |
It didn't, it's all good :)
Depending on to what degree you'd like to use Git, it's one of these:
I'd probably recommend the second option, but it's up to you really, and if you need any more help, let me know. :) The translations in the YAML file can all be found under
Nothing to be sorry for, we're thankful for your contribution.
Thursday would be great, because I'd like to package and test the release on Friday, but if you can't make that, just let me know and I'll prepare to get the French translations as a late addition, no big deal. Thanks again! |
Thanks a lot for testing and happy holidays (everyone)! |
Awesome, thanks so much :) Happy holidays to you too! |
With the French translations added, I've reduced the only two "missing" ones to warnings instead of errors in #300:
It doesn't make a lot of sense to contact translators just for the maintenance message (that might change on short notice anyway), and the privacy policy URL is only translated if we have an up-to-date privacy policy for that language. I think this issue can be considered done. Thanks again for everyone who contributed. |
This issue exists to guide volunteers to provide translations for several new text snippets in frontend & backend, as well as provide an overview over what needs to be done and what has been done.
Languages requested
We need translations for French, Danish, Portuguese and Swedish. Please create a new branch for your language (and name it
translation-XX-16-oct-23
, withXX
being your language code), do your translations there, and open a pull request for it. Mention this issue (#182) in the PR’s description so that it will be linked here.Changes requested
The frontend texts
call.home.descriptions.0.text
andcall.home.descriptions.1.text
have been modified in English & German, the other languages should follow.The Data Protection Policy has been slightly changed, please modify your translated version accordingly (English & German are done already):
In French and Portuguese, the
phone_number_verification_sms
translation does not start with{code}
. This is not a big issue, but if the{code}
is not placed at the beginning, it might be cut off from the notification popup the User will receive on their mobile phone, forcing them to open their SMS app to be able to read it. It’s therefore considered best practice to start the message with the code, even if it sounds slightly strange. Please update the translation in these two languages.New strings
You’ve done this before: We collect the translations in
server/dearmep/example-config.yaml
. You can simply scroll through the file and check where new translations are required, or use this list. The following strings are new:strings
):feedback_survey_sms
frontend_strings
):call.call-now-btn.outOfOfficeHoursHint
call.office-hours.title
call.office-hours.description
call.office-hours.hours-zoned
call.office-hours.hours
call.office-hours.day-range
call.office-hours.time-range-zoned
call.office-hours.time-range
call.office-hours.time-zone-local
call.home.titleAuthenticated
call.home.youHaveAlreadySignedIn
verification.enterNumber.numberIsRequired
verification.enterNumber.invalidNumber
verification.enterNumber.numberNotAllowed
verification.enterNumber.numberBlocked
verification.enterNumber.tooManyAttempts
verification.enterNumber.policyLinkUrl
verification.enterCode.invalidCode
callSetup.error.failedToEstablishCall
callSetup.error.failedToReachDestination
callSetup.error.outsideOfficeHours
feedback.skip
feedback.alreadySubmitedError
error.genericApiError
errro.genericError
error.errorDialogTitle
error.errorDialogOK
Languages completed
The text was updated successfully, but these errors were encountered: