Bug 388425 - krunner unit converter does not convert to a specific unit in french
Summary: krunner unit converter does not convert to a specific unit in french
Status: RESOLVED FIXED
Alias: None
Product: i18n
Classification: Translations
Component: fr (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR minor
Target Milestone: ---
Assignee: KDE Francophone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-01 15:27 UTC by Bertrand Bousquet
Modified: 2018-01-05 17:07 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Runner unit converter without specified unit (18.50 KB, image/png)
2018-01-01 15:27 UTC, Bertrand Bousquet
Details
Runner unit converter with a specified unit (KO) (3.90 KB, image/png)
2018-01-01 15:28 UTC, Bertrand Bousquet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bertrand Bousquet 2018-01-01 15:27:07 UTC
Created attachment 109615 [details]
Runner unit converter without specified unit

Hi,

In english and in french, I can ask krunner "100€" or "100 EUR" and I get multiple results. This is fine.

Then, in english, I can ask krunner "100 EUR in JPY" (for example) and I get the result.

But I get no results in french. I've checked the expected translations ("dans", "vers" or "comme") [1].

It could be a space and/or an encoding issue. How can I compile a *.po file to *.mo and force the runner to use my custom translation ?

Thanks.

[1] https://websvn.kde.org/*checkout*/trunk/l10n-support/fr/summit/messages/kde-workspace/plasma_runner_converterrunner.po
Comment 1 Bertrand Bousquet 2018-01-01 15:28:53 UTC
Created attachment 109616 [details]
Runner unit converter with a specified unit (KO)
Comment 2 Nate Graham 2018-01-02 16:58:30 UTC
Yes, that definitely looks like an encoding issue. Please feel free to submit a fix! Here's the documentation for how to get involved and do that: https://community.kde.org/Get_Involved/translation
Comment 3 Simon Depiets 2018-01-05 17:06:18 UTC
There was an issue in the po (translation) file, there were spaces (including non breaking spaces) around the semicolon to separate the different versions. The reason is probably due to the french convention (of spaces around semicolons) being applied too rigorously during the translation.

I've also replaced "comme" by "en" which is more natural.

https://phabricator.kde.org/R883:1507895
Comment 4 Nate Graham 2018-01-05 17:07:02 UTC
Fantastic, thank you so much!