-
|
When syntax highlighting is enabled, and the current document is a new one, shouldn't s.h. not work? But it seems like in this case, if I type Japanese or Korean, text becomes dim. Is this an intended feature, or a bug of FeatherPad or Fcitx5 (the IME)? Screencast_20240504_012007.webm |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 12 replies
-
The default syntax highlighting is that of URL, and it works with a new document. Type I don't know how Asian texts work, but your video shows that the text is OK in the end. The reason it's gray at first may be that highlighting hasn't finished yet, waiting for the final text. |
Beta Was this translation helpful? Give feedback.
-
|
I don't know why all Asian text's input in composition should match the URL pattern. Seems like a bug. Also, it seems that it happens with all the text in the line before the current composition from line two. This is very distracting. Screencast_20240504_025906.webmIf fixing this is difficult, I wish I could disable URL highlighting. Actually, URL lighting has been in general problematic for me because I could accidentally click the URL when trying to select the text. |
Beta Was this translation helpful? Give feedback.
-
|
Seems like it's caused by "Show whitespace" and "Also show line ends". It's just that disabling syntax highlighting disables those whitespaces, too. |
Beta Was this translation helpful? Give feedback.
-
They don't need to match; the highlighter should wait to see what the final text is.
Yes. But it isn't a bug. It's how whitespaces are made gray: the whole text is gray before highlighting, and the real text gets real colors after it, leaving the whitespaces. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe it's not a bug technically, but in users' perspective, I think this shouldn't be a desirable behaviour. I guess I could just disable whitespace options. |
Beta Was this translation helpful? Give feedback.
-
URLs aren't launched when clicked; |
Beta Was this translation helpful? Give feedback.
-
I understand. Why Fcitx5 interrupts text processing, I have no clue. |
Beta Was this translation helpful? Give feedback.
-
I agree, but I doubt that it can be in FeatherPad. A coder who knows Asian texts in addition to Qt coding may have a solution — typing what's in your videos is beyond me ;) |
Beta Was this translation helpful? Give feedback.
-
FeatherPad doesn't get Asian words; Qt does.
KWrite uses KDE libraries for text processing, while FeatherPad uses Qt. Using KDE libraries in FeatherPad is not an option. |
Beta Was this translation helpful? Give feedback.
-
|
OK, this is definitely a Qt bug. In FeatherPad's code, I left the text to be painted by Qt completely, instructed Qt to show whitespaces, copy-pasted a Korean text from the Internet (whose meaning I don't know), and added a single space to its beginning. This is what happened:
As you see, the whitspace is positioned incorrectly. I can't report this to Qt because I know nothing of Asian languages; you can't report it either because they need a sample code (please note that I don't have a sample code — I just made FeatherPad's code leave it to Qt). Unless it's already reported, Qt devs don't seem to know about it (apparently, there's no one among them with a knowledge of Asian languages). The problem might have been fixed in a KDE library by a contributor at some point. |
Beta Was this translation helpful? Give feedback.
-
|
There is another text editor written in QT, although it's QT5: Notepadqq. It doesn't seem to have a problem with Korean, although it did not recognise the Japanese full-width space as whitespace. It probably isn't using KDE, so maybe you could refer to its code.
|
Beta Was this translation helpful? Give feedback.
-
All KDE apps are also written in Qt. Qt has so many classes. FeatherPad uses QPlainTextEdit because it's lightweight and fast. The problem is there. There are other classes for showing and editing text (like QTextEdit), but they aren't for lightweight text/code editors. |
Beta Was this translation helpful? Give feedback.
-
|
Quoting from notepadqq/notepadqq#873: Notepadqq is "very RAM hungry because it's practically running a browser in which to display the text." |
Beta Was this translation helpful? Give feedback.
They don't need to match; the highlighter should wait to see what the final text is.
Yes. But it isn't a bug. It's how whitespaces are made gray: the whole text is gray before highlighting, and the real text gets real colors after it, leaving the whitespaces.