Activity for L.K.P.
-
L.K.P. posted a comment on discussion General Discussion
That's not the case here. XSupportsLocale returns true also with Motif-2.3.4 but nevertheless it doesn't work. I think it's because the scalable font handling in newer Motif versions supports only UTF-8 coded text.
-
The problem with the dialog boxes is really a Motif issue. It occurs with Motif-2.3.4, but not with the older Motif-2.1.32 that doesn't have scalable font support. But dialog boxes with bitmapped X11 fonts are better than boxes with nice looking but broken text . Two ideas relating to the character encoding: You are storing the encoding internally as a property of the window. Why not handle it in this way also externally for the user as an option of a window resp. tab without the selection boxes...
-
Hi Olaf, I did sent a reply per mail to the list, but it didn't appear here, so I'm entering it again througt the web interface. Please ignore it, if this same message appears again later. Thanks a lot. Not only for finding this bug, but also for the patch. The error handling is really nice. Based on that I also changed the encoding conversion in doOpen. what you also should check is the behavior with UTF-8 encoding, when strconv = copyBytes. The last call to iconv() should be one with inbuf or *inbuf...
-
Hi, I think there are still problems when not using an UTF8 locale. If you create a new file and save it, the default encoding is still UTF8. The next time you start XNEdit and want to open that file, you have to manually select the UTF8 encoding, because "detect" is not that powerful. what I have noticed is that xnedit sets the extended file attribute user.charset even if this wasn't specified in the "Save as" dialog. Should I just implement that the default charset on Save is the locale charset?...
-
Hi, great, eventually an nedit with smooth fonts and UTF8 support. But I'm still using a locale with a simple ISO character encoding. Here's a small suggestion to be able to use xnedit in a non-UTF8 locale on files without extended attributes: --- file.c.org 2019-02-24 14:24:48.000000000 +0100 +++ file.c 2019-03-27 23:15:22.053279131 +0100 @@ -57,6 +57,7 @@ #include <unistd.h> #include <ctype.h> #include <iconv.h> +#include <langinfo.h></langinfo.h></iconv.h></ctype.h></unistd.h> #ifdef VMS #include...
-
Lame doesn't recognize user locale correctly
-
I'm also an nedit user for many years. I've first installed it on an Apollo/Domain workstation, then under HP-UX and then under Linux. And you're right, it's more and more difficult to get Motif applications running under recent Linux distributions. I'm now on OpenSuse 42.3 and nedit had massive font rendering problems with the Motif 2.3.4 library. I had to go back to OpenMotif-2.1.32 to get it working again. I don't know why, but under OpenSuse 42.2, nedit worked without problems with Motif-2.3.4....
-
Sorry, I only wanted to give you a hint how to compile it, I can't help you with the cursor trace bug, Both nedit 5.6a and 5.7 are working correctly for me under OpenSuse 42.2. But it looks like a bug in one of the X libraries or the X server. Did you install all the latest OpenSuse Patches?
-
The created binary should be "source/nedit". Does is work? If not, you could try a "make clean" and then rebuild everything with "make linux".
-
Syntax highlighting overwrites characters
-
To compile nedit, just install libX11-devel, libXt-devel and motif-devel.
-
I had the same problem under OpenSuse 42.3 with OpenMotif 2.3.4. Compiling Nedit with OpenMotif 2.1.32 fixed it, the complete menu is now visible again. But this non-rectangular clipping of the menu entries is very strange. I can't imagine, how the motif library can do that.
-
Thanks, the crash is fixed in the svn version. But the trimming of 94677 frames takes a lot of time.
-
Lives 2.8.4 crashes when selecting Tools->Trim frames/Add Border...
1