Egbert Hinzen wrote: > > Hi! > > First my thanks to all who helped to make a great game! > > After not-looking at CF for years, I saw you finally call it "1.0.0" now. > Maybe that was a little too optimistic... > > Questions > ========= > 1.) How can I use the new sound system? > Looking at the client's README it should be done automatically... > (I use Linux 2.4.5 with ALSA sounddrivers 0.5.11) > 'cfsndserv' is compiles without problems but doesn't play sounds... > BTW: The old system runs without any problems. Can't really help. I don't use ALSA, so this is not a problem I can really investigate/fix. I got it to the point where it at least compiles with ALSA, but that was on a remote system where it is hard to verify that there is actual sound output. > > 2.) How can I build the 1.0.0-documentation? > There was no way to build handbook (ps) or spoiler (ps or html) > using the Makefiles. > (Yes, I installed all needed programs including the arch-files > not needed for new users 8-)). > BTW: I also found *no* place where I could download them. 8-( cd doc; make spoiler.ps; make handbook.ps Yes, not very well documented. The latex file are probably basically unsupported at this point (I don't think/know that any of the developers know latex very well, and I don't think anyone really wants to learn). There are also the html docs, which of course are not as good for printing, but if those are broken, someone may be more willing to look at the problem and fix it. > > 3.) Everytime I start the (GtK-)client it starts my (dial-up)-internet- > connection (also offering my localhost). That's nice, but there should > be the possiblity just to use my localhost. > I tried "-server localhost", but that changed nothing. That has been fixed for future releases (you can turn off the client trying to contact the metaserver). the logic of trying to contact the metaserver is not spelled out that well, but basically, if the server supplied matches the compiled in default server, it tries to contact the metaserver. You can likely fix this by doing -server 127.0.0.1 (which amounts to localhost, but string name is different). Also, if your system actually has a real name beyond localhost, you can use that. > > 4.) Do you have plans to add localization to CF? > If so, I'll offer my help to make a German translation... I don't think there are any plans. This gets a little trickier in that a lot of the messages/names come from objects, not code. Done properly, localization should purely be a client issue (ie, connecting to an american server, I should be able to tell my client I want german as my language). This also gets a bit harder. But probably the bigger reason this won't get done anytime really soon is that for most people, this is not a high priority issue or something they want to spend time on.