http://apr.apache.org/docs/apr/1.4/apr__getopt_8h-source.html
http://svnbook.red-bean.com/en/1.5/svn.developer.usingapi.html On Sep 15, 2011, at 1:41 PM, Dennis E. Hamilton wrote: > Support for w_char matters to me, but that is unrelated to work here. > > However, there's another place to look. > > I know there are command-line utilities in Subversion releases, so I went > nosing around. There is an <apr_lib.h> reference and apr_getopt... calls. I > haven't found the library and its source yet, but I bet it might have what is > needed for Apache OOo. It might take some preprocessor magic to rename back > in a custom getopt.h file. > > I did trace back enough to know that here are some interesting places to look > further: > > <http://archive.apache.org/dist/apr/apr-1.4.5.tar.bz2> > > <http://archive.apache.org/dist/apr/apr-util-1.3.12.tar.bz2> > > - Dennis > > -----Original Message----- > From: Pedro Giffuni [mailto:giffu...@tutopia.com] > Sent: Wednesday, September 14, 2011 22:39 > To: ooo-dev@incubator.apache.org > Subject: Re: How to do with glibc-2.1.3 in AOOo? > > On Thu, 15 Sep 2011 08:06:40 +0300, Tor Lillqvist <t...@iki.fi> wrote: >>> For command line options I think the normal char is enough >> >> I don't know what the OOo code actually uses getopt() for (I am >> pretty >> sure it is just some build-time tools that actually use it...), but >> you can be assured that the actual OOo executable(s), for Windows >> (which presumably *is* the OS you expect most of your users to >> have?), >> definitely do need the full original Unicode command line. >> >> (Remember that Windows is Unicode-based, all file names and other >> system interfaces are in UTF-16.) >> >> And of course the OOo code itself uses UTF-16 strings almost >> exclusively. >> > > Indeed, I had forgotten: > > http://dvice.com/archives/2009/01/klingon_keyboar.php :) > > Cheers, > > Pedro. > >
