Re: [LyX/master] Add support for IM attribute specification over multiple segments
Scott Kostyshak <[email protected]> Sun, 14 Jun 2026 12:59:44 +0200
| Newsgroups | gmane.editors.lyx.devel |
|---|---|
| Message-ID | <ai6JV6LxiVQSztue@jimmy> |
On Sun, Jun 14, 2026 at 11:13:31AM +0200, Kornel Benko wrote: > Am Sun, 14 Jun 2026 05:04:06 +0000 > schrieb Koji Yokota <[email protected]>: > > > commit f198a3847c685e29565ffb952caf7870ba45bc60 > > Author: Koji Yokota <[email protected]> > > Date: Sun Jun 14 13:57:45 2026 +0900 > > > > Add support for IM attribute specification over multiple segments > > > > Although QInputMethodEvent documents that there should be at most one > > text format attribute specified on each segment, the de-facto standard > > seems different. LyX allowed duplicate attribute specification segment > > by segment so far. This fix extends it to allow overwrapped > > specification over segments. > > > > Eg. existing attribute [ seg ] [charFormat for a segment] [seg] > > incoming attribute [ <------ charFormat over segments ------> ] > > --- > > src/frontends/qt/GuiInputMethod.cpp | 192 ++++++++++++++++++++++++++++-------- > > src/frontends/qt/GuiInputMethod.h | 3 +- > > src/frontends/qt/GuiPainter.cpp | 4 +- > > 3 files changed, 155 insertions(+), 44 deletions(-) > ... > > Now I get the attached. Interesting, I can't reproduce. Maybe a difference in versions? $ g++ --version g++ (Ubuntu 15-20250404-0ubuntu1) 15.0.1 20250404 (experimental) [master r15-9193-g08e803aa9be] $ clang++ --version Ubuntu clang version 20.1.2 (0ubuntu1) Scott -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel
signature.asc
(application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEMfkICpsJzYuNuGlOA4ZnarZHC+sFAmouiaAACgkQA4ZnarZH C+uP5Qf9F6wX1a1iVlIB0I5i/SZgPUYXbZk91HYXieEs4JQiP3OwEPgp/oq3E2II lgBipOL8stgbIlxAdhsUKCF6/ujmuBgPcmoH8NDOwQxYYFcyscYpoCbpD/OnSpxs rDc4c8+rAUSN8/6K5fk1oQt3algG5LACM91pGlAugKOSBzZGU5lHW4iYW0Qkcxv+ Ry7vcWILptWg+ljMlIa6DAUnIpFjd35aYM+/Bk5PJGb9UxKLg4kfxwKe9EX1GQak DMU9NuGMd6O3kBFesAAB8NKYpD/oxYb2s6Pd9AiGwViAY85q4GXTEHS7g4tHJI/G 6GMLMbf6Ua4jsDmTw0iu7PIcQPW61A== =PPCK -----END PGP SIGNATURE-----