> Well, the problem with Σ is whether the letter is at the end of a word or > inside a word; otherwise it would be unique.
Correct, but since the case change is only done on the selection it may not be able to tell end of word when just a contiguous sequence of word characters is selected (which is also the default if there is no selection) since then the selection contains nothing to indicate end of word, or similarly if only one character is selected. > But I agree that it is sufficient to restrict it to the ASCII subset. Yeah, IIUC most coding is done in English since the common (programming) languages have English keywords and in older languages identifiers are limited to ASCII. The use-case of Geany's "Toggle case" is lost in the mists of time but I would guess its to correct shift key errors (on English keyboards many operator characters are shifted, so shift key lead/lag capitalises the previous/next character too) like `misseD(` and `*Missed`. I would guess non-ASCII use would only be in documentation or translations, and I'm not sure how often it would be used then, so it should be ok to leave it unrestricted since (hopefully) the edge cases won't happen very often. > A formulation in English would perhaps be "cycle case".... Of the editors/IDEs I have here only Geany has a "toggle case", Scite and Eclipse have "to upper" and "to lower" as two commands and Xed, Gedit, Vscode have no case handling. I think "toggle case" comes from word processors, certainly MS Word and Libre Office have "toggle case" (as well as "upper case" and "lower case"). I don't think inventing a new term is really necessary, and "toggle case" is pretty entrenched, all the translations would need to be changed, but if somebody makes a PR it might be considered. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3336#issuecomment-1315335379 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/issues/3336/[email protected]>
