[okteta] [Bug 444453] The last character encoding combobox entries are unreachable by scrolling

2022-02-21 Thread Friedrich W. H. Kossebau
https://bugs.kde.org/show_bug.cgi?id=53

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/util
   ||ities/okteta/commit/95c1bdb
   ||937e06130b2a4c97f8981aef4d4
   ||96e0bf
   Version Fixed In||0.26.7
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Friedrich W. H. Kossebau  ---
Git commit 95c1bdb937e06130b2a4c97f8981aef4d496e0bf by Friedrich W. H.
Kossebau.
Committed on 21/02/2022 at 19:33.
Pushed by kossebau into branch '0.26'.

Implement own IBM874 codec, as Qt with ICU uses instead TIS-620
FIXED-IN: 0.26.7

M  +1-0core/CMakeLists.txt
M  +5-1core/codecs/charcodec.cpp
A  +88   -0core/codecs/ibm874charcodec.cpp [License: LGPL(3+eV)
LGPL(v3.0) LGPL(v2.1)]
A  +40   -0core/codecs/ibm874charcodec.hpp [License: LGPL(3+eV)
LGPL(v3.0) LGPL(v2.1)]
M  +1-1core/codecs/textcharcodec.cpp

https://invent.kde.org/utilities/okteta/commit/95c1bdb937e06130b2a4c97f8981aef4d496e0bf

-- 
You are receiving this mail because:
You are watching all bug changes.

[okteta] [Bug 444453] The last character encoding combobox entries are unreachable by scrolling

2021-10-26 Thread Friedrich W. H. Kossebau
https://bugs.kde.org/show_bug.cgi?id=53

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #1 from Friedrich W. H. Kossebau  ---
Hi, thanks for the report.

I can confirm the duplicated entry. Seems Qt broke here when switching to using
ICU as backend, and request for TIS-620 and IBM874 are now both getting the
same codec back. Meh. And seems there is quite some confusing naming for
confusingly many variants of encodings for Latin/Thai. And Qt's code to connect
to libicu is rather oversimplifying things, just caring for MIME and IANA
naming now. Guess I have to escape into a custom codec then. Will think about
the next days.

I can also reproduce the error. That seems a bug in Qt, which also happens when
adding a different data and icon to each entry, while using the same string.

Ideally someone should file that bug with them.

But once the charset duplication is fixed, should not bother us here.

-- 
You are receiving this mail because:
You are watching all bug changes.