Re: What to do for next release?
On Wed, Aug 08, 2001 at 06:08:06PM +0700, Dmitry Yu. Bolkhovityanov wrote: On Sun, 5 Aug 2001, Dominik Vogt wrote: On Sat, Aug 04, 2001 at 08:36:27PM +0700, Dmitry Yu. Bolkhovityanov wrote: BTW, would it be possible to make --enable-multibyte a default in 2.4.1? As I understand, most of the people are lucky with 8859-1, but that's not the case for us, koi8-r'ers. In most of the modern apps (Netscape is most popular) russian titles are displayed as raw 2022 strings, i.e. the titles are interweaved with koi8-r strings and 2022 escapes. (Sure, my students now better understand how i18n works in X, but I'd prefer them to use their time for other work.) Is there something critical and untested in multibyte code? The whole multibyte support is basically untested :-) I can't remember the minute details, but there are several places where internationalised strings are not yet handled. Then there was this font problem you reported a while ago. Finally, it's implemented using dozens of ifdefs all over the code. This can not be the final solution. A library like implementation like the Xinerama library is needed. This includes a font/fontlist management module that hides the details from the caller. Okay, this answers the question I haven't asked yet -- regarding antialiased text. The Xft library becomes very polular, and is already used in Qt, Gtk and some other WMs. I've skimmed through fvwm code, and it has too close relations with X core fonts. But if a dedicated library is already planned for i18n, adding support for antialiased text will be easy. Planned is perhaps not the right term. Needed urgently might be a better one. We don't have anyone here on the list who is experienced in mb support *and* willing to do the work. Bye Dominik ^_^ ^_^ -- Dominik Vogt, email: [EMAIL PROTECTED] LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20 -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: What to do for next release?
On Sat, Aug 04, 2001 at 08:36:27PM +0700, Dmitry Yu. Bolkhovityanov wrote: BTW, would it be possible to make --enable-multibyte a default in 2.4.1? As I understand, most of the people are lucky with 8859-1, but that's not the case for us, koi8-r'ers. In most of the modern apps (Netscape is most popular) russian titles are displayed as raw 2022 strings, i.e. the titles are interweaved with koi8-r strings and 2022 escapes. (Sure, my students now better understand how i18n works in X, but I'd prefer them to use their time for other work.) Is there something critical and untested in multibyte code? The whole multibyte support is basically untested :-) I can't remember the minute details, but there are several places where internationalised strings are not yet handled. Then there was this font problem you reported a while ago. Finally, it's implemented using dozens of ifdefs all over the code. This can not be the final solution. A library like implementation like the Xinerama library is needed. This includes a font/fontlist management module that hides the details from the caller. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: What to do for next release?
On 02 Aug 2001 21:29:19 +0200, Dominik Vogt wrote: On Mon, Jul 30, 2001 at 12:23:48AM +, Mikhael Goikhman wrote: On 29 Jul 2001 02:28:52 +0200, Dominik Vogt wrote: I have been thinking about the plans for the next release and about the long way we had to go for 2.4. Dan is absolutely right when he wants to find a way to establish a shorter release cycle. 2.4 took to much time and I doubt I have the endurace for such an herculean effort again. There are a *lot* of things that were postponed until after 2.4 that could be done now. All the small enhancement requests and bug fixes alone may justify another release. I believe 2.4 got out of hand because we tried to do everything at once at first and then there were too many dependencies in the code to be resolved so that we could not release although we wanted to. It may be better to plan for a 2.6 release that comes up with many small enhancements, bug fixes and maybe even some of the bigger but less disruptive features. A new stable release within half of a year semms to be a good plan to me. What do you think? If we already go for 2.6 in some months, maybe grab cvs before Xinerama commits and release 2.4.1 based on it? The current one may become 2.5.0. This is somewhat similar to what I and Olivier suggested previously. I think I don't understand what you are saying. What do you mean with maybe grab cvs before Xinerama commits and release 2.4.1 based on it? What I mean is this. If we go for 2.6 in some months, maybe we leave 2.4.x branch for fatal bugs only, move to 2.5.x betas and release 2.6.0 with Xinerama, EWMH support (both need a deep testing) and probably other not very big features just like you suggest. If you ask how to do this technically, this is another question, first we should agree whether we (you) want Xinerama in 2.4.1 or 2.6.0. Regards, Mikhael. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: What to do for next release?
BTW, would it be possible to make --enable-multibyte a default in 2.4.1? As I understand, most of the people are lucky with 8859-1, but that's not the case for us, koi8-r'ers. In most of the modern apps (Netscape is most popular) russian titles are displayed as raw 2022 strings, i.e. the titles are interweaved with koi8-r strings and 2022 escapes. (Sure, my students now better understand how i18n works in X, but I'd prefer them to use their time for other work.) Is there something critical and untested in multibyte code? ___ Dmitry Yu. Bolkhovityanov | Novosibirsk, RUSSIA phone (383-2)-39-49-56 | The Budker Institute of Nuclear Physics | Lab. 5-13 -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: What to do for next release?
On Mon, Jul 30, 2001 at 12:23:48AM +, Mikhael Goikhman wrote: On 29 Jul 2001 02:28:52 +0200, Dominik Vogt wrote: I have been thinking about the plans for the next release and about the long way we had to go for 2.4. Dan is absolutely right when he wants to find a way to establish a shorter release cycle. 2.4 took to much time and I doubt I have the endurace for such an herculean effort again. There are a *lot* of things that were postponed until after 2.4 that could be done now. All the small enhancement requests and bug fixes alone may justify another release. I believe 2.4 got out of hand because we tried to do everything at once at first and then there were too many dependencies in the code to be resolved so that we could not release although we wanted to. It may be better to plan for a 2.6 release that comes up with many small enhancements, bug fixes and maybe even some of the bigger but less disruptive features. A new stable release within half of a year semms to be a good plan to me. What do you think? If we already go for 2.6 in some months, maybe grab cvs before Xinerama commits and release 2.4.1 based on it? The current one may become 2.5.0. This is somewhat similar to what I and Olivier suggested previously. I think I don't understand what you are saying. What do you mean with maybe grab cvs before Xinerama commits and release 2.4.1 based on it? Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
What to do for next release?
I have been thinking about the plans for the next release and about the long way we had to go for 2.4. Dan is absolutely right when he wants to find a way to establish a shorter release cycle. 2.4 took to much time and I doubt I have the endurace for such an herculean effort again. There are a *lot* of things that were postponed until after 2.4 that could be done now. All the small enhancement requests and bug fixes alone may justify another release. I believe 2.4 got out of hand because we tried to do everything at once at first and then there were too many dependencies in the code to be resolved so that we could not release although we wanted to. It may be better to plan for a 2.6 release that comes up with many small enhancements, bug fixes and maybe even some of the bigger but less disruptive features. A new stable release within half of a year semms to be a good plan to me. What do you think? Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
