Bug#243373: non-breaking spaces

2006-06-07 Thread Colin Watson
On Mon, Apr 19, 2004 at 01:34:20PM -0400, Joey Hess wrote: > This is related to bug #189026 on debconf. The problem is that leading > spaces are eaten both in Default: lines in the templates file, and in > the SET command in the debconf protocol. We really need a solution that > deals with all of t

Processed: Re: Bug#243373: non-breaking spaces

2004-04-24 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reassign 243373 libnewt0.51 Bug#243373: newt frontend replaces any line starting with a non-breaking space with a blank line, unless in utf-8 locale Bug reassigned from package `cdebconf' to `libnewt0.51'. > thanks Stopping processing here. Please co

Bug#243373: non-breaking spaces

2004-04-24 Thread Denis Barbier
reassign 243373 libnewt0.51 thanks On Wed, Apr 21, 2004 at 04:34:02PM -0400, Joey Hess wrote: > Anton Zinoviev wrote: > > On 19.IV.2004 at 20:40 (-0400) Joey Hess wrote: > > > > > > Actually, the only way I can get it to work there is by > > > setting LANG=C.UTF-8, and belive me, that looks very

Bug#243373: non-breaking spaces

2004-04-21 Thread Joey Hess
Anton Zinoviev wrote: > On 19.IV.2004 at 20:40 (-0400) Joey Hess wrote: > > > > Actually, the only way I can get it to work there is by > > setting LANG=C.UTF-8, and belive me, that looks very funky. > > I also reproduced this. It seams as if utf8 is hardcoded somehow in > the newt frontend. Th

Bug#243373: non-breaking spaces

2004-04-20 Thread Anton Zinoviev
On 19.IV.2004 at 20:40 (-0400) Joey Hess wrote: > > Actually, the only way I can get it to work there is by > setting LANG=C.UTF-8, and belive me, that looks very funky. I also reproduced this. It seams as if utf8 is hardcoded somehow in the newt frontend. The text frontend works fine. Anton Z

Bug#243373: non-breaking spaces

2004-04-19 Thread Joey Hess
Anton Zinoviev wrote: > Anyway, using non-utf-8 terminal with C.UTF-8 locale is a bad idea. > If the terminal is non-utf and the locale is C.UTF-8 then we may use > only ASCII symbols. > > Or probably unset the LANG environment variable? Thus cdebconf (and > its frontends) will know that the termi

Bug#243373: non-breaking spaces

2004-04-19 Thread Anton Zinoviev
On 19.IV.2004 at 13:34 (-0400) Joey Hess wrote: > > Non-breaking spaces seem like a more palatable workaround from this > new perspective. So we're back to why does cdebconf blank out entire > lines if they start with a NBSP and it's not at a utf-8 terminal? What is the behaviour of the text fro

Bug#243373: non-breaking spaces

2004-04-19 Thread Joey Hess
This is related to bug #189026 on debconf. The problem is that leading spaces are eaten both in Default: lines in the templates file, and in the SET command in the debconf protocol. We really need a solution that deals with all of these, and right now using escaped characters (\t, \n, \s or '\ ') s

Bug#243373: non-breaking spaces

2004-04-18 Thread Martin Michlmayr
clone 243373 -1 retitle -1 Cannot give partition to be formated a mount point or file system thanks * Joey Hess <[EMAIL PROTECTED]> [2004-04-16 19:45]: > AFAIK it's only a cosmetic problem. In which case my original report contains two different issues, both important. -- Martin Michlmayr [EMAI

Bug#243373: non-breaking spaces

2004-04-16 Thread Martin Michlmayr
* Joey Hess <[EMAIL PROTECTED]> [2004-04-16 19:45]: > I have seen the behavior you describe when I tried to use a hurd > partition as a linux root filesystem, iirc. Well, my partitions are normal Linux partitions, and they definitely worked with and older version of partman. -- Martin Michlmayr [

Bug#243373: non-breaking spaces

2004-04-16 Thread Joey Hess
Martin Michlmayr wrote: > * Joey Hess <[EMAIL PROTECTED]> [2004-04-14 14:32]: > > Partman needs to stop using non-breaking spaces. I thought I had this fixed, > > but Anton put the non-breaking spaces back in: > > Just to clarify: is this just a display problem, or does this also > explain why onc

Bug#243373: non-breaking spaces

2004-04-16 Thread Martin Michlmayr
* Joey Hess <[EMAIL PROTECTED]> [2004-04-14 14:32]: > Partman needs to stop using non-breaking spaces. I thought I had this fixed, > but Anton put the non-breaking spaces back in: Just to clarify: is this just a display problem, or does this also explain why once I choose a partition and go to "fo

Bug#243373: non-breaking spaces

2004-04-15 Thread Anton Zinoviev
On 14.IV.2004 at 15:54 (-0400) Joey Hess wrote: > Anton Zinoviev wrote: > > On 14 April 2004 (Wednesday) at 14:32 (-0400) Joey Hess wrote: > > > > > > I think the default option may need to have the leading space escaped so > > > it looks the same as what is in the choices list. So you'd have: > >

Bug#243373: non-breaking spaces

2004-04-14 Thread Joey Hess
Anton Zinoviev wrote: > On 14 April 2004 (Wednesday) at 14:32 (-0400) Joey Hess wrote: > > > > I think the default option may need to have the leading space escaped so > > it looks the same as what is in the choices list. So you'd have: > > > > Choices: \ a, \ b, \ c > > Default: \ b > >

Bug#243373: non-breaking spaces

2004-04-14 Thread Anton Zinoviev
On 14 April 2004 (Wednesday) at 14:32 (-0400) Joey Hess wrote: > > I think the default option may need to have the leading space escaped so > it looks the same as what is in the choices list. So you'd have: > > Choices: \ a, \ b, \ c > Default: \ b I tried different ways with escaped spa

Bug#243373: non-breaking spaces

2004-04-14 Thread Joey Hess
Partman needs to stop using non-breaking spaces. I thought I had this fixed, but Anton put the non-breaking spaces back in: - definitions.sh (debconf_select): convert the first space in the options to non-break space as otherwise the default options is ignored if it starts with spa