Closed Bug 1877232 Opened 1 year ago Closed 1 year ago

Thunderbird find shortcuts for pt-BR reported incorrect

Categories

(Mozilla Localizations :: pt-BR / Portuguese (Brazil), defect)

Product:
Mozilla Localizations
Component:
pt-BR / Portuguese (Brazil)
Type:
defect

Tracking

(firefox-esr115 fixed, firefox124 fixed)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox-esr115 --- fixed
firefox124 --- fixed

People

(Reporter: rjl, Unassigned)

References

(
URL
)

Details

Using the current release - thunderbird with PT-BR (portuguese Brazil) language pack (115.7.0)

Open a new Write message:
Some of the shortcuts are incorrect.
'Edit' > 'Find' is showing 'Ctrl+P' and the 'Find and Replace' is 'Ctrl+U' - both incorrect.
'Edit' > 'Find' should be 'Ctrl+F' and the 'Find and Replace' should be 'Ctrl+H'

This seems to be causing a problem because the 'Format' > 'Text Style' > 'Underline' also correctly uses 'Ctrl+U' - but it no longer works.
'Ctrl+P' opens the print dialog.

User in Support Forum posted this issue:
https://support.mozilla.org/en-US/questions/1437204

Both the "Find" and "Find and Replace" shortcuts were indeed incorrect in pt-BR localization.
I have corrected this and completely revised all the shortcuts.
It should be fixed in the next update.

Thanks! I will make sure the update makes it into an upcoming stable (115.7.1 or 115.8.0) release.

@Marcelo
You might want to check the first 4 in this list (the rest is SeaMonkey or false positives)
https://transvision.flod.org/commandkeys/?locale=pt-BR&repo=comm_l10n

Hi, Lodolo

All fixed.
Just "msg.url.key" does not match a keyboard shortcut.
Thanks for that tool in transvision.

Hi, Roland
I made a diff of this article with the pt-BR translation, all the shortcuts were already correct.

Flags: needinfo?(marcelo.ghelman)

Thunderbird 115.8.0:
https://hg.mozilla.org/releases/comm-esr115/rev/3dbed2394f58

Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox124: --- → fixed
status-firefox-esr115: --- → fixed
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.