Thread: Re: Bug#217067: Impossible to display non-European languages
> Ergo, if you reassign this to wx2.4, I'll summarily close it, > gtk2/unicode is not sufficiently supported in 2.4 to justify 'stable' > packages in those flavours, (and there is plenty of prior discussion > on that). > > Sorry Jean-Michel, but the answer is probably that you'll have to wait > for wx2.6 (the binary freeze release of 2.5) before you get this in > mainstream poedit. In the meantime, if you want bleeding edge features > you'll have to continue to build them for yourself. Dear Ron, Thank for your support. It is really motivating to see how fast you can get an answer on Debian. Your answer about poEdit mostly satisfies me. I am glad to see we share the same opinion about wx2.4. About wx2.6: we use wx2.5 unstable to build pgAdmin3, the next official GUI for PostgreSQL. You can get pgAdmin3 from http://www.pgadmin.org. deb http://www.pgadmin.org/snapshots/linux/debian unstable/testing/woody pgadmin3 pgAdmin3 is an important project for PostgreSQL. Our stats show that we have more than 2000 new users everyday with a minimum user base of 100.000 users. pgAdmin is being translated into 40 languages. It is based on Unicode and supports PostgreSQL unicode databases. This user base makes it possible for us to detect and fix the main Unicode bugs in wx. As a result we publish our own version of wx, until the fixes are integrated in wx. Whenever you prepare wx2.6, we would appreciate to discuss before releasing it on Debian. To make sure that a working wx2.6 version is used. Could you point me out the Debian list where the wx stuff is discussed? Best regards, Jean-Michel
I've trimmed the cc list to something a bit more appropriate for this. On Thu, Oct 23, 2003 at 09:37:23AM +0200, Jean-Michel POURE wrote: > This user base makes it possible for us to detect and fix the main Unicode > bugs in wx. As a result we publish our own version of wx, until the fixes are > integrated in wx. > > Whenever you prepare wx2.6, we would appreciate to discuss before releasing it > on Debian. To make sure that a working wx2.6 version is used. You will _really_ need to get your fixes into 2.5 well before 2.6 is released. The first release of 2.6 will mandate a freeze on binary incompatible changes to that branch and all but the most obvious and safe bugfixes will have to go into 2.7 after that. If pgadmin does not work with an unpatched 2.6 then you are going to be in a world of pain wrt to distributing it in Debian (and probably the other distros too, though I can't speak for them). We had a major disaster when 'stable' wxPy released depending on the unstable wx2.3 and I'll not be keen to repeat such an episode, even for an app as important as you indicate pgadmin to be. My best recommendation would be that you get an idea (from wx-dev) of when people would like to see 2.6 frozen (the borland thing will surely be pushing this in ways the code alone might not mandate) and then work very hard to see that all your important patches are incorporated in one way or another before then. I have a responsibility to the maintainers of other wx-using apps to be extremely hesitant to accept any patches that aren't in cvs for inclusion in the .debs. Not only might it break their compatibility on other platforms, but it might break their app entirely with no chance for prior testing. The bottom line basically is that either you guys will need to fork wx entirely and support your own version, or work to merge your branch with the mainstream before the stable release is made. Sorry, but as much as I'd love to help you guys get your app into the next Debian stable release, I just can't make the .debs a leverage point for patches that haven't been accepted into cvs yet. If you want them in the 2.6 debs, you're going to have to get them past the gauntlet of wx-dev first. > Could you point > me out the Debian list where the wx stuff is discussed? There isn't one as such, (other than wx-dev) but I have a cc list of the wx app maintainers that I usually post to when I'm about to change anything controversial, or when it all hits the fan in a big way. The last time it got used was for the what to do about gtk2 question. I'm not sure if any of this helps you at all, but I hope it sheds a bit of light on the path to follow. cheers, Ron
Dear Ron, > If pgadmin does not work with an unpatched 2.6 then you are going to > be in a world of pain wrt to distributing it in Debian (and probably > the other distros too, though I can't speak for them). Of course. Please note that we never intended to get our patched version into Debian. > My best recommendation would be that you get an idea (from wx-dev) > of when people would like to see 2.6 frozen (the borland thing will > surely be pushing this in ways the code alone might not mandate) > and then work very hard to see that all your important patches are > incorporated in one way or another before then. Borland is a company. PostgreSQL is a community. I hope you prefer PostgreSQL to Borland. Therefore, 2.6 cannot be frozen before it incorporates Andreas Pflug patches, which will probably be the case sooner or later. > The bottom line basically is that either you guys will need to fork > wx entirely and support your own version, or work to merge your > branch with the mainstream before the stable release is made. We do not intend to fork wx and never will. > Sorry, but as much as I'd love to help you guys get your app into > the next Debian stable release, I just can't make the .debs a > leverage point for patches that haven't been accepted into cvs yet. > If you want them in the 2.6 debs, you're going to have to get them > past the gauntlet of wx-dev first. Let's wait for wxWindows to manage Unicode and aother issues. All patches are available for inclusion into wx main branch: http://snake.pgadmin.org/snapshots/wxwindows/patches/ The goal of Debian is to be a world distribution. We all have the same goals: proper Unicode management, working Cut/Paste, etc... For example, work is being done by the wx team on RTL better support. Everyone is working in the same direction, there is no idea of a "fork" and we never intended so. But, only one thing : please, publish wx26, poEdit and pgAdmin3 in Debian at the same time. Everyone will benefit from it. Best regards, Jean-Michel
Jean-Michel POURE wrote: > All patches are available for inclusion into wx main branch: May I suggest that it's sometimes not enough that patches "are available"? That some of them may need (judging from comments under #776217 and #816019) a bit of further work to be ready for inclusion? Vaclav -- PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x465264C9