AntennaPod currently and mostly uses WiFi (without a hyphen) on source language across all components on Weblate. I say mostly because, when querying :source on Weblate, it shows 185 strings for WiFi versus 100 strings for Wi-Fi. As far as I know, there’s really nothing wrong with the WiFi spelling. It is used informally, just not officially. The hyphenated form is the official term defined by the Wi‑Fi Alliance and is used consistently by major tech companies in their documentation.
Pros of replacing:
Fix the divergence of terms within the source vocabulary;
Update it to a more industry-standardized term;
End up sounding more credible and professional through points (1) and (2).
In the end, it’s a tiny change, but I believe that it would make the app feel just a bit more polished and professional. Any feedback is appreciated.
Hello!
I doubt many people are aware of point 2, but consistency is always good. It’ll be extra work for translators, but I reckon that we can do it still.
If we do it now @ByteHamster then maybe we can still include it in the next beta?
Then @delthia can send a message to all translators via Weblate, both about this Wi-Fi correction and the beta release.
I think it would be great if we could do the full release before August. If no new bugs show up, we maybe don’t need another beta (especially given that the release has mostly bug fixes)
That’s a fair point. Also, if these strings are not updated, it’ll display English instead.
I wonder actually if we update translation strings in code, Weblate will pick that up. I would suspect it does. We can try, and if that doesn’t work we can export from Weblate and import changes. So either way translators don’t need to retranslate.
Ok, great. Then let’s not do it now. We can try after the release is out.
Hi @Matth78!
Thanks for bringing your perspective. I totally understand when you say it isn’t really noticeable and I kinda feel the same. It’s a hyphen-sized issue . For context, I was actually reviewing the pt-BR translation trying to figure out some network-related string that mentioned “WiFi” and when I checked “Other languages” for more context, to see how other Latin languages were translating it, I couldn’t help but notice these differences across translations (WiFi x Wi-Fi). That caught my attention and I decided to take a look into the source language as well to see if the divergence occurs there too, that’s when I found out. So yes, quite stealthy.
The main reason for this substitution would be to standardize our vocabulary. By doing so, we minimize the chances of our translators replicating the divergence, and by adopting the hyphenated form we comply with the industry standard (examples [1], [2], [3]). As for the extra work, Weblate has a feature for mass replacement that’s very straightforward, it’s a 4-click-ish function, so no worries!
I’m not a coder or translator, but I actually am aware of the proper forms for Wi-Fi, Bluetooth, and Blu-ray (often misspelled Wifi, Blutooth, and Bluray, respectively). Though it’s not a huge deal, I concur with @OlliesGudh about the matter of professionalism. Even more important than correctness is consistency, and I would hope that our code and documentation are consistent. Spellcheckers will usually provide the correct forms, including right here in this forum where I see those common misspellings underlined in red. However, I don’t claim to understand how that works in languages other than English.
I prefer wifi as it means less faff with the on screen keyboard on my phone switching between alpha and symbolic modes. Though I suppose auto-correct will eventually learn to offer me up the capitalised, hyphenated version.
Yes, I already said as much in my follow-up replies covering how we could do this
I didn’t think about this one, thanks for bringing it up.
Note that it’s not as simple as using the ‘Search and replace’ functionality alone: it won’t work on the source strings because we manage those in code, not through Weblate.
Also: I’ve tried using Search and replace but it doesn’t find any string in the App component. Not sure why that is.
Oh snap! That was me being naive I assumed it was pulled from Weblate source strings.
About that… It’s possible that I might have done something wrong while making these replacements for pt-BR. Maybe I replaced for all possible components?
That wasn’t my intention. I apologize for that. I’ll make sure to double check when using new tools. Do you want me to revert those manually? I could do it and I’d be okay with that.
. For context, I was actually reviewing the pt-BR translation trying to figure out some network-related string that mentioned “WiFi” and when I checked “Other languages” for more context, to see how other Latin languages were translating it, I couldn’t help but notice these differences across translations (WiFi x Wi-Fi). That caught my attention and I decided to take a look into the source language as well to see if the divergence occurs there too, that’s when I found out. So yes, quite stealthy.
I assumed it was pulled from Weblate source strings.