Bug 143279 - Property marked as translatable but should maybe not
Summary: Property marked as translatable but should maybe not
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
7.3.0.0 alpha0+
Hardware: All All
: medium normal
Assignee: Julien Nabet
URL:
Whiteboard: target:7.5.0
Keywords:
Depends on:
Blocks:
 
Reported: 2021-07-09 13:40 UTC by sophie
Modified: 2022-07-10 19:11 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Comment 1 Buovjaga 2021-07-19 15:31:45 UTC
If I search with

git grep 'accessible-name" translatable="no"'

I get no hits, so the convention seems to be to translate accessible-names. There are 248 such translatable ones.
Comment 2 Adolfo Jayme Barrientos 2022-05-31 12:58:01 UTC
Then, those accessible descriptions should be written with proper syntax, instead of being camelCase.
Comment 3 Julien Nabet 2022-07-08 20:47:51 UTC
Following Adolfo's suggestion, I gave a try with https://gerrit.libreoffice.org/c/core/+/136911
Comment 4 Commit Notification 2022-07-10 19:09:48 UTC
Julien Nabet committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/e8388c9456dc1a7c753f4bc2a86473ced3be0830

tdf#143279: fix accessible-name in cui

It will be available in 7.5.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 5 Julien Nabet 2022-07-10 19:11:50 UTC
Since hard English string & UI freeze is over, let's put this one to FIXED.