Does your approach inherently depend heavily on Xft and
Xrender, or are they just nice extras?
NEdit has a long tradition of not adding dependencies, so if
the core UTF-8 support could be done without them it would
be a lot easier to get this into the standard distribution in the
near future.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This patch is intended to allow UTF-8 edit operations in NEdit
in truly i18n manner. No crazy codepages and such things.
There is also extended clipboard data interchange to handle
new proposed UTF8_STRING format. It works for instance
with XTerm -u8, Yudit, GNOME based apps...
Xft is way to go, w/ anti-aliasing as a bonus.
Well, there is possible to build NEdit w/o any dependencies,
just as regular one.
Makefile.li18nux can be changed to suit any situation.
There is still lot to be done, don't use it for your serious work!
More to come next month.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To get anti-aliasing support into NEdit, I tried to isolate just the Xft
portions of this patch by hand but I don't have the expertise to debug the
end result, especially since I'm trying to add these changes to 5.5.
Can you submit a patch that just contains the Xft portions applied to the
5.5 codebase?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Most of Xft related changes are in source/textDisp.c
drawString(), font selector is still not finished. There is
also remaining bug with drawing of control characters. ETA 2010.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
UTF-8 patch reloaded, this time updated to current CVS
version. Edit options in Makefile.linux. Works w/ latest
OpenMotif 2.3 as well as any other toolkit.
Almost two years later, but still experimental. There's lot
to be done right. For instance font selection should be done
by Motif toolkit, not application code. Xdnd and Motif Drag
and Drop, better handling of character expansion, et cetera.
Apply:
bzcat nedit+Unicode.diff.bz2 | patch -p1
RFC: would it be possible to use PCRE instead of libunicode
for character case change?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=197101
Interesting. Could you share with us what your patch provides?
Logged In: YES
user_id=82866
Brilliant!
Does your approach inherently depend heavily on Xft and
Xrender, or are they just nice extras?
NEdit has a long tradition of not adding dependencies, so if
the core UTF-8 support could be done without them it would
be a lot easier to get this into the standard distribution in the
near future.
Logged In: NO
This patch is intended to allow UTF-8 edit operations in NEdit
in truly i18n manner. No crazy codepages and such things.
There is also extended clipboard data interchange to handle
new proposed UTF8_STRING format. It works for instance
with XTerm -u8, Yudit, GNOME based apps...
Xft is way to go, w/ anti-aliasing as a bonus.
Well, there is possible to build NEdit w/o any dependencies,
just as regular one.
Makefile.li18nux can be changed to suit any situation.
There is still lot to be done, don't use it for your serious work!
More to come next month.
NEdit-5.4 UTF-8 patch #2
Macro to get/set Unicode mode
Various UTF-8 symbols for test purposes
Logged In: YES
user_id=109269
See Makefile.li18nux
Known issues:
Text drag is leaving garbage
NTH:
UTF-8 handling routines reimplemented in order to avoid
dependency on Fontconfig, Xft & company
Logged In: YES
user_id=109269
It might be possible to use ancient X bitmap font drawing
routines for systems w/o Xft.
TBD:
Xdbe would be good for faster text redraw.
Peter Kovř
50 65 74 65 72 20 4B 6F 76 C3 A1 C5 99
Logged In: YES
user_id=836812
To get anti-aliasing support into NEdit, I tried to isolate just the Xft
portions of this patch by hand but I don't have the expertise to debug the
end result, especially since I'm trying to add these changes to 5.5.
Can you submit a patch that just contains the Xft portions applied to the
5.5 codebase?
Logged In: YES
user_id=109269
Indeed. Sometime this week.
Logged In: YES
user_id=836812
Any news on the anti-aliasing support?
Logged In: YES
user_id=109269
Most of Xft related changes are in source/textDisp.c
drawString(), font selector is still not finished. There is
also remaining bug with drawing of control characters. ETA 2010.
Logged In: YES
user_id=109269
UTF-8 patch reloaded, this time updated to current CVS
version. Edit options in Makefile.linux. Works w/ latest
OpenMotif 2.3 as well as any other toolkit.
Almost two years later, but still experimental. There's lot
to be done right. For instance font selection should be done
by Motif toolkit, not application code. Xdnd and Motif Drag
and Drop, better handling of character expansion, et cetera.
Apply:
bzcat nedit+Unicode.diff.bz2 | patch -p1
RFC: would it be possible to use PCRE instead of libunicode
for character case change?
NEdit UTF-8 patch
Is there a new version of patch for nedit-5.7 ?