Re: Build Instructions?

On Thu, 10 Jul 2003, Helge Hess wrote:

> On Donnerstag, 10. Juli 2003, at 20:04 Uhr, Noah Silva [Mailing list]
> wrote:
>
> > Just as FYI, the reason I need to build it, instead of using .debs is
> > because I am using Debian/PowerPC.  I didn't check, but I assumed your
> > .deb files were for x86.
>
> Ah, interesting. Let us know how it turns out. We are currently porting
> OGo to the IBM iSeries platform, which also runs Linux on PowerPC. That
> didn't work out of the box, but the port should be completed next week.
> So if you encounter problems with va_arg structures, it might be worth
> waiting a bit longer instead of getting gray hair inside of GDB ;-)

Maybe I should wait for your port to be done then!  I wouldn't get to the
point of tinkering with GDB, as C isn't my "Native" language.  (I program
in Pascal/Kylix/Delphi normally, and do a good deal of tinkering in SQL,
etc., and PHP recently with messing around with the Sausalito sources).

I hope when you are done with the iSeries, you will make PPC .deb files
too ;)

> > I am happy this project was open-sourced, of course, but I am curious
> > as
> > to -why- the decision was made.
>
> There are several reasons which I cannot fully disclose ;-) One of
> course is marketing (which already was huge !). Whether the software is

I see, so it isn't that the project has reached EOL or something.  I hope
Skyrix continues to do well from the consulting business.  Some portions
that are LGPL, you might want to consider making SISSL to allow 3rd
parties to make branded releases, but without breaking basic
compatibility.
I was looking at the online demo, is the "Project" portion also
open-sourced?  My main interest was in the calendar backend for evolution,
but it looks like I have to use Connector for that right now.

> > Also, if I can understand how the internationalization was done, I
> > might
> > have time to localize it to Japanese.
>
> I would like to come back on that to you later. Japanese currently
> isn't as easy and needs some programming work as well. OGo uses Unicode
> internally but not in all places.

Even if it is stored as "Ascii", as long as it is sent in the proper
format (i.e. TELL the web-browser it is UTF8), it shouldn't matter much.
We could work on Romanjii (ASCII-ized japanese) in the meantime.

Again, thanks for your quick answers.

 -- noah silva