Skip to content

Conversation

lucasmz-dev
Copy link
Collaborator

  • Pontos de acesso -> Redes (because it's too big, even though I like it)
  • localização precisa -> local exato (match AOSP translation)

@lucasmz-dev lucasmz-dev force-pushed the pt-br branch 2 times, most recently from 72e3047 to f84d008 Compare May 19, 2025 07:15
@lucasmz-dev lucasmz-dev changed the title translation: pt-BR: update app translation: pt-BR: update app + fastlane May 19, 2025
Copy link

codecov bot commented May 19, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.26%. Comparing base (5f0c9a5) to head (bba7695).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #516   +/-   ##
=========================================
  Coverage     95.26%   95.26%           
  Complexity      868      868           
=========================================
  Files           123      123           
  Lines          2618     2618           
  Branches        194      194           
=========================================
  Hits           2494     2494           
  Misses           44       44           
  Partials         80       80           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@lucasmz-dev lucasmz-dev force-pushed the pt-br branch 2 times, most recently from 97046ce to 11c5a12 Compare May 19, 2025 07:52
- Pontos de acesso -> Redes (because it's too big, even though I like it)
- localização precisa -> local exato (match AOSP translation)
- etc.
e.g. in the string about frequently asked questions, it instead asks you to check the questions in the website frequently.
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates the Portuguese (pt-BR) translations for both the app and fastlane metadata to adhere to updated terminology and AOSP translation guidelines.

  • Updated terminology from “pontos de acesso” to “redes”.
  • Revised several string resources to improve clarity and match AOSP standards.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
fastlane/metadata/android/pt-BR/full_description.txt Adjusted descriptive text to use “redes” instead of “pontos de acesso” and updated other related translations.
app/src/main/res/values-pt/strings.xml Updated several string resources (e.g., “scanner_play”, “no_data_msg”, “export_not_available”, “security_none”) to improved translations.
app/src/main/res/values-pt-rBR/strings.xml Modified action labels and other texts for consistency with the new terminology in the app UI.
Comments suppressed due to low confidence (1)

app/src/main/res/values-pt-rBR/strings.xml:51

  • The updated string for channel_rating_best_alternative seems truncated compared to the previous version. Please verify that removing 'Wi-Fi' was intentional and that the message remains clear and contextually complete for end users.
<string name="channel_rating_best_alternative">", tente a banda de"</string>

@VREMSoftwareDevelopment
Copy link
Owner

VREMSoftwareDevelopment commented May 19, 2025

Pontos de acesso -> Redes (because it's too big, even though I like it)

Where is it too big?

localização precisa -> local exato (match AOSP translation)

This translation is taken directly from Google Android API

@lucasmz-dev
Copy link
Collaborator Author

Where is it too big?

That one actually fit in my screen, though likely wouldn't on slightly different screens. It's not really common to see anyone say access point here though, we just end up saying network. The other strings (that I then changed later) did not though.

This translation is taken directly from Google Android API

Huh, wdym? Where is that? I like to follow AOSP but not too much because it also DOES suck (it's constantly changed in QPRs, yet... not anything that needs to be fixed is), but I wanna keep it using similar terminology so things are findable. That one you actually changed for the regular pt string but I undid that but then just replaced that, basically which kept it the same as pt.

To be honest the little changelog I added quickly stopped being of much description. I ended up adapting a lot more than I thought I would initially

@VREMSoftwareDevelopment
Copy link
Owner

Possible locations when Android Studio is installed:

  • English: <android_sdk_folder>/sdk/platforms/<android_api_version>/data/res/values/string.xml
  • Portuguese Portugal: <android_sdk_folder>/sdk/platforms/<android_api_version>/data/res/values-pt/string.xml
  • Portuguese Brazil: <android_sdk_folder>/sdk/platforms/<android_api_version>/data/res/values-pt-rBR/string.xml
  • etc

Example key: name="permdesc_accessFineLocation"

@lucasmz-dev
Copy link
Collaborator Author

Can I keep the version I did? Or is that automated? I'm not a fan of how these descriptions are translated in Android, they seem pretty abandoned

@VREMSoftwareDevelopment VREMSoftwareDevelopment merged commit 9a0d972 into VREMSoftwareDevelopment:main May 22, 2025
5 checks passed
@lucasmz-dev
Copy link
Collaborator Author

lucasmz-dev commented May 22, 2025

@VREMSoftwareDevelopment working on pt-PT rn

I'm not a native pt-PT speaker but... still. I'm basically using the AOSP translations and previous contexts to try and make it easier for an european user to go and find the relevant settings.

Will actually also send ANOTHER pr for pt-BR because I noticed something while doing this lmao (sorry for the commit spam)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants