On 12.09.2008, at 13:17, MacArthur, Ian (SELEX GALILEO, UK) wrote:
Sometimes I'm glad I have English as my first language...
Or as an American friend recently noted: I have a hard time
understanding those Brittish. I wish they would speak proper English
like us.
ROTFL, Matthias
matthiasm wrote:
...
1: go strictly with our patch, remove duplicates, and clean up our
API
2: use the already clean GLib API and hook that up with the guts from
the patch
3: extract the unicode from GLib and replace code from the patch (but
GLib is LGPL, FLTK is modified LGPL, so I am
matthiasm wrote:
I was very excited yesterday to see the first Japanese characters on
my FLTK-for-OSX yesterday and I beleive that we are on a good path.
I'd be happy to test your build with my commercial app in Japanese.
OSX has been the one platform I haven't yet been able
OK, so I have no problem with using glib with Pango and X11/Cairo,
however glib isn't fast or light or standard outside Linux/Solaris,
so I wouldn't want to make it a dependency on other platforms. In
particular, glib on Windows still has a lot of issues...
Indeed so, and for simply
Thanks for all the suggestions. I will use a combination of 1 and 2
then. I merge the code base with the patch (done), then make all the
IDEs and Makefiles work that I can test (Linux, OSX, Xcode,
VC6, VC7,
VC8) and merge back into the trunk.
Outstanding! That was really quick...
I'd be happy to test your build with my commercial app
in Japanese.
OSX has been the one platform I haven't yet been able to run in
Japanese mode.
What! My dirty hack wasn't good enough for you then? ;-)
Cheers Greg,
--
Ian
SELEX Sensors and Airborne Systems
On 10.09.2008, at 09:45, MacArthur, Ian (SELEX GALILEO, UK) wrote:
FWIW, iconv is the usual API on Linux/UNIX systems to do character
set conversions, and Windows has its own multibyte functions - I'd
rather use those than glib, if we are going to pull in another
library...
If I understand
Understanding more and more about languages, script, glyphs, fonts,
and layouts, I realize that we can never produce a perfect UTF8
support. So let's keep it fast and light and allow rendering of all
fonts and simple text input. The existing code base is just fine for
that.
Yup - I
On 10.09.2008, at 14:52, MacArthur, Ian (SELEX GALILEO, UK) wrote:
Editing complex scripts is *hard*
Trivia:
Reading through various documentation, my own language, German, has
several pitfalls I was not aware of. Converting the word measurments
in German from lower to upper case is a
On 10.09.2008, at 21:20, Yuri wrote:
OK, so I have no problem with using glib with Pango and X11/Cairo,
however glib isn't fast or light or standard outside Linux/Solaris,
so I wouldn't want to make it a dependency on other platforms. In
particular, glib on Windows still has a lot of
Winding myself through the depths of Unicode and utf8
encoding, I have
You are in a maze of twisty passages, all exactly alike...
come across GLib. GLib is part of the GTK toolkit and incorporates
everything that the GUI part of GTK needs to work, but wihich is not
strictly GUI
On 09.09.2008, at 16:12, MacArthur, Ian (SELEX GALILEO, UK) wrote:
Anyway, GLib contains among many other features all the Unicode
handling routines we need for FLTK1. Sure, most of the stuff is
already implemented in the patch (some code even twice or three
times ;-),
Yes - sorry about
My opinion:
I would vote for 1)+2) (1 + API inspiration from GLib),
I do not like too much 3) because this would ruin static linking of fltk
for commercial applications and definitely NO to 4)
matthiasm wrote:
1: go strictly with our patch, remove duplicates, and clean up our API
2: use
Albrecht Schlosser wrote:
matthiasm wrote:
I'm not a license specialist, and I didn't look very deeply in the patch
(I did, some time ago), but nevertheless, here are my comments.
Sorry, that looks af if Matthias wrote this first sentence. That was
my text, however.
Albrecht
matthiasm wrote:
...
1: go strictly with our patch, remove duplicates, and clean up our API
2: use the already clean GLib API and hook that up with the guts from
the patch
3: extract the unicode from GLib and replace code from the patch (but
GLib is LGPL, FLTK is modified LGPL, so I am
15 matches
Mail list logo
