| Summary: | \textonequater gets inserted instead of 6 or ^ at random times! (win7) | ||
|---|---|---|---|
| Product: | [Applications] kile | Reporter: | Peter <peter.vandendriessche> |
| Component: | user interface | Assignee: | Michel Ludwig <michel.ludwig> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 2.1b5 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Oops, reproducibility should be always reproducible, it seems I forgot to fill that in. Sorry, but I can't reproduce this here. Did you change any options so far? Also, did you choose the MSVC or MinGW version in the installer? And what keyboard layout do you use? I picked the standard compiler, I think that is MSVC. You actually hit the nail on the head with that keyboard lay-out: if I pick another keyboard layout, it's not reproducible anymore! Being a linux fan (but forced to work under windows) I use this keyboard layout: http://code.google.com/p/usialtgr/ Please try it with this lay-out. Indeed, with the standard US or US-international lay-out in windows, I could not reproduce it. Also, this does not happen under other programs: a 6 or ^ always gets printed as a 6 or ^, never as any weird sign (which I assume is what happens here -- a nonstandard sign being replaced by \textonequater?). Does the problem disappear if you disable the "Automatically insert the LaTeX equivalent of special characters" functionality in the configuration dialog under LaTeX/General? Yes. When I disable that feature, the problem does not trigger: a 6 or ^ gets printed correctly. I thought about this problem, but I don't think that Kile is actually at fault here. :-) Kile inserts '\textonequator' because it gets notified that this 'key' has been pressed. So, I reckon this is either a problem with Qt or with the keyboard layout software you have mentioned. Could you maybe contact the authors of the keyboard layout software and point them to this bug report? It would be interesting to see what they think about it. Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone! Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |
Version: 2.1b5 (using KDE 4.5.4) OS: MS Windows On windows 7, I use KDE for windows to run Kile. This works fine but there are some problems with it, which I will report here, in a split topic for each. A very weird bug is the following one. It is reproducibly by simply opening Kile (auto-loading your last document), and pressing the key with 6 and ^ on it. Instead of a 6 or a ^ (depending whether or not you held shift), it will print a \textonequator, and throw an error message: [Missing Package] You have to include the package textcomp to use \textonequarter. This phenomenon appears at random other times as well, making it quite annoying -- the above is simply a way to reproduce it. It only appears with this key (regardless whether 6 or ^ is used) and always the same command and error. Reproducible: Didn't try Steps to Reproduce: It is reproducibly by simply opening Kile (auto-loading your last document), and pressing the key with 6 and ^ on it. Actual Results: Instead of a 6 or a ^ (depending whether or not you held shift), it will print a \textonequator, and throw an error message: [Missing Package] You have to include the package textcomp to use \textonequarter. Expected Results: Type 6 or ^ instead of \textonequarter