|
From: Jarek C. <jar...@po...> - 2012-08-26 08:07:54
|
W dniu 08/26/2012 06:15 AM, Mike Maxwell pisze: > I would like to do that, since the new behavior makes it impossible to > copy a diacritic from one character (say, an a+acute) and pasting it > onto another character (resulting in, for example, an > e+acute)--something which I do often. Hi Mike This is the original bug that started cursor movement changes: https://sourceforge.net/tracker/index.php?func=detail&aid=3040720&group_id=588&atid=100588 (there is a lot of info and links there) First idea of fixing the bug was to have arrows move by a codepoint. Final decision was to go a step farther and move by combined characters. Definitely old behaviour was wrong, but seems like codepoint operations are also desired. They will never cause data corruption, what was the case in character operations (see the bug). As I understand the main problem, it is inserting codepoints like accent sign. One has no such character on the keyboard. So the most straightforward solution is copying and pasting it, like Mike used to do. Other possibilities are: 1. having a macro that inserts accent sign 2. using character map 3. copying only complete characters; that is if you want a+acute find it and copy, don't use e+acute to produce a+acute None of the 3 solutions seems to be as flexible as copying and pasting combining characters, although they are possible workarounds. It seems like a good idea to allow for codepoint movements and editions though. Jarek |