#Validation of translation placeholders for localized string failed
dire beacon
Logger: homeassistant.helpers.translation
Source: helpers/translation.py:285
First occurred: 18:51:15 (4 occurrences)
Last logged: 18:51:15
Validation of translation placeholders for localized (en-GB) string component.google_drive.config.abort.access_not_configured failed: (set() != {'message'})
Validation of translation placeholders for localized (en-GB) string component.google_drive.config.abort.create_folder_failure failed: (set() != {'message'})
Validation of translation placeholders for localized (en-GB) string component.google_drive.config.abort.no_url_available failed: (set() != {'docs_url'})
Validation of translation placeholders for localized (en-GB) string component.mastodon.exceptions.integration_not_found.message failed: (set() != {'target'})
quartz drum
please create individual issues for them
dire beacon
please create individual issues for them
All you're getting is two 😉
quartz drum
yes that
hollow sun
@quartz drum is this an issue with packaging of b0, running locally and mastodon is fine at compiling the English translations.
quartz drum
I mean I would expect it to error out if this happened at dev
So I agree, there is something weird going on
this is done in the backend
so I also don't expect cache
hollow sun
ok, weird it's multiple integrations, I'll hold off chasing this more today.
quartz drum
where do you see the more integrations?
Also
I remember after a patch release there was a mastodon issue
what was that about
and is it maybe related?
hollow sun
Start of this thread there's also google_drive ones mentioned
quartz drum
yes
but I was wondering what that was and if its related
at this moment I suspect lokalize not having up to date strings, or we are downloading wrong strings
or something isnt working in the config flow
If it's the first
I might go to Amsterdam tomorrow and have drinks at Lokalize
😂
hollow sun
There wasn't any mastodon issues/pr's in Feb, just 2 pr's that went into this month.
Seems to only be issues with translations with params, seeing a few of those closed in the past but no real resolution, just fixed in v xxx
quartz drum
I will also try to look at this tomorrow
hollow sun
Thanks, shout if I've done something stupid with this one, or get a free beer from Localize if it's their fault 😀
quartz drum
fun fact, they are sponsoring a free happy hour
hollow sun
Have they done lots of things wrong for a whole hours worth 😆
royal python
Vandalized translations. Nothing more.
I just found around 50 references from 8 hours ago, but there seems to be way more in an earlier attempt
quartz drum
but then still those wouldn't be valid right?
and localize would still mark them als unverified?
quartz drum
Those end up being valid and verified
but how
royal python
Some person translated it and that's how it works
quartz drum
oh no I get that part
but I mean, we have set the validation of strings to not accept strings with mismatching placeholders right
royal python
That's never been the case.
quartz drum
hollow sun
Fixed in 2025.3.0b1, thanks @royal python
quartz drum
I gave this feedback to lokalise today
royal python
The settings you're having there apply to the editor, but will not prevent you from downloading it.
royal python
Did you change the settings to error now or was it already error before?
quartz drum
this one was already error
but
this is a separate one
and this one seems to be used
royal python
I've just seen the latest messages on the beta channel
There are 230 new [VOID] in the English UK
All done today
royal python
That person translates some of them and put [VOID] into others
Can you put a ban on that person?
royal python
I reverted it in bulk, I wish I found this yesterday 😛
royal python
Thanks! 🙂
quartz drum
Like, if it was a complete stranger, I would have banned
but like, if you are submitting 2 PRs for translations and then doing this, I am fairly sure this is an accident
My guess would be
"This sounds bri'ish enough, let's make it empty"
with the idea it would take the source string
royal python
I think your guess is right.
astral thistle
Hello! Dan here...
quartz drum
👋
astral thistle
I was following rule 4 here
Which I don't like at all, because it makes for a rubbish workflow... But I thought that was the right thing to do
astral thistle
I'd very happily clone the source text when it's valid for British English, because it makes the whole thing much better
quartz drum
@pliant lantern Do you remember when the project stopped using [VOID]?
royal python
If you're entering [VOID] it just gets an empty string right now. So during beta, if people use the language you're helping to translate, a lot of texts dissapear.
quartz drum
But I don't think you're to blame, you did what the docs did and we should definitely update the docs
astral thistle
I hadn't until recently... Another user pointed it out and I realised they were correct. Apparently not...
But if we can just update the docs and go back to copying the source text then that would be great from my point of view.
Sorry. Didn't mean to break anything!
quartz drum
I think that is the way to go yes
No no don't be sorry!
I mean, I am mostly happy that you created PRs this week, otherwise I would not have remembered your name 😂
astral thistle
Well you were exceptionally patient with me there too! So thank you. I learnt a lot!
quartz drum
oh but that wasn't that bad
I mean I also made a mistake
there are also people who get you on your nerves
who can only steer in 90 degrees, so its either left or right, no in between
astral thistle
So, should I run through and undo the [VOID] entries?
I certainly won't add any more
quartz drum
I think Silam now reverted all of them
royal python
Yeah, all covered. 🙂