Bug 139834 - [UI] String breaks translation gender
Summary: [UI] String breaks translation gender
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Chart (show other bugs)
Version:
(earliest affected)
7.0.3.1 release
Hardware: All All
: medium normal
Assignee: Olivier Hallot
URL:
Whiteboard: target:26.2.0
Keywords:
Depends on:
Blocks: Chart
  Show dependency treegraph
 
Reported: 2021-01-22 12:25 UTC by Olivier Hallot
Modified: 2025-07-10 11:57 UTC (History)
3 users (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.
Description Olivier Hallot 2021-01-22 12:25:29 UTC
The string  iKkhv (STR_STATUS_OBJECT_MARKED) in chart2 breaks gender in latin languages

String is "%OBJECTNAME Selected"

%OBJECTNAME can me masculine or feminine depending on the nature.

for pt-BR

Eixo (Axis) -> masc.
Área (Area) -> fem.
Linha (Line) -> fem.
...

So please find a way to include gender in %OBJECTNAME.

Thanks
Comment 1 Mike Kaganski 2021-01-22 12:36:20 UTC
I suppose it's up to translators to modify this string. E.g., it could possibly be for some language: "Selection: %OBJECTNAME", or some such.
Comment 2 Olivier Hallot 2021-01-23 17:49:06 UTC
Good catch.
Works nicely with pt-BR.
Comment 3 Buovjaga 2021-12-02 12:31:43 UTC
Seems to be OK, so closing
Comment 4 Adolfo Jayme Barrientos 2021-12-05 18:05:36 UTC
We shouldn’t be forced to do juggling with the translations to work around a bad source string.

Reopening until a source-code fix is made.
Comment 5 Mike Kaganski 2021-12-05 18:52:26 UTC
(In reply to Adolfo Jayme from comment #4)
> We shouldn’t be forced to do juggling with the translations to work around a
> bad source string.

I don't quite understand. Do you say that the source string is bad, and "%OBJECTNAME Selected" must be replaced with something else (which I disagree with: given >5000 natural languages out there, and >100 translations for LibreOffice, you will always find a language where a given string is awkward to translate, so no source string should be considered "bad"); or do you say that there needs to be a machinery to provide some gender-speicifc translations?
Comment 6 QA Administrators 2023-12-06 03:17:57 UTC Comment hidden (obsolete)
Comment 7 Commit Notification 2025-07-10 11:56:26 UTC
Olivier Hallot committed a patch related to this issue.
It has been pushed to "master":

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

tdf#139834 Fix UI string for object gender

It will be available in 26.2.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.