Bug#436469: hex-a-hop: Localization misses non-ascii chars

[Jens Seidel]

Hi Miriam,

On Mon, Aug 13, 2007 at 09:50:29AM +0200, Miriam Ruiz wrote:
> I'm sorry I haven't written back in the whole weekend, I've been some days out
> and wasn't online.

Oh, no problem. So the next patch will contain proper i18n support for
all languages :-)

> First of all, would any of you, Jens and Helge, want to comaintain the
> package? We're already maintaining it cooperatively inside the Debian Games
> Team SVN repository, so if you want, I can add you to the alioth group. Please
> tell me if you want, that way it might be easier to make changes directly in
> the SVN server instead of having to send all the individual patches to the
> BTS, one by one.

Yes, I would like it. Please note that I do not know how much time I
will invest into hex-a-hop in the future but I still have two weeks
holidays and I'm interested in internationalisation. I think I have now
already basic knowledge about the source code so I me be able to fix other
bugs in the future ...

Maybe I will switch the build system to autotools (configure, ...) to
add more cross platform support (inclusive Windows (which I cannot test
as it's non free)).

My alioth user name is jseidel-guest. What do I have to do? Subscribe to
hex-a-hop, to the mailinglists of Debian Games ...

What are the rules for the Subversion repository. Should all extensions
be put into patches in debian/patches or would it be possible to directly
apply all code changes into a branch? (I think this would simplify some
handling.)

> Second, mostly to Tom, we have already done some modifications to hex-a-hop in
> the form of patches to be applied when creating the package, but they seem to
> be increasing especially as we're taking i18n into consideration. What would
> you like to do with all those patches, would you be willing to integrate them
> in a new release of the program?

I asked him yesterday already :-)

> I guess we should start dealing on how to handle all those changes. The

Right!

> package is right now using quilt, so if I add you to add comaintainers and you
> make your commits directly into the svn server, it might be easier for all of
> us to handle the patches. Quilt makes it very easy to handle a stach of
> patches, much easier than just sending them to the BTS.

I don't know it. Need to learn it ...

> I don't exactly know how Tom is handling the management of the source of the
> program, but another possibility would be that he was integrating the patches
> in his source.

If he hasn't a source code repository whould it be possible to offer him
to work with your Subversion one? He could work on a separate branch
"upstream" (directory) where only he has access to. So it's easier for
us to test prereleases, merge code into our branch, ...

> > package (it uses a new SDLPango dependency). I also noticed that
> > SDLPango is currently comletely untested in Debian (only frozen-bubble
> > uses it), it's not even possible to include the header file in two
> > distinct object files!

Bugs are already filed. Currently I work around it.

Jens