fix(portuguese-brazil): translate 3 high-confidence anglicisms (Checkout/Downgrade/Logs) - #71
Conversation
From the anti-slop pass requested by @teamssUTXO in -5292199939 2026-05-26. 33 entries in portuguese (brazil).json were flagged as identical-to-English; most are anglicisms acceptable in modern PT-BR (Login, Logo, Online, Plugins, Token, Upload, Webhooks, etc). This PR translates 3 entries where Brazilian Portuguese has clear conventional translations: - Checkout -> Finalizar compra - Downgrade -> Rebaixar - Logs -> Registros The other 30 identical-to-English entries are deliberately not touched - they're judgment calls (Hostname / Timestamp / Pull Payments / Memo / Min sats / etc) where the maintainer's preference governs. Some are widely-accepted anglicisms in BR tech context; some are specialized BTCPay/Bitcoin protocol terms that should stay English. Caveat: I'm not a native PT-BR speaker. These three translations are best-attempts grounded in common Brazilian e-commerce / dev usage. If thgO-O prefers different phrasings (e.g. 'Checkout' as anglicism, 'Logs' as anglicism), push a maintainer-edit on this branch or comment with the preferred wording and I'll update.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Portuguese (Brazil) translation file updates two strings: the ChangesTranslation Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
thgO-O
left a comment
thgO-O
left a comment
There was a problem hiding this comment.
Downgrade is a good catch.
I’d keep “Checkout” and “Logs” in English. IMHO “Finalizar compra” reads like a button/action label rather than the name of a screen, and the file consistently uses “checkout” in related strings like “página de checkout”, “Aparência do Checkout”, and “Experiência de Checkout”.
“Logs” is also already used naturally in strings like “arquivos de log” / “log do servidor”, while “Registros” feels more generic and may conflict with other meanings like registration/records.
Per btcpayserver#71 (review): - Revert 'Checkout' -> keep English. File consistently uses 'checkout' in related strings ('página de checkout', 'Aparência do Checkout', 'Experiência de Checkout'); a translated standalone reads as button/action label and creates inconsistency. - Revert 'Logs' -> keep English. 'log' already naturally used ('arquivos de log', 'log do servidor'); 'Registros' is generic and may conflict with registration/records meanings. - Keep 'Downgrade' -> 'Rebaixar' (thgO-O endorsed this catch). Net PR diff: 1 line, Downgrade only.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@translations/portuguese` (brazil).json:
- Line 624: The translation for the key "Downgrade" currently uses "Rebaixar"
while a related string "Would you like to downgrade..." remains as an anglicism;
update for consistency by either changing the "Downgrade" entry to the loanword
"Downgrade" or translate the longer prompt to "Você gostaria de rebaixar..." so
both keys ("Downgrade" and "Would you like to downgrade...") use the same
terminology, and run a quick search in the translations file to ensure no other
occurrences of "downgrade" conflict with your chosen convention.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: c97cbad2-a6c5-4b66-811f-fc4606921adb
📒 Files selected for processing (1)
translations/portuguese (brazil).json
4 participants
@thgO-O - opening this PR from the anti-slop pass on
translations/portuguese (brazil).jsonrequested by @teamssUTXO in the BTCPay Translations TG group 2026-05-26.What
Three high-confidence translations applied:
Checkout->Finalizar compraDowngrade->RebaixarLogs->RegistrosAnti-slop scan summary
33 entries in
portuguese (brazil).jsonwere flagged as identical-to-English (translation matches source). Most are anglicisms acceptable in modern Brazilian Portuguese tech context and deliberately not touched here:Login,Logo,Online,Upload,Plugins,Token,Webhooks,Editor,Normal,Link,Total,SubtotalLightning Address,PayJoin BIP21,Min sats,Pull PaymentsGoogle Cloud Storage,Amazon S3, etc.Hostname(->Nome do host?),Memo(->Nota?),Timestamp(->Carimbo de data/hora?),Pull Payments(->Pagamentos de saque?),Placeholder/Placeholders,Scripting,via HTTP/via HTTPS, etc.Full list of 33 identical-to-English entries with my suggested-or-keep notes is in the report markdown - happy to drop it here or paste into a comment if useful.
Caveats
I'm not a native PT-BR speaker. The three applied translations are best-attempts grounded in common Brazilian e-commerce / dev usage; please push a maintainer-edit on this branch or comment with preferred phrasing if any of them are off.
The identical-to-English entries left untouched are because they're either widely-accepted anglicisms in BR tech, BTCPay/protocol-specific terms, or judgment calls only the maintainer should make. Happy to do a follow-up PR with any additional translations you specify.
Context
Companion to #70 (Serbian fix) from the same anti-slop pass. Hindi findings are HTML-tag-mismatches that need maintainer Khush + Abhijay7 to restore tags - separate PR if they confirm here.