Several slightly different loading screens

[dbkr]

Steps to reproduce

It looks like there are several screens that say "Loading..." in slightly different ways, between LoadingView and others views that just return <h1>Loading...</h1> (eg. RegisteredView, UnauthenticatedView). As a walkie-talkie call loads, I can see it step through two different versions of "Loading..." with a slightly different size font (and then "Loading room...").

Outcome

What did you expect?

Probably just one "Loading...", or one saying, "Reticulating splines..."

What happened instead?

Operating system

No response

Browser information

No response

URL for webapp

No response

Will you send logs?

No

[robintown]

Gaëlle says yes, we should change all loading screens to simply say "Loading…"

[abhijain2003]

can I work on this. yes having consistency on the loading screen is quite important.

[SimonBrandner]

can I work on this. yes having consistency on the loading screen is quite important.

Yes, sure, good luck!

[abhijain2003]

Thanks

[abhijain2003]

I just changed Loading room... to Loading... from
GroupCallView.tsx and GroupCallLoader.tsx and in all public/locales/[file]/app.json I just removed key-value of
"Loading room...": "Loading room...". As I think these are all implementation of multiple language support and as we are not using Loading room... anywhere I thought removing these properties from public/locales/[file]/app.json would be best.

while some other files still using slightly different words for loading in different components

such as Saving... is used like this in ProfileModal.tsx

{loading ? t("Saving…") : t("Save")}

and some are using Sending... I didn't change them to Loading.... as I thought they are matching with CTA
but if you want I will also change them.

so anyone please help me on these queries.
it would be helpful in my initial contributions

[SimonBrandner]

... and in all public/locales/[file]/app.json I just removed key-value of "Loading room...": "Loading room...". As I think these are all implementation of multiple language support and as we are not using Loading room... anywhere I thought removing these properties from public/locales/[file]/app.json would be best.

You aren't supposed to touch those files by hand. Remove the changes there and run yarn i18n which should update the appropriate files, rest is handled by Weblate

[abhijain2003]

ok I understood, I will make relative changes

Thanks for letting me know