Bug 405645

Summary:	Source tab text field is rich-text and automatically uses ligatures
Product:	[Applications] KBibTeX	Reporter:	Erik Quaeghebeur <bugs.kde.org>
Component:	User interface	Assignee:	Thomas Fischer <fischer>
Status:	RESOLVED FIXED
Severity:	normal	CC:	auxsvr
Priority:	NOR
Version First Reported In:	0.8.2
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:	8b6edc4cfc4f3670011eb6ad7525c436aeabfdd3	Version Fixed/Implemented In:	0.9
Sentry Crash Report:

Description Erik Quaeghebeur 2019-03-19 14:21:31 UTC

SUMMARY
In the source tab, the text field is rich-text and automatically uses ligatures. This means that ligatures are introduced instead of ‘fi’, ‘st’, etc. This causes hell in LaTeX, because these ligature characters are not recognized. Even beyond that, they are unwanted. Moreover, KBibTeX should not silently change the text. Just going to another tab and coming back to the source tab is enough to make the ligatures re-appear if they had been edited away.

Also, because the text fields is richt-text, markup gets in the way when copy-pasting data from webpages.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3

Comment 1 Thomas Fischer 2019-03-19 21:06:26 UTC

This problem should be fixed both by using the powerful KTextEditor component in the source view as well as a rewrite of an Encoder class that erroneously replaced 'st' with 'ﬆ' in certain situations.

To test the latest code going towards 0.9, please have a look at the quick start instructions:
https://userbase.kde.org/KBibTeX/Development#Quick_Start_to_Run_KBibTeX_from_Git
Run the script as follows:
bash run-kbibtex.sh https://anongit.kde.org/kbibtex.git kbibtex/0.9

Please re-open the bug if the problem still persists.

Comment 2 Erik Quaeghebeur 2019-03-20 13:29:20 UTC

(In reply to Thomas Fischer from comment #1)
> This problem should be fixed both by using the powerful KTextEditor
> component in the source view as well as a rewrite of an Encoder class that
> erroneously replaced 'st' with 'ﬆ' in certain situations.
I can confirm that running latest git head fixed the issue. (Thanks)