[openbeos] Re: StyledEdit news of various interest

Okay, now that I've shown my ignorance of C vs. C++ linking, I'll try again.
It sounds like we agree to put the CharacterSet and CharacterSetRoster
code in libtextencoding.so.  I will keep the current method of creating the
CharacterSet objects in source.  I will separate the creation code from the
object code though, like it should be.

So, I'm trying to figure out where to put these files in cvs.  convert_to_utf8
and convert_from_utf8 are grouped into the Support Kit by the
BeBook.  As such, the files could go in current/src/kits.  Anyone have a
better alternative?  Also, the CharacterSet.h would presumably go into
current/headers/os/support? or perhaps current/headers/private/support?
UTF8.h is in current/headers/os/support.

Axel is right about iconv being part of glibc.  glibc is LGPL, and so is
iconv.  Somewhere in the back of my mind I thought iconv used to be
pure GPL, but I was wrong.  However, I'm still fuzzy on what's okay
with LGPL and what's not.  (I Am Not A Lawyer, and so I just want
someone official to say it's okay.)  Perhaps we can have a FAQ or
something on licensing issues and get a final say on LGPL.

It was my intention to include iconv from libtextencoding.so and to
implement the major bulk of the heavy lifting by simply calling to
iconv.  Depending on the interface to iconv, which I am not very
familiar with, it may be more desirable to create new conversion
functions that could be more useful than the convert_to_utf8 and
convert_from_utf8 functions.  (libiconv has some direct conversions
which could be much faster and/or less lossy)  I can take a look at
this but I'd like to have a green light on iconv first, of course. :-)

Andrew

Other related posts: