Bug 360959 - French special character/letter not recognize in kmail
Summary: French special character/letter not recognize in kmail
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: mail (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-25 08:02 UTC by toine.p
Modified: 2018-02-01 09:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description toine.p 2016-03-25 08:02:28 UTC
Hi,
I use french keyboard (all my system is in french).
We have special character like "é", or "à" etc...
These are well recognize in kde in general, but not in kmail and all kontact modules in general.
When I type those special characters, I got "é", "@".

It looks related to encoding or layout, but I am not finding what to change and where to configure. 

My platform is fedora 23 with KDE.
Kdepim is 4.14.10
All other modules for KDE are KF5 (don't know if the issue can come from there).

Thank you




Reproducible: Always

Steps to Reproduce:
1.write a new mail
2. type any special french characters
3.

Actual Results:  
"é", "@" ... 

Expected Results:  
"é", "à", ...
Comment 1 Denis Kurz 2017-06-23 21:31:25 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those Framework-based versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-02-01 09:52:10 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.