Re: New speakup-udeb component

[Samuel Thibault]

Hello,

Frans Pop, le Mon 14 Jul 2008 20:04:48 +0200, a écrit :
 On Saturday 28 June 2008, Samuel Thibault wrote:
  Attached are the patches against rootskel and finish-install which I
  could test with success (provided the patch from bug #479227 is applied
  to kernel-wedge and the speakup module be added to
  linux-kernel-di-*-2.6)
 
 I've just committed these patches in SVN with minor changes for coding 
 style [1]. It would be great if you could do a final test using a custom 
 build that includes the now committed changes

Done so, it seems to work fine.  BTW, on
http://wiki.debian.org/DebianInstaller/Accessibility
I've put the steps to test it thanks to the dummy driver.

 and then we can discuss for which architectures and in which images to
 actually include the speakup modules.

Well, I don't think there is any architecture which shouldn't be
supported, except s390 on which speakup doesn't even compile.  As for
the images, I guess we can for now include it on the same images as
brltty, that would make things coherent (i.e. accessible images).
I have attached a documentation patch.

Samuel
Index: build/boot/x86/f8.txt
===
--- build/boot/x86/f8.txt   (r�vision 53932)
+++ build/boot/x86/f8.txt   (copie de travail)
@@ -12,6 +12,7 @@
 Force static network config 0fnetcfg/disable_dhcp=true07
 Set keyboard map0fbootkbd=es07
 Use Braille tty 0fbrltty=driver,device,texttable07
+Use Speakup 0fspeakup.synth=driver07
 Use high contrast accessibility theme   0ftheme=dark07
 Select the kde or xfce desktops 0fdesktop=kde07
 

Bug#488494: cdebconf: Make the dark theme even more readable

[Samuel Thibault]

Frans Pop, le Tue 15 Jul 2008 12:58:02 +0200, a écrit :
 On Monday 30 June 2008, Samuel Thibault wrote:
  Oops, I should have explained indeed: I just meant that we won't get
  bright colors (e.g. real white) in bterm until bogl gets fixed, i.e.
  even if the cdebconf part is fixed, the result will be hindered by the
  bug of bogl.
 
 OK, but that means that it does not actually block the change in 
 cdebconf. That can be uploaded as is.

Ah, yes.  The comment on
http://www.debian.org/Bugs/server-control.en.html
could probably be more clear on that.

 There is one thing that I noticed. If you tab from a selected item in a 
 list to the GoBack button, the selected item gets a blue background. This 
 does not seem to really fit with the theme as a whole.
 Some (distinguishable) color difference should be preserved though. In the 
 default theme the background of the selected item changes from red to 
 blue (against a white window background).
 
 Could you have a look at that Samuel?

I had already actually.  The problem is that the background color is
technically limited to the dark palette, i.e. black, gray, and dark
colors.  Setting the background of the selection to black is obviously
not correct unless we change the foreground color, but I'm afraid only
changing the foreground color does not provide enough contrast.  Leaving
it gray provides confusion about what currently has keyboard focus.
That's why I left it blue, which lets the user know which element is
selected, but still be different from gray, for less confusion.

I don't know if another color would fit better, anybody on the list
would have an idea?  To test, just boot the mini-ISO on
http://brl.thefreecat.org/mini.iso
press tab, and type theme=dark

Samuel



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#488494: cdebconf: Make the dark theme even more readable

[Samuel Thibault]

Frans Pop, le Tue 15 Jul 2008 18:17:16 +0200, a écrit :
  I don't know if another color would fit better, anybody on the list
  would have an idea?
 
 Are there any colors that are bad because they look like grey to some 
 colorblind users?

I've no idea, that's why I ask for people on debian-accessibility to
test :)

Samuel



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Software speech in Debian installer

[Samuel Thibault]

(Cc-ing debian-boot as well)

Zachary Kline, le Tue 15 Jul 2008 10:21:27 -0700, a écrit :
 I was wondering about any possibility of putting software speech of some 
 kind into the Debian installer along with Speakup.  I realize it isn't a 
 trivial undertaking,

Just to copy-paste what I've said on the speakup mailing list:

« The trade-offs are about e.g disk usage and also which speech
synthesis we should enable, how to choose the language, etc.  Not a
trivial question like juste modprobing speakup_driver and voilà ;) »

And now that I'm thinking about it again, it's not only the soft synth,
but also sound drivers that would need to go into the debian installer
images...

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#488494: cdebconf: Make the dark theme even more readable

[Samuel Thibault]

Frans Pop, le Tue 15 Jul 2008 18:17:16 +0200, a écrit :
 Are there any colors that are bad because they look like grey to some 
 colorblind users? If not, I think I'd personally prefer dark red over 
 dark blue with dark grey.

For people on the list to test it, I've put a second mini.iso on
http://brl.thefreecat.org/mini-red.iso

Samuel



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Make syslinux beep?

[Samuel Thibault]

Hello,

There was no answer from debian-boot on this request:

Samuel Thibault, le Thu 19 Jun 2008 11:08:32 +0100, a écrit :
 It is a bit hard for blind people to know exactly when they can type
 boot options for the installer.  It would be helpful that syslinux beeps
 when it is ready to get input.  What do people think about it?

So would people consider it a problem that debian installation CDs make
a beep at syslinux stage by default?  It's just a matter of adding a ^G
in the menu title for instance.

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Make syslinux beep?

[Samuel Thibault]

Frans Pop, le Thu 17 Jul 2008 07:15:38 +0200, a écrit :
 On Thursday 17 July 2008, Samuel Thibault wrote:
  Samuel Thibault, le Thu 19 Jun 2008 11:08:32 +0100, a écrit :
   It is a bit hard for blind people to know exactly when they can type
   boot options for the installer.  It would be helpful that syslinux
   beeps when it is ready to get input.  What do people think about it?
 
  So would people consider it a problem that debian installation CDs make
  a beep at syslinux stage by default?  It's just a matter of adding a ^G
  in the menu title for instance.
 
 IIRC correctly it has been discussed before and was rejected as to 
 annoying for the normal case. I must say I agree with that.

I do agree it is annoying, but as Sebastien said, it's just about
installation.  I've asked a few people, they said they wouldn't complain
if it could help others.

 Especially as there's not that much magic involved in booting from CD: 
 just waiting for some time and hitting enter should also work.

How much time?  The BIOS may sometimes take quite long to boot...
What blind people currently do is waiting for hearing the CD spinning
down, but that's not always feasible, e.g. on a laptop, and they end
up booting, waiting for a few minutes, and then hope that it's at the
syslinux prompt, then type the magic stuff (with qwerty keymap without
help from the screen), type enter, wait for the kernel/udev/etc. to
boot, and eventually maybe see brltty or hear speakup starting.  On
nowadays silent laptops, that's the only point when they eventually get
feedback at last.  For a sysadmin that's not really convenient.

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Make syslinux beep?

[Samuel Thibault]

Daniel Dalton, le Thu 17 Jul 2008 20:22:52 +1000, a écrit :
 But, the beep would solve this. I know it wouldn't help on a laptop, but
 still.

Why wouldn't it help on a laptop?  If there is no internal speaker maybe
you could use headphone?

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Make syslinux beep?

[Samuel Thibault]

Frans Pop, le Thu 17 Jul 2008 12:32:39 +0200, a écrit :
 I could see myself agreeing if you can come up with an implementation that 
 only includes the beep for official builds (i.e. the addition of the beep 
 is triggered by something in debian/rules).

That should be feasible, so I guess that's the way we can head to.  I
can have a look at that part.

 We'd also need some assurance that it does not break installs using serial 
 console and on systems using management devices (like HP's iLO [1]).
 This means it needs to be tested for such cases before the change is 
 committed. Getting it tested would be up to you (accessibility people), 
 though we can possibly point you to people you could contact for that.

It is just about making sure that syslinux emitting a beep doesn't
pose problem there, should be feasible.  Debian-accessibility people,
volunteers?  It's just about modifying a syslinux image to add a ^G
character, check that it beeps on your system, and have it tested by
those people.

Thanks for your patience,
Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: New speakup-udeb component

[Samuel Thibault]

Hello,

Frans Pop, le Thu 17 Jul 2008 13:50:45 +0200, a écrit :
 On Tuesday 15 July 2008, Samuel Thibault wrote:
  Well, I don't think there is any architecture which shouldn't be
  supported, except s390 on which speakup doesn't even compile.  As for
  the images, I guess we can for now include it on the same images as
  brltty, that would make things coherent (i.e. accessible images).
  I have attached a documentation patch.
 
 I'm going to have to delay this discussion until I can see what the impact 
 on image size would be.

The speakup-modules package is 51K gz-compressed, 170K uncompressed
with a 1byte block size, 204K with a 4K block size.

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Make syslinux beep?

[Samuel Thibault]

Jérémy Bobbio, le Thu 17 Jul 2008 18:57:10 +0200, a écrit :
  For a version of the installer with full speech synthesis support, a 
  custom image would probably be the _only_ option.
 
 One of the other things that we have discussed (but not it full length)
 with Samuel after his talk during the last DebConf was about trying to
 add AT-SPI or other GTK+ accessibility features in the graphical
 installer.  One of the issue we thought about was about the image size.
 So, it would be another aspect that would benefit from a dedicated
 image.

Yep.

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#488494: cdebconf: Make the dark theme even more readable

[Samuel Thibault]

Richard Rafalski, le Thu 17 Jul 2008 17:08:07 +0200, a écrit :
 I've put an image doing this on
 http://brl.thefreecat.org/mini.iso
 And an image using white on blue as you suggested on
 http://brl.thefreecat.org/mini-blue.iso
 
 Thank you for the images. Both look good. It is ok to use the black 
 asterisk an the gray background.

Ok, so for coherency we should probably go with the black on gray.
Here is a patch that fixes the progression bar too.

Samuel
Index: src/modules/frontend/newt/newt.c
===
--- src/modules/frontend/newt/newt.c(r�vision 54394)
+++ src/modules/frontend/newt/newt.c(copie de travail)
@@ -89,7 +89,8 @@
black, lightgray,   /* button fg, bg */
gray, brightred,/* active button fg, bg */
white, gray,/* checkbox fg, bg */
-   yellow, brown,  /* active checkbox fg, bg */
+   /*yellow, brown,*/  /* active checkbox fg, bg */
+   black, lightgray,   /* active checkbox fg, bg */
/*yellow, blue,*/   /* entry box fg, bg */
white, black,   /* entry box fg, bg */
/*blue, lightgray,*//* label fg, bg */
@@ -104,9 +105,9 @@
white, black,   /* help line */
yellow, blue,   /* root text */
/*blue,*/ /* scale full */
-   gray, /* scale full */
+   black,/* scale full */
/*red,*/  /* scale empty */
-   lightgray,/* scale empty */
+   blue, /* scale empty */
blue, lightgray,/* disabled entry fg, bg */
/*black, lightgray,*/   /* compact button fg, bg */
white, black,   /* compact button fg, bg */

Bug#488494: cdebconf: Make the dark theme even more readable

[Samuel Thibault]

Hello,

Frans Pop, le Fri 18 Jul 2008 08:05:17 +0200, a écrit :
 On Thursday 17 July 2008, Samuel Thibault wrote:
  Ok, so for coherency we should probably go with the black on gray.
  Here is a patch that fixes the progression bar too.
 
 Committed in SVN.

Thanks, however slang was written by american people, so the UK
orthography is not recognized, it has to be lightgray, see attached
patch.

Samuel
Index: src/modules/frontend/newt/newt.c
===
--- src/modules/frontend/newt/newt.c(r�vision 54429)
+++ src/modules/frontend/newt/newt.c(copie de travail)
@@ -90,7 +90,7 @@
gray, brightred,/* active button fg, bg */
white, gray,/* checkbox fg, bg */
/*yellow, brown,*/  /* active checkbox fg, bg */
-   black, lightgrey,   /* active checkbox fg, bg */
+   black, lightgray,   /* active checkbox fg, bg */
/*yellow, blue,*/   /* entry box fg, bg */
white, black,   /* entry box fg, bg */
/*blue, lightgray,*//* label fg, bg */

Re: Make syslinux beep?

[Samuel Thibault]

Otavio Salvador, le Thu 17 Jul 2008 20:33:36 -0300, a écrit :
 Frans Pop [EMAIL PROTECTED] writes:
  (No need to CC me
 
  On Thursday 17 July 2008, Samuel Thibault wrote:
  I do agree it is annoying, but as Sebastien said, it's just about
  installation.  I've asked a few people, they said they wouldn't
  complain if it could help others.
 
  It's annoying for me amongst others. I do huge numbers of installations 
  and even more boots of the installer during development.
 
 For development we could put a variable to disable it, and it wouldn't
 hurt since it would help blind people a lot.
 
 I share the Samuel feeling that it would be good. Samuel  could
 provide an image for us to test and see how bad it would be. 

Ok, it wasn't just putting a ^G in the menu, because syslinux doesn't
have beep support in graphical mode...

Anyway, I've put an image on 
http://brl.thefreecat.org/mini-beep.iso

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Make syslinux beep?

[Samuel Thibault]

Stephen Frazier, le Sat 19 Jul 2008 23:11:36 -0500, a écrit :
 I know that other people with a different set up may not like the
 beeps. So, why not make it an option.

An option at debian-installer build time you mean?

If there was a way to pass an option dont beep to an already existing
boot image, we wouldn't really need for a beep, we could use that same
way to pass accessibility options...

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Make syslinux beep?

[Samuel Thibault]

Samuel Thibault, le Tue 12 Aug 2008 00:10:26 +0100, a écrit :
 Still no feedback on this?

(I mean feedback from debian-boot, I got some from debian-accessibility,
the feature was greatly appreciated).

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Make syslinux beep?

[Samuel Thibault]

Hello,

Still no feedback on this?

Samuel Thibault, le Sun 20 Jul 2008 15:47:18 +0100, a écrit :
 Otavio Salvador, le Thu 17 Jul 2008 20:33:36 -0300, a écrit :
  Frans Pop [EMAIL PROTECTED] writes:
   On Thursday 17 July 2008, Samuel Thibault wrote:
   I do agree it is annoying, but as Sebastien said, it's just about
   installation.  I've asked a few people, they said they wouldn't
   complain if it could help others.
  
   It's annoying for me amongst others. I do huge numbers of installations 
   and even more boots of the installer during development.
  
  For development we could put a variable to disable it, and it wouldn't
  hurt since it would help blind people a lot.
  
  I share the Samuel feeling that it would be good. Samuel  could
  provide an image for us to test and see how bad it would be. 
 
 Ok, it wasn't just putting a ^G in the menu, because syslinux doesn't
 have beep support in graphical mode...
 
 Anyway, I've put an image on 
 http://brl.thefreecat.org/mini-beep.iso

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Make syslinux beep?

[Samuel Thibault]

Otavio Salvador, le Mon 11 Aug 2008 22:06:50 -0300, a écrit :
 Samuel Thibault [EMAIL PROTECTED] writes:
 
  Samuel Thibault, le Tue 12 Aug 2008 00:10:26 +0100, a écrit :
  Still no feedback on this?
 
  (I mean feedback from debian-boot, I got some from debian-accessibility,
  the feature was greatly appreciated).
 
 It would be acceptable for release images. Could to work on a patch to
 only make it when we're doing a release? (no dailies or local builds)

Here is a patch.  I didn't know how I should detect the kind of build, I
just made it look at the udebs source.

Index: build/config/x86.cfg
===
--- build/config/x86.cfg(révision 54981)
+++ build/config/x86.cfg(copie de travail)
@@ -60,6 +60,11 @@
outfile= ; \
fi; \
fi; \
+   if [ $$outfile = menu.cfg -a $$USE_UDEBS_FROM != unstable ] ; 
then \
+   addbeep=s/^menu title.*//; \
+   else \
+   addbeep=; \
+   fi; \
if [ $$outfile ]; then \
cat $(file) \
| bootvars-subst MEDIA_TYPE $(MEDIA_TYPE) \
@@ -70,6 +75,7 @@
INITRD_GTK initrdg.gz \
VIDEO_MODE $(VIDEO_MODE) \
VIDEO_MODE_GTK $(VIDEO_MODE_GTK) \
+   | sed -e $$addbeep \
| todos | mcopy -i$(TEMP_BOOT) - ::$$outfile; \
fi; \
)
@@ -157,6 +163,11 @@
outfile=isolinux.cfg; \
fi; \
cat $(file) \
+   if [ $$outfile = menu.cfg -a $$USE_UDEBS_FROM != unstable ] ; 
then \
+   addbeep=s/^menu title.*//; \
+   else \
+   addbeep=; \
+   fi; \
| bootvars-subst MEDIA_TYPE $(MEDIA_TYPE) \
DEBIAN_VERSION $(DEBIAN_VERSION) \
BUILD_DATE $(BUILD_DATE) \
@@ -165,6 +176,7 @@
INITRD_GTK /install/gtk/initrd.gz \
VIDEO_MODE $(VIDEO_MODE) \
VIDEO_MODE_GTK $(VIDEO_MODE_GTK) \
+   | sed -e $$addbeep \
 $(TEMP_CD_INFO_DIR)/$$outfile; \
)
 
@@ -213,6 +225,11 @@
if [ $$outfile = syslinux.cfg ]; then \
outfile=isolinux.cfg; \
fi; \
+   if [ $$outfile = menu.cfg -a $$USE_UDEBS_FROM != unstable ] ; 
then \
+   addbeep=s/^menu title.*//; \
+   else \
+   addbeep=; \
+   fi; \
cat $(file) \
| bootvars-subst MEDIA_TYPE $(MEDIA_TYPE) \
DEBIAN_VERSION $(DEBIAN_VERSION) \
@@ -222,6 +239,7 @@
INITRD_GTK /install/gtk/initrd.gz \
VIDEO_MODE $(VIDEO_MODE) \
VIDEO_MODE_GTK $(VIDEO_MODE_GTK) \
+   | sed -e $$addbeep \
| todos  $(TEMP_CD_TREE)/$$outfile; \
)

@@ -266,6 +284,11 @@
if [ `basename $(file)` = syslinux.cfg ]; then \

outfile=$(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)/pxelinux.cfg/default; \
fi; \
+   if [ $$outfile = menu.cfg -a $$USE_UDEBS_FROM != unstable ] ; 
then \
+   addbeep=s/^menu title.*//; \
+   else \
+   addbeep=; \
+   fi; \
cat $(file) \
| bootvars-subst MEDIA_TYPE $(MEDIA_TYPE) \
DEBIAN_VERSION $(DEBIAN_VERSION) \
@@ -274,6 +297,7 @@
KERNEL $(NETBOOT_PATH)/linux \
INITRD $(NETBOOT_PATH)/initrd.gz \
VIDEO_MODE $(VIDEO_MODE) \
+   | sed -e $$addbeep \
 $$outfile; \
)



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Make syslinux beep?

[Samuel Thibault]

Frans Pop, le Tue 12 Aug 2008 10:29:23 +0200, a écrit :
 On Tuesday 12 August 2008, Samuel Thibault wrote:
  Here is a patch.  I didn't know how I should detect the kind of build,
  I just made it look at the udebs source.
 
 I don't think it's smart to use USE_UDEBS_FROM here. Better use a 
 dedicated variable.

So add a new one, just for the beeps or some RELEASE_BUILD=true/false?

 Also, please use '[ test ]  [ test ]' instead of '[ test -a
 test ]'.

I'm curious: why?

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

[PATCHv2] Make syslinux beep

[Samuel Thibault]

Hello,

Here is an corrected patch

Samuel

Index: build/config/x86.cfg
===
--- build/config/x86.cfg(révision 54981)
+++ build/config/x86.cfg(copie de travail)
@@ -60,6 +60,11 @@
outfile= ; \
fi; \
fi; \
+   if [ $$outfile = menu.cfg ]  $$MENU_BEEP ] ; then \
+   addbeep=s/^menu title.*//; \
+   else \
+   addbeep=; \
+   fi; \
if [ $$outfile ]; then \
cat $(file) \
| bootvars-subst MEDIA_TYPE $(MEDIA_TYPE) \
@@ -70,6 +75,7 @@
INITRD_GTK initrdg.gz \
VIDEO_MODE $(VIDEO_MODE) \
VIDEO_MODE_GTK $(VIDEO_MODE_GTK) \
+   | sed -e $$addbeep \
| todos | mcopy -i$(TEMP_BOOT) - ::$$outfile; \
fi; \
)
@@ -157,6 +163,11 @@
outfile=isolinux.cfg; \
fi; \
cat $(file) \
+   if [ $$outfile = menu.cfg ]  $$MENU_BEEP ] ; then \
+   addbeep=s/^menu title.*//; \
+   else \
+   addbeep=; \
+   fi; \
| bootvars-subst MEDIA_TYPE $(MEDIA_TYPE) \
DEBIAN_VERSION $(DEBIAN_VERSION) \
BUILD_DATE $(BUILD_DATE) \
@@ -165,6 +176,7 @@
INITRD_GTK /install/gtk/initrd.gz \
VIDEO_MODE $(VIDEO_MODE) \
VIDEO_MODE_GTK $(VIDEO_MODE_GTK) \
+   | sed -e $$addbeep \
 $(TEMP_CD_INFO_DIR)/$$outfile; \
)
 
@@ -213,6 +225,11 @@
if [ $$outfile = syslinux.cfg ]; then \
outfile=isolinux.cfg; \
fi; \
+   if [ $$outfile = menu.cfg ]  $$MENU_BEEP ] ; then \
+   addbeep=s/^menu title.*//; \
+   else \
+   addbeep=; \
+   fi; \
cat $(file) \
| bootvars-subst MEDIA_TYPE $(MEDIA_TYPE) \
DEBIAN_VERSION $(DEBIAN_VERSION) \
@@ -222,6 +239,7 @@
INITRD_GTK /install/gtk/initrd.gz \
VIDEO_MODE $(VIDEO_MODE) \
VIDEO_MODE_GTK $(VIDEO_MODE_GTK) \
+   | sed -e $$addbeep \
| todos  $(TEMP_CD_TREE)/$$outfile; \
)

@@ -266,6 +284,11 @@
if [ `basename $(file)` = syslinux.cfg ]; then \

outfile=$(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)/pxelinux.cfg/default; \
fi; \
+   if [ $$outfile = menu.cfg ]  $$MENU_BEEP ] ; then \
+   addbeep=s/^menu title.*//; \
+   else \
+   addbeep=; \
+   fi; \
cat $(file) \
| bootvars-subst MEDIA_TYPE $(MEDIA_TYPE) \
DEBIAN_VERSION $(DEBIAN_VERSION) \
@@ -274,6 +297,7 @@
KERNEL $(NETBOOT_PATH)/linux \
INITRD $(NETBOOT_PATH)/initrd.gz \
VIDEO_MODE $(VIDEO_MODE) \
+   | sed -e $$addbeep \
 $$outfile; \
)

Index: build/config/common
===
--- build/config/common (révision 54981)
+++ build/config/common (copie de travail)
@@ -55,6 +55,9 @@
 # The date the installer is built.
 BUILD_DATE ?= $(shell date -u '+%Y%m%d-%H:%M')
 
+# Produce a beep at boot menu
+MENU_BEEP ?= false
+
 # Filesystem type for the initrd, currently valid values are ext2, cramfs,
 # and initramfs.
 # NOTE: Your kernel must support this filesystem, not just a module. 
Index: build/README
===
--- build/README(révision 54981)
+++ build/README(copie de travail)
@@ -348,6 +348,11 @@
 DOS_VOLUME_LABEL
   Volume ID and label for DOS filesystems.
 
+MENU_BEEP
+  Set to true to produce a beep when the boot menu is ready to accept commands
+  (e.g. extra kernel parameters)
+  This improves accessibility of the image for blind people.
+
 GZIPPED
   Create gzipped images. This works only for the BOOT, ROOT and EXTRA
   targets.
Index: debian/rules
===
--- debian/rules(révision 54981)
+++ debian/rules(copie de travail)
@@ -7,9 +7,11 @@
 ifeq (${SUITE},UNRELEASED)
 USE_UDEBS_FROM=unstable
 TRANSSTATUS=
+MENU_BEEP=false
 else
 USE_UDEBS_FROM=lenny
 TRANSSTATUS=translation-status
+MENU_BEEP=true
 endif
 
 ARCHIVEDIR=debian/tmp/installer-$(ARCH)
@@ -29,7 +31,7 @@
 build-images:
$(MAKE) -C build all_build stats release \

Re: [PATCHv2] Make syslinux beep

[Samuel Thibault]

Frans Pop, le Wed 13 Aug 2008 00:51:29 +0200, a écrit :
 On Tuesday 12 August 2008, Samuel Thibault wrote:
  Here is an corrected patch
 
 Looks fine to me.
 
 Only wonder if it would not make more sense to rename the variable to 
 BOOT_BEEP or BEEP_ON_BOOT or SYSLINUX_BEEP. MENU could easily be confused 
 with the D-I main menu.

BOOTMENU_BEEP?

BOOT_BEEP alone would make me think that it's just beeping during boot,
not at the menu.

(SYSLINUX is probably not generic enough)

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [PATCHv2] Make syslinux beep

[Samuel Thibault]

Per Andersson, le Wed 13 Aug 2008 01:31:37 +0200, a écrit :
 On Wed, Aug 13, 2008 at 12:51 AM, Frans Pop [EMAIL PROTECTED] wrote:
  On Tuesday 12 August 2008, Samuel Thibault wrote:
  Here is an corrected patch
 
  Looks fine to me.
 
 Shouldn't there be a left bracket after the ?
 (It's missing in several places.)
 
 if [ $$outfile == menu.cfg ]  $$MENU_BEEP ]; then

EPARSE :)

MENU_BEEP holds true or false, which doesn't need a [ ].

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [PATCHv2] Make syslinux beep

[Samuel Thibault]

Samuel Thibault, le Wed 13 Aug 2008 00:54:15 +0100, a écrit :
 Per Andersson, le Wed 13 Aug 2008 01:31:37 +0200, a écrit :
  On Wed, Aug 13, 2008 at 12:51 AM, Frans Pop [EMAIL PROTECTED] wrote:
   On Tuesday 12 August 2008, Samuel Thibault wrote:
   Here is an corrected patch
  
   Looks fine to me.
  
  Shouldn't there be a left bracket after the ?
  (It's missing in several places.)
  
  if [ $$outfile == menu.cfg ]  $$MENU_BEEP ]; then
 
 EPARSE :)

Oops, man read for me, sorry, that's a typo indeed.

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

[PATCHv3] Make syslinux beep

[Samuel Thibault]

Frans Pop, le Wed 13 Aug 2008 02:05:45 +0200, a écrit :
 Better to just use 0/1 as values and only test for '= 1' (or test for
 set/unset, not sure what is more common).

At least DEBUG uses y/n, so I have done the same in the attached fixed
patch.

Samuel

Index: build/config/x86.cfg
===
--- build/config/x86.cfg(révision 54981)
+++ build/config/x86.cfg(copie de travail)
@@ -60,6 +60,11 @@
outfile= ; \
fi; \
fi; \
+   if [ $$outfile = menu.cfg ]  [ $$BOOTMENU_BEEP = y ] ; then \
+   addbeep=s/^menu title.*//; \
+   else \
+   addbeep=; \
+   fi; \
if [ $$outfile ]; then \
cat $(file) \
| bootvars-subst MEDIA_TYPE $(MEDIA_TYPE) \
@@ -70,6 +75,7 @@
INITRD_GTK initrdg.gz \
VIDEO_MODE $(VIDEO_MODE) \
VIDEO_MODE_GTK $(VIDEO_MODE_GTK) \
+   | sed -e $$addbeep \
| todos | mcopy -i$(TEMP_BOOT) - ::$$outfile; \
fi; \
)
@@ -157,6 +163,11 @@
outfile=isolinux.cfg; \
fi; \
cat $(file) \
+   if [ $$outfile = menu.cfg ]  [ $$BOOTMENU_BEEP = y ] ; then \
+   addbeep=s/^menu title.*//; \
+   else \
+   addbeep=; \
+   fi; \
| bootvars-subst MEDIA_TYPE $(MEDIA_TYPE) \
DEBIAN_VERSION $(DEBIAN_VERSION) \
BUILD_DATE $(BUILD_DATE) \
@@ -165,6 +176,7 @@
INITRD_GTK /install/gtk/initrd.gz \
VIDEO_MODE $(VIDEO_MODE) \
VIDEO_MODE_GTK $(VIDEO_MODE_GTK) \
+   | sed -e $$addbeep \
 $(TEMP_CD_INFO_DIR)/$$outfile; \
)
 
@@ -213,6 +225,11 @@
if [ $$outfile = syslinux.cfg ]; then \
outfile=isolinux.cfg; \
fi; \
+   if [ $$outfile = menu.cfg ]  [ $$BOOTMENU_BEEP = y ] ; then \
+   addbeep=s/^menu title.*//; \
+   else \
+   addbeep=; \
+   fi; \
cat $(file) \
| bootvars-subst MEDIA_TYPE $(MEDIA_TYPE) \
DEBIAN_VERSION $(DEBIAN_VERSION) \
@@ -222,6 +239,7 @@
INITRD_GTK /install/gtk/initrd.gz \
VIDEO_MODE $(VIDEO_MODE) \
VIDEO_MODE_GTK $(VIDEO_MODE_GTK) \
+   | sed -e $$addbeep \
| todos  $(TEMP_CD_TREE)/$$outfile; \
)

@@ -266,6 +284,11 @@
if [ `basename $(file)` = syslinux.cfg ]; then \

outfile=$(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)/pxelinux.cfg/default; \
fi; \
+   if [ $$outfile = menu.cfg ]  [ $$BOOTMENU_BEEP = y ] ; then \
+   addbeep=s/^menu title.*//; \
+   else \
+   addbeep=; \
+   fi; \
cat $(file) \
| bootvars-subst MEDIA_TYPE $(MEDIA_TYPE) \
DEBIAN_VERSION $(DEBIAN_VERSION) \
@@ -274,6 +297,7 @@
KERNEL $(NETBOOT_PATH)/linux \
INITRD $(NETBOOT_PATH)/initrd.gz \
VIDEO_MODE $(VIDEO_MODE) \
+   | sed -e $$addbeep \
 $$outfile; \
)

Index: build/config/common
===
--- build/config/common (révision 54981)
+++ build/config/common (copie de travail)
@@ -55,6 +55,9 @@
 # The date the installer is built.
 BUILD_DATE ?= $(shell date -u '+%Y%m%d-%H:%M')
 
+# Produce a beep at boot menu
+BOOTMENU_BEEP ?= n
+
 # Filesystem type for the initrd, currently valid values are ext2, cramfs,
 # and initramfs.
 # NOTE: Your kernel must support this filesystem, not just a module. 
Index: build/README
===
--- build/README(révision 54981)
+++ build/README(copie de travail)
@@ -348,6 +348,11 @@
 DOS_VOLUME_LABEL
   Volume ID and label for DOS filesystems.
 
+BOOTMENU_BEEP
+  Set to y to produce a beep when the boot menu is ready to accept commands
+  (e.g. extra kernel parameters, etc.)
+  This improves accessibility of the image for blind people.
+
 GZIPPED
   Create gzipped images. This works only for the BOOT, ROOT and EXTRA
   targets.
Index: debian/rules
===
--- debian/rules(révision 54981)
+++ debian/rules(copie de travail)
@@ -7,9 +7,11 @@
 ifeq (${SUITE},UNRELEASED)
 

Re: [PATCHv3] Make syslinux beep

[Samuel Thibault]

Samuel Thibault, le Wed 13 Aug 2008 01:39:31 +0100, a écrit :
 Frans Pop, le Wed 13 Aug 2008 02:05:45 +0200, a écrit :
  Better to just use 0/1 as values and only test for '= 1' (or test for
  set/unset, not sure what is more common).
 
 At least DEBUG uses y/n, so I have done the same in the attached fixed
 patch.

ping?

Samuel

Index: build/config/x86.cfg
===
--- build/config/x86.cfg(révision 54981)
+++ build/config/x86.cfg(copie de travail)
@@ -60,6 +60,11 @@
outfile= ; \
fi; \
fi; \
+   if [ $$outfile = menu.cfg ]  [ $$BOOTMENU_BEEP = y ] ; then \
+   addbeep=s/^menu title.*//; \
+   else \
+   addbeep=; \
+   fi; \
if [ $$outfile ]; then \
cat $(file) \
| bootvars-subst MEDIA_TYPE $(MEDIA_TYPE) \
@@ -70,6 +75,7 @@
INITRD_GTK initrdg.gz \
VIDEO_MODE $(VIDEO_MODE) \
VIDEO_MODE_GTK $(VIDEO_MODE_GTK) \
+   | sed -e $$addbeep \
| todos | mcopy -i$(TEMP_BOOT) - ::$$outfile; \
fi; \
)
@@ -157,6 +163,11 @@
outfile=isolinux.cfg; \
fi; \
cat $(file) \
+   if [ $$outfile = menu.cfg ]  [ $$BOOTMENU_BEEP = y ] ; then \
+   addbeep=s/^menu title.*//; \
+   else \
+   addbeep=; \
+   fi; \
| bootvars-subst MEDIA_TYPE $(MEDIA_TYPE) \
DEBIAN_VERSION $(DEBIAN_VERSION) \
BUILD_DATE $(BUILD_DATE) \
@@ -165,6 +176,7 @@
INITRD_GTK /install/gtk/initrd.gz \
VIDEO_MODE $(VIDEO_MODE) \
VIDEO_MODE_GTK $(VIDEO_MODE_GTK) \
+   | sed -e $$addbeep \
 $(TEMP_CD_INFO_DIR)/$$outfile; \
)
 
@@ -213,6 +225,11 @@
if [ $$outfile = syslinux.cfg ]; then \
outfile=isolinux.cfg; \
fi; \
+   if [ $$outfile = menu.cfg ]  [ $$BOOTMENU_BEEP = y ] ; then \
+   addbeep=s/^menu title.*//; \
+   else \
+   addbeep=; \
+   fi; \
cat $(file) \
| bootvars-subst MEDIA_TYPE $(MEDIA_TYPE) \
DEBIAN_VERSION $(DEBIAN_VERSION) \
@@ -222,6 +239,7 @@
INITRD_GTK /install/gtk/initrd.gz \
VIDEO_MODE $(VIDEO_MODE) \
VIDEO_MODE_GTK $(VIDEO_MODE_GTK) \
+   | sed -e $$addbeep \
| todos  $(TEMP_CD_TREE)/$$outfile; \
)

@@ -266,6 +284,11 @@
if [ `basename $(file)` = syslinux.cfg ]; then \

outfile=$(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)/pxelinux.cfg/default; \
fi; \
+   if [ $$outfile = menu.cfg ]  [ $$BOOTMENU_BEEP = y ] ; then \
+   addbeep=s/^menu title.*//; \
+   else \
+   addbeep=; \
+   fi; \
cat $(file) \
| bootvars-subst MEDIA_TYPE $(MEDIA_TYPE) \
DEBIAN_VERSION $(DEBIAN_VERSION) \
@@ -274,6 +297,7 @@
KERNEL $(NETBOOT_PATH)/linux \
INITRD $(NETBOOT_PATH)/initrd.gz \
VIDEO_MODE $(VIDEO_MODE) \
+   | sed -e $$addbeep \
 $$outfile; \
)

Index: build/config/common
===
--- build/config/common (révision 54981)
+++ build/config/common (copie de travail)
@@ -55,6 +55,9 @@
 # The date the installer is built.
 BUILD_DATE ?= $(shell date -u '+%Y%m%d-%H:%M')
 
+# Produce a beep at boot menu
+BOOTMENU_BEEP ?= n
+
 # Filesystem type for the initrd, currently valid values are ext2, cramfs,
 # and initramfs.
 # NOTE: Your kernel must support this filesystem, not just a module. 
Index: build/README
===
--- build/README(révision 54981)
+++ build/README(copie de travail)
@@ -348,6 +348,11 @@
 DOS_VOLUME_LABEL
   Volume ID and label for DOS filesystems.
 
+BOOTMENU_BEEP
+  Set to y to produce a beep when the boot menu is ready to accept commands
+  (e.g. extra kernel parameters, etc.)
+  This improves accessibility of the image for blind people.
+
 GZIPPED
   Create gzipped images. This works only for the BOOT, ROOT and EXTRA
   targets.
Index: debian/rules
===
--- debian/rules(révision 54981)
+++ debian/rules(copie de

Re: [PATCHv3] Make syslinux beep

[Samuel Thibault]

Otavio Salvador, le Wed 20 Aug 2008 15:40:09 -0300, a écrit :
 Samuel Thibault [EMAIL PROTECTED] writes:
  Samuel Thibault, le Wed 13 Aug 2008 01:39:31 +0100, a écrit :
  Frans Pop, le Wed 13 Aug 2008 02:05:45 +0200, a écrit :
   Better to just use 0/1 as values and only test for '= 1' (or test for
   set/unset, not sure what is more common).
  
  At least DEBUG uses y/n, so I have done the same in the attached fixed
  patch.
 
  ping?
 
 Hello Samuel,
 
 It looks OK for me. What is you alioth login? I think it is
 'sthibaul-guest' but wanted to be sure before adding you on the
 project.
 
 Obviously, you should still send the patches for review on the mailing
 list before commiting them but it makes easier for you to be able to
 commit your changes.

Oh, I wasn't expecting to commit it myself, but why not.  Yes, it is
sthibaul-guest.

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: r55173 - in trunk/installer: build build/config debian

[Samuel Thibault]

Ok, never mind, lunar fixed it in a much better (and actually
debian-installer style) way, thanks!

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: r55173 - in trunk/installer: build build/config debian

[Samuel Thibault]

Frans Pop, le Sat 23 Aug 2008 09:19:06 +0200, a écrit :
 On Saturday 23 August 2008, Samuel Thibault wrote:
  Author: sthibaul-guest
  Date: Sat Aug 23 00:22:05 2008
  New Revision: 55173
 
  Log:
* Optionally add a beep to the x86 syslinux menu, controlled by
  BOOTMENU_BEEP. This is enabled by default only for release builds.
 
 With this patch (after fixing a syntax error) I'm hearing beeps *during*
 D-I image builds. I don't really like that...

Oops, sorry, I usually always disable the bell in my terms, so didn't
notice.  I guess since we are using GNU sed anyway, the patch below
would be fine?

 @@ -222,6 +239,7 @@
 INITRD_GTK /install/gtk/initrd.gz \
 VIDEO_MODE $(VIDEO_MODE) \
 VIDEO_MODE_GTK $(VIDEO_MODE_GTK) \
 +   | sed -e $$addbeep \
 
 ... I also don't like that if BOOTMENU_BEEP != y we apparently execute
 'sed -e '. It may work, but it's not pretty.

It sure works, an empty sed scripts does nothing...  I'm not quite happy
with that solution either, but the problem is that there is an ambiguity
issue between the spaces that separate the arguments and the space
within the sed script (which has to be preserved).  Another way would be
to set addbeep_cmd to | sed -e and use

$addbeep_cmd $addbeep_arg

to disambiguate the spaces.

Samuel

Index: build/config/x86.cfg
===
--- build/config/x86.cfg(révision 55181)
+++ build/config/x86.cfg(copie de travail)
@@ -61,7 +61,7 @@
fi; \
fi; \
if [ $$outfile = menu.cfg ]  [ $$BOOTMENU_BEEP = y ]; then \
-   addbeep=s/^menu title.*//; \
+   addbeep=s/^menu title.*/\\a/; \
else \
addbeep=; \
fi; \
@@ -164,7 +164,7 @@
fi; \
cat $(file); \
if [ $$outfile = menu.cfg ]  [ $$BOOTMENU_BEEP = y ]; then \
-   addbeep=s/^menu title.*//; \
+   addbeep=s/^menu title.*/\\a/; \
else \
addbeep=; \
fi \
@@ -226,7 +226,7 @@
outfile=isolinux.cfg; \
fi; \
if [ $$outfile = menu.cfg ]  [ $$BOOTMENU_BEEP = y ]; then \
-   addbeep=s/^menu title.*//; \
+   addbeep=s/^menu title.*/\\a/; \
else \
addbeep=; \
fi; \
@@ -285,7 +285,7 @@

outfile=$(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)/pxelinux.cfg/default; \
fi; \
if [ $$outfile = menu.cfg ]  [ $$BOOTMENU_BEEP = y ]; then \
-   addbeep=s/^menu title.*//; \
+   addbeep=s/^menu title.*/\\a/; \
else \
addbeep=; \
fi; \

 


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: speakup enabled d-i?

[Samuel Thibault]

Hello,

Christian Perrier, le Wed 10 Sep 2008 06:39:41 +0200, a écrit :
 I'm personnally not completely sure about the status of this work, so
 I prefer leaving others to answer.

The script part is integrated, what is left is just to add the kernel
modules to the initrd, the question was which archs and which targets?
For instance, the patch below adds it to x86 cdrom, hd-media and netboot
targets.

Samuel

Index: build/boot/x86/f8.txt
===
--- build/boot/x86/f8.txt   (révision 55712)
+++ build/boot/x86/f8.txt   (copie de travail)
@@ -12,6 +12,7 @@
 Force static network config 0fnetcfg/disable_dhcp=true07
 Set keyboard map0fbootkbd=es07
 Use Braille tty 0fbrltty=driver,device,texttable07
+Use Speakup 0fspeakup.synth=driver07
 Use high contrast accessibility theme   0ftheme=dark07
 Select the kde or xfce desktops 0fdesktop=kde07
 
Index: build/pkg-lists/cdrom/i386.cfg
===
--- build/pkg-lists/cdrom/i386.cfg  (révision 55712)
+++ build/pkg-lists/cdrom/i386.cfg  (copie de travail)
@@ -22,3 +22,4 @@
 scsi-common-modules-${kernel:Version}
 
 acpi-modules-${kernel:Version}
+speakup-modules-${kernel:Version} ?
Index: build/pkg-lists/hd-media/i386.cfg
===
--- build/pkg-lists/hd-media/i386.cfg   (révision 55712)
+++ build/pkg-lists/hd-media/i386.cfg   (copie de travail)
@@ -29,3 +29,4 @@
 loop-modules-${kernel:Version}
 
 acpi-modules-${kernel:Version}
+speakup-modules-${kernel:Version} ?
Index: build/pkg-lists/netboot/i386.cfg
===
--- build/pkg-lists/netboot/i386.cfg(révision 55712)
+++ build/pkg-lists/netboot/i386.cfg(copie de travail)
@@ -40,3 +40,4 @@
 brltty-udeb
 serial-modules-${kernel:Version}
 usb-serial-modules-${kernel:Version} ?
+speakup-modules-${kernel:Version} ?


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: speakup enabled d-i?

[Samuel Thibault]

Frans Pop, le Wed 10 Sep 2008 11:38:21 +0200, a écrit :
 I would suggest to only add speakup to the graphical installer images. 

That would be better than nothing, as that includes the complete network
installer (not the businesscard).

 I would also seriously suggest to limit speakup to x86 and possibly 
 powerpc (if someone will test it!).

IIRC somebody already tried speakup on powerpc?

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: speakup enabled d-i?

[Samuel Thibault]

Frans Pop, le Wed 10 Sep 2008 11:38:21 +0200, a écrit :
 I would suggest to only add speakup to the graphical installer images. 
 Those are big already and already have a higher memory requirement. An 
 extra increase there is a lot less harmful than for the regular images.
 
 I would also seriously suggest to limit speakup to x86 and possibly 
 powerpc (if someone will test it!).

So we could commit this for now?

Samuel

Index: build/boot/x86/f8.txt
===
--- build/boot/x86/f8.txt   (révision 55726)
+++ build/boot/x86/f8.txt   (copie de travail)
@@ -12,6 +12,7 @@
 Force static network config 0fnetcfg/disable_dhcp=true07
 Set keyboard map0fbootkbd=es07
 Use Braille tty 0fbrltty=driver,device,texttable07
+Use Speakup 0fspeakup.synth=driver07
 Use high contrast accessibility theme   0ftheme=dark07
 Select the kde or xfce desktops 0fdesktop=kde07
 
Index: build/pkg-lists/cdrom/isolinux/gtk/i386.cfg
===
--- build/pkg-lists/cdrom/isolinux/gtk/i386.cfg (révision 55726)
+++ build/pkg-lists/cdrom/isolinux/gtk/i386.cfg (copie de travail)
@@ -1 +1,2 @@
 mouse-modules-${kernel:Version}
+speakup-modules-${kernel:Version}
Index: build/pkg-lists/hd-media/gtk/i386.cfg
===
--- build/pkg-lists/hd-media/gtk/i386.cfg   (révision 55726)
+++ build/pkg-lists/hd-media/gtk/i386.cfg   (copie de travail)
@@ -1 +1,2 @@
 mouse-modules-${kernel:Version}
+speakup-modules-${kernel:Version}
Index: build/pkg-lists/netboot/gtk/i386.cfg
===
--- build/pkg-lists/netboot/gtk/i386.cfg(révision 55726)
+++ build/pkg-lists/netboot/gtk/i386.cfg(copie de travail)
@@ -1 +1,2 @@
 mouse-modules-${kernel:Version}
+speakup-modules-${kernel:Version}


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: speakup enabled d-i?

[Samuel Thibault]

Frans Pop, le Wed 10 Sep 2008 13:59:22 +0200, a écrit :
  So we could commit this for now?
 
 You should add amd64 as well.

Ah, right.

Samuel

Index: build/boot/x86/f8.txt
===
--- build/boot/x86/f8.txt   (révision 55726)
+++ build/boot/x86/f8.txt   (copie de travail)
@@ -12,6 +12,7 @@
 Force static network config 0fnetcfg/disable_dhcp=true07
 Set keyboard map0fbootkbd=es07
 Use Braille tty 0fbrltty=driver,device,texttable07
+Use Speakup 0fspeakup.synth=driver07
 Use high contrast accessibility theme   0ftheme=dark07
 Select the kde or xfce desktops 0fdesktop=kde07
 
Index: build/pkg-lists/cdrom/isolinux/gtk/i386.cfg
===
--- build/pkg-lists/cdrom/isolinux/gtk/i386.cfg (révision 55726)
+++ build/pkg-lists/cdrom/isolinux/gtk/i386.cfg (copie de travail)
@@ -1 +1,2 @@
 mouse-modules-${kernel:Version}
+speakup-modules-${kernel:Version}
Index: build/pkg-lists/cdrom/isolinux/gtk/amd64.cfg
===
--- build/pkg-lists/cdrom/isolinux/gtk/amd64.cfg(révision 55726)
+++ build/pkg-lists/cdrom/isolinux/gtk/amd64.cfg(copie de travail)
@@ -1 +1,2 @@
 mouse-modules-${kernel:Version}
+speakup-modules-${kernel:Version}
Index: build/pkg-lists/hd-media/gtk/i386.cfg
===
--- build/pkg-lists/hd-media/gtk/i386.cfg   (révision 55726)
+++ build/pkg-lists/hd-media/gtk/i386.cfg   (copie de travail)
@@ -1 +1,2 @@
 mouse-modules-${kernel:Version}
+speakup-modules-${kernel:Version}
Index: build/pkg-lists/hd-media/gtk/amd64.cfg
===
--- build/pkg-lists/hd-media/gtk/amd64.cfg  (révision 55726)
+++ build/pkg-lists/hd-media/gtk/amd64.cfg  (copie de travail)
@@ -1 +1,2 @@
 mouse-modules-${kernel:Version}
+speakup-modules-${kernel:Version}
Index: build/pkg-lists/netboot/gtk/i386.cfg
===
--- build/pkg-lists/netboot/gtk/i386.cfg(révision 55726)
+++ build/pkg-lists/netboot/gtk/i386.cfg(copie de travail)
@@ -1 +1,2 @@
 mouse-modules-${kernel:Version}
+speakup-modules-${kernel:Version}
Index: build/pkg-lists/netboot/gtk/amd64.cfg
===
--- build/pkg-lists/netboot/gtk/amd64.cfg   (révision 55726)
+++ build/pkg-lists/netboot/gtk/amd64.cfg   (copie de travail)
@@ -1 +1,2 @@
 mouse-modules-${kernel:Version}
+speakup-modules-${kernel:Version}


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: speakup enabled d-i?

[Samuel Thibault]

Jérémy Bobbio, le Wed 10 Sep 2008 17:14:34 +0200, a écrit :
 This would make this option appear in all images, even those where
 speakup is not available, wouldn't it?
 
 f8.txt should probably be amended in f8.txt.withgtk…

Right, here is an updated patch

Samuel

Index: build/boot/x86/f8.txt.withgtk
===
--- build/boot/x86/f8.txt.withgtk   (révision 0)
+++ build/boot/x86/f8.txt.withgtk   (révision 0)
@@ -0,0 +1,24 @@
+0fSPECIAL BOOT PARAMETERS - INSTALLATION SYSTEM07  
   09F807
+
+You can use the following boot parameters at the 0fboot:07 prompt, 
+in combination with the boot method (see 09F307). These parameters
+control how the installer works.
+0f
+RESULT  PARAMETER07
+Verbose debugging   0fDEBCONF_DEBUG=507
+Debug boot sequence 0fBOOT_DEBUG=2|307
+Disable framebuffer 0ffb=false07
+Don't start PCMCIA  0fhw-detect/start_pcmcia=false07
+Force static network config 0fnetcfg/disable_dhcp=true07
+Set keyboard map0fbootkbd=es07
+Use Braille tty 0fbrltty=driver,device,texttable07
+Use Speakup 0fspeakup.synth=driver07
+Use high contrast accessibility theme   0ftheme=dark07
+Select the kde or xfce desktops 0fdesktop=kde07
+
+
+
+For example:
+  boot: install fb=false
+
+Press F1control and F then 1 for the help index, or ENTER to ${BOOTPROMPT}
Index: build/pkg-lists/cdrom/isolinux/gtk/i386.cfg
===
--- build/pkg-lists/cdrom/isolinux/gtk/i386.cfg (révision 55726)
+++ build/pkg-lists/cdrom/isolinux/gtk/i386.cfg (copie de travail)
@@ -1 +1,2 @@
 mouse-modules-${kernel:Version}
+speakup-modules-${kernel:Version}
Index: build/pkg-lists/cdrom/isolinux/gtk/amd64.cfg
===
--- build/pkg-lists/cdrom/isolinux/gtk/amd64.cfg(révision 55726)
+++ build/pkg-lists/cdrom/isolinux/gtk/amd64.cfg(copie de travail)
@@ -1 +1,2 @@
 mouse-modules-${kernel:Version}
+speakup-modules-${kernel:Version}
Index: build/pkg-lists/hd-media/gtk/i386.cfg
===
--- build/pkg-lists/hd-media/gtk/i386.cfg   (révision 55726)
+++ build/pkg-lists/hd-media/gtk/i386.cfg   (copie de travail)
@@ -1 +1,2 @@
 mouse-modules-${kernel:Version}
+speakup-modules-${kernel:Version}
Index: build/pkg-lists/hd-media/gtk/amd64.cfg
===
--- build/pkg-lists/hd-media/gtk/amd64.cfg  (révision 55726)
+++ build/pkg-lists/hd-media/gtk/amd64.cfg  (copie de travail)
@@ -1 +1,2 @@
 mouse-modules-${kernel:Version}
+speakup-modules-${kernel:Version}
Index: build/pkg-lists/netboot/gtk/i386.cfg
===
--- build/pkg-lists/netboot/gtk/i386.cfg(révision 55726)
+++ build/pkg-lists/netboot/gtk/i386.cfg(copie de travail)
@@ -1 +1,2 @@
 mouse-modules-${kernel:Version}
+speakup-modules-${kernel:Version}
Index: build/pkg-lists/netboot/gtk/amd64.cfg
===
--- build/pkg-lists/netboot/gtk/amd64.cfg   (révision 55726)
+++ build/pkg-lists/netboot/gtk/amd64.cfg   (copie de travail)
@@ -1 +1,2 @@
 mouse-modules-${kernel:Version}
+speakup-modules-${kernel:Version}


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: speakup enabled d-i?

[Samuel Thibault]

Frans Pop, le Thu 11 Sep 2008 21:24:34 +0200, a écrit :
 I've done a quick test with the dummy speakup driver for i386/mini.iso and 
 it seems to work fine.

Ok, thanks!

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

f8 speakup documentation

[Samuel Thibault]

Hello,

In f8.txt, one can read

Use Speakup (graphical install only)speakup.synth=driver

That is however misleading: what people understand is that they have to
boot the gui installer, which is wrong (since speakup can only read the
text console).  Something like the attached patch would be needed for
clarification.

Samuel

Index: f8.txt
===
--- f8.txt  (révision 55913)
+++ f8.txt  (copie de travail)
@@ -12,7 +12,8 @@
 Force static network config 0fnetcfg/disable_dhcp=true07
 Set keyboard map0fbootkbd=es07
 Use Braille tty 0fbrltty=driver,device,texttable07
-Use Speakup (graphical install only)0fspeakup.synth=driver07
+Use Speakup 0fspeakup.synth=driver07
+(Note: Speakup is available only on images that have the graphical installer)
 Use high contrast accessibility theme   0ftheme=dark07
 Select the kde or xfce desktops 0fdesktop=kde07
 


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: f8 speakup documentation

[Samuel Thibault]

Hello,

Frans Pop, le Sat 20 Sep 2008 20:30:30 +0200, a écrit :
 I'm sorry, but that text is much too verbose and takes up way too much of 
 the available space on that screen.

Well, I actually agree.

 As the option in the syslinux menu is titled Graphical install
 and that is exactly what needs to be selected, I do not see how the
 current text is misleading.

Then the title of the menu itself is misleading too since in order to be
able to use speakup we need to _not_ use the graphical installer
(speakup can only read the plain linux text console).

 IMO you should do better to get this documented clearly on the Debian 
 website, in the wiki and in the installation guide than relying on a help 
 screen that IMO very few people will read anyway.

My current experience on this is that people read these help screen more
than the installation guide...

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: plans concerning console-setup for squeeze?

[Samuel Thibault]

Hello,

Julien Cristau, le Wed 24 Sep 2008 12:29:07 +0200, a écrit :
 On Tue, Sep 23, 2008 at 18:03:16 +0200, Christian Perrier wrote:
  - having someone really caring about this *and* being skilled enough
  in those things to be able to  commit self to conduct the transition
  *and* maintain c-s afterwards
  
 OK.  I don't really know what's involved in maintaining c-s, and I
 expect my free time will shrink in the next months (and X is enough of a
 big beast to make me not want to take on anything else), so I'm not
 volunteering, but I'd be happy to help whoever does.

I would volunteer to work on it.

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#497676: Bug#396291: Bug#356055: loadlin: loadlin.exe cannot be built from source

[Samuel Thibault]

Hello,

Resending without the patch as it seems some mail servers don't like
160KB patches.

Samuel Thibault, le Tue 07 Oct 2008 11:06:23 +0200, a écrit :
 Peter commited upstream my yasm patch to support tasm syntax for
 loadlin, here is a backport to the debian package (just a few minor
 changes).  The patch is quite big, but as noted in the changelog, it
 just adds extensions that are enabled only when tasm compatible mode is
 requested.

Patch available on
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=56;filename=patch;att=1;bug=396291

Samuel



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Is speakup available in the GTK d-i from a usb-booted install?

[Samuel Thibault]

Terry D. Cudney, le Tue 14 Oct 2008 19:07:01 -0400, a écrit :
   In fact, the initial menu which one sees from a CD D-I boot does not 
 appear.

Then that's the problem, since you thus couldn't set the speakup
parameter.

   I have tried mini.iso and debian-testing-amd64-netinst.iso from the GTK 
 directory (Oct10 daily build) on a usb-drive with two partitions, the first 
 with syslinux, syslinux.cfg, initrd.gz and vmliuz, both from the GTK daily 
 build.

You can add the speakup parameter at the end of the `append' line of
syslinux.cfg.

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#505564: Please document the braille support

[Samuel Thibault]

Hello,

Simon Bienlein, le Fri 14 Nov 2008 17:12:24 +0100, a écrit :
 I am blind myself and I suggested the paragraph Install debian with a 
 Braille display in Bug #500441.

Thanks.  I've been asking for volunteers a few times already, apparently
nobody stepped up yet :/

There's a non-official documentation on
http://brl.thefreecat.org/wiki/moin.cgi/debian
which should provide braille  speakup information.

Samuel



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

uinput is needed for some braille devices

[Samuel Thibault]

Hello,

Some braille devices have a complete AT2 keyboard.  Brltty properly
simulates keypresses by passing them to a uinput device.  However, that
module is not available in the debian installer, and thus brltty falls
back to simulating keypresses by passing ascii to the tty layer and thus
having to assume a qwerty layout, which is not user friendly.  Would
it be fine to include uinput in the debian installer as the attached
patches should do? (patch-linux-kernel-di is for amd64, other archs need
a similar patch as well of course)

Samuel
Index: package-list
===
--- package-list(révision 56664)
+++ package-list(copie de travail)
@@ -445,3 +445,9 @@
 Priority: standard
 Description: atl2 NIC modules
  This package contains atl2 NIC modules.
+
+Package: uinput-modules
+Depends: kernel-image
+Priority: extra
+Description: uinput support
+ This package contains the uinput module.
Index: modules/uinput-modules
===
--- modules/uinput-modules  (révision 0)
+++ modules/uinput-modules  (révision 0)
@@ -0,0 +1 @@
+uinput
Index: modules/amd64/uinput-modules
===
--- modules/amd64/uinput-modules(révision 0)
+++ modules/amd64/uinput-modules(révision 0)
@@ -0,0 +1 @@
+#include uinput-modules
patching file config/common
Index: pkg-lists/netboot/alpha.cfg
===
--- pkg-lists/netboot/alpha.cfg (révision 56341)
+++ pkg-lists/netboot/alpha.cfg (copie de travail)
@@ -27,3 +27,4 @@
 brltty-udeb
 serial-modules-${kernel:Version} ?
 usb-serial-modules-${kernel:Version} ?
+uinput-modules-${kernel:Version} ?
Index: pkg-lists/netboot/i386.cfg
===
--- pkg-lists/netboot/i386.cfg  (révision 56341)
+++ pkg-lists/netboot/i386.cfg  (copie de travail)
@@ -41,3 +41,4 @@
 brltty-udeb
 serial-modules-${kernel:Version}
 usb-serial-modules-${kernel:Version} ?
+uinput-modules-${kernel:Version} ?
Index: pkg-lists/netboot/ppc64.cfg
===
--- pkg-lists/netboot/ppc64.cfg (révision 56341)
+++ pkg-lists/netboot/ppc64.cfg (copie de travail)
@@ -25,6 +25,7 @@
 brltty-udeb
 serial-modules-${kernel:Version}
 usb-serial-modules-${kernel:Version} ?
+uinput-modules-${kernel:Version} ?
 
 # IBM Power hypervisor modules, only available on powerpc64.
 hypervisor-modules-${kernel:Version} ?
Index: pkg-lists/netboot/ia64.cfg
===
--- pkg-lists/netboot/ia64.cfg  (révision 56341)
+++ pkg-lists/netboot/ia64.cfg  (copie de travail)
@@ -16,3 +16,4 @@
 brltty-udeb
 serial-modules-${kernel:Version}
 usb-serial-modules-${kernel:Version} ?
+uinput-modules-${kernel:Version} ?
Index: pkg-lists/netboot/amd64.cfg
===
--- pkg-lists/netboot/amd64.cfg (révision 56341)
+++ pkg-lists/netboot/amd64.cfg (copie de travail)
@@ -41,3 +41,4 @@
 brltty-udeb
 serial-modules-${kernel:Version} ?
 usb-serial-modules-${kernel:Version} ?
+uinput-modules-${kernel:Version} ?
Index: pkg-lists/netboot/powerpc.cfg
===
--- pkg-lists/netboot/powerpc.cfg   (révision 56341)
+++ pkg-lists/netboot/powerpc.cfg   (copie de travail)
@@ -25,6 +25,7 @@
 brltty-udeb
 serial-modules-${kernel:Version}
 usb-serial-modules-${kernel:Version} ?
+uinput-modules-${kernel:Version} ?
 
 # IBM Power hypervisor modules, only available on powerpc64.
 hypervisor-modules-${kernel:Version} ?

Bug#370172: cdebconf-gtk-udeb: yes/no questions through checkbox aren't understandable

[Samuel Thibault]

Package: cdebconf-gtk-udeb
Version: 0.101
Severity: minor

Hi,

When the gtk frontend asks yes/no debconf questions, it uses a checkbox
that the user has to check.  This gives a strange result, for instance

Write the changes to disks?

[ ] Write the changes to disks?

A simple correction for now could be to just not repeat the question:

Write the changes to disks?

[ ] Yes.

Regards,
Samuel

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (900, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

-- 
Samuel Thibault [EMAIL PROTECTED]
Actually, typing random strings in the Finder does the equivalent of
filename completion.
(Discussion in comp.os.linux.misc on the intuitiveness of commands: file
completion vs. the Mac Finder.)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#371167: (no subject)

[Samuel Thibault]

Package: installation-reports

INSTALL REPORT

This is actually an install report for two machines with exactly the same 
configuration, but I'm submitting only one report.

Debian-installer-version: debian-testing-amd64-netinst.iso, dated 2006-03-14, 
fetched from http://cdimage.debian.org/cdimage/etch_di_beta2/amd64/iso-cd/
uname -a: Linux rantanplan 2.6.15-1-amd64-generic #2 Mon Mar 20 10:43:41 UTC 
2006 x86_64 GNU/Linux
Date: Wed Jun  7 18:33:52 CEST 2006
Method: Netboot CD ROM, from ftp.fr.debian.org without proxy
Machine: Rackable server
Processor: Dual Core Opteron 265
Memory: 1GB
Root Device: SCSI NFORCE-CK804 controller.
Root Size/partition table:  /: 20GB, 2GB swap, 50GB spare:

Disk /dev/sda: 81.9 GB, 81964302336 bytes
255 heads, 63 sectors/track, 9964 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
   Device Boot  Start End  Blocks   Id  System
/dev/sda1   *   1243219535008+  83  Linux
/dev/sda224332675 1951897+  82  Linux swap / Solaris
/dev/sda32676996458548892+  83  Linux
Output of lspci and lspci -n:

:00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev 
a3)
:00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3)
:00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
:00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2)
:00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3)
:00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev a2)
:00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev 
a3)
:00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev 
a3)
:00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2)
:00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
:00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Address Map
:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
:00:19.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
:00:19.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Address Map
:00:19.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
:00:19.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
:01:06.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
:01:08.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 
100] (rev 10)
:08:0a.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge 
(rev 12)
:08:0a.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC (rev 01)
:08:0b.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge 
(rev 12)
:08:0b.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC (rev 01)
:0a:09.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 
Gigabit Ethernet (rev 03)
:0a:09.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 
Gigabit Ethernet (rev 03)

:00:00.0 0580: 10de:005e (rev a3)
:00:01.0 0601: 10de:0051 (rev a3)
:00:01.1 0c05: 10de:0052 (rev a2)
:00:02.0 0c03: 10de:005a (rev a2)
:00:02.1 0c03: 10de:005b (rev a3)
:00:06.0 0101: 10de:0053 (rev a2)
:00:07.0 0101: 10de:0054 (rev a3)
:00:08.0 0101: 10de:0055 (rev a3)
:00:09.0 0604: 10de:005c (rev a2)
:00:0d.0 0604: 10de:005d (rev a3)
:00:0e.0 0604: 10de:005d (rev a3)
:00:18.0 0600: 1022:1100
:00:18.1 0600: 1022:1101
:00:18.2 0600: 1022:1102
:00:18.3 0600: 1022:1103
:00:19.0 0600: 1022:1100
:00:19.1 0600: 1022:1101
:00:19.2 0600: 1022:1102
:00:19.3 0600: 1022:1103
:01:06.0 0300: 1002:4752 (rev 27)
:01:08.0 0200: 8086:1229 (rev 10)
:08:0a.0 0604: 1022:7450 (rev 12)
:08:0a.1 0800: 1022:7451 (rev 01)
:08:0b.0 0604: 1022:7450 (rev 12)
:08:0b.1 0800: 1022:7451 (rev 01)
:0a:09.0 0200: 14e4:1648 (rev 03)
:0a:09.1 0200: 14e4:1648 (rev 03)

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O]
Detect CD:  [O]
Load installer modules: [E]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install boot loader:[O]
Reboot: [E]

Comments/Problems:

When configuring the debian mirror, the provided choices weren't correct: they 
were looking for /debian-amd64/debian on mirrors. I guess this used to be 

Bug#371167: Acknowledgement ((no subject))

[Samuel Thibault]

Hi,

I forgot to add: in the partitionner, partition sizes are expressed in
GB.  But a french person might not understand that, Go should be
used instead.

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#373650: kbd-chooser: bootkbd option makes installer hangs, has to press enter

[Samuel Thibault]

Package: kbd-chooser
Version: 1.27
Severity: normal

Hi,

I tried to use the bootkbd option for preselecting the keyboard type,
but it just hangs and requires enter to be pressed.

- at the syslinux prompt, I type
install bootkbd=fr-latin9
- the kernel boots up, udev starts, the frame buffer is set up.
- It then hangs with only

Trying to enable the frame buffer...
SET debian-installer/keymap fr-latin9

displayed on a frame buffer-like console. Only if I press Enter does it
continue with

FSET debian-installer/keymap seen yes

and I have to press enter again for getting to the usual select
language installer screen.

I don't know if such behavior is on purpose or not, but it either needs
fixed or documented (press Enter to continue).

Samuel

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-rc1
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Beta3 and brltty

[Samuel Thibault]

Hi,

Just a note: when releasing Beta3, please Cc debian-accessibility, and
add a note somewhere in the mail that this is the first release which
integrates brltty (with auto-detection of USB devices).

(I'll probably be on vacation when this is released, that's why I won't
be able to do it myself)

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Etch Beta 3 bug: BRLTTY not installed

[Samuel Thibault]

Hi,

Could someone please add the following to the errata list?

BrlTTY doesn't automatically get installed

  Even if BrlTTY gets started if needed during installation (thanks to
  autodetection or manual setting), it isn't automatically installed
  on the target system.  That's because of ordering issues (see bug
  #373704) and missing transition (see bug #373118).  A wild fix is,
  during installation, to switch to VT 2 for running

  mv /usr/lib/prebaseconfig.d/50brltty /usr/lib/finish-install.d/19brltty

  Later, when the installer warns you that it will reboot the system,
  you may want to check that /target/etc/brltty.conf exists and contains
  wanted configuration.

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#373704: sort -k does not count fields the same as gnu sort

[Samuel Thibault]

reopen 373704
thanks

Version: 1:1.1.3-2

Hi,

It doesn't seem to be fixed:

$ sort -k5 -t/ -n
/usr/lib/finish-install.d/99reboot
/usr/lib/prebaseconfig.d/50brltty
^D
/usr/lib/finish-install.d/99reboot
/usr/lib/prebaseconfig.d/50brltty

While it would be expected to see 50brltty coming before 99reboot.

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#373704: sort -k does not count fields the same as gnu sort

[Samuel Thibault]

Geert Stappers, le Thu 24 Aug 2006 09:46:54 +0200, a écrit :
  It doesn't seem to be fixed:
  
  $ sort -k5 -t/ -n
  ^^
  /usr/lib/finish-install.d/99reboot
  /usr/lib/prebaseconfig.d/50brltty
  ^D
  /usr/lib/finish-install.d/99reboot
  /usr/lib/prebaseconfig.d/50brltty
  
  While it would be expected to see 50brltty coming before 99reboot.
 
 How does it behave when you leave out the numeric ( -n ) ?

Just the same:

$ sort -k5 -t/
/usr/lib/finish-install.d/99reboot
/usr/lib/prebaseconfig.d/50brltty
^D
/usr/lib/finish-install.d/99reboot
/usr/lib/prebaseconfig.d/50brltty

Samuel

BrlTTY and debian-installer

[Samuel Thibault]

+
+Template: brltty/table
+Type: select
+# Translators, keep the first word as is, and please try to avoid letters other
+# than just plain a-z, because only a-z have standard braille representations
+_Choices: cz, da, da-lt, da-1252, de, es, fi1, fi2, fr-cbifs, fr_CA, fr_FR, 
visiob, it, no-h, no-p, pl, ru, se, se-old, simple, uk, us, vni, nabcc
+Default: nabcc
+_Description: Choose a braille table (nabcc for having BrlTTY not restarted)
+
+Template: brltty/extra
+Type: string
+_Description: Extra BrlTTY options
diff -urN brltty-3.7.2/debian/brltty-udeb.udev.rules 
brltty-3.7.2-3/debian/brltty-udeb.udev.rules
--- brltty-3.7.2/debian/brltty-udeb.udev.rules  2006-08-27 04:43:06.0 
+0200
+++ brltty-3.7.2-3/debian/brltty-udeb.udev.rules2006-08-27 
04:54:39.0 +0200
@@ -5,28 +5,28 @@
 SUBSYSTEM!=usb_device, GOTO=brltty_rules_end
 
 # Alva
-SYSFS{idVendor}==06b0, SYSFS{idProduct}==0001, RUN+=/lib/brltty/brltty.sh 
-b al -d usb:
+SYSFS{idVendor}==06b0, SYSFS{idProduct}==0001, RUN+=/lib/brltty/brltty.sh 
al usb:
 
 # Baum
-SYSFS{idVendor}==0403, SYSFS{idProduct}==fe71, RUN+=/lib/brltty/brltty.sh 
-b bm -d usb:
-SYSFS{idVendor}==0403, SYSFS{idProduct}==fe72, RUN+=/lib/brltty/brltty.sh 
-b bm -d usb:
-SYSFS{idVendor}==0403, SYSFS{idProduct}==fe73, RUN+=/lib/brltty/brltty.sh 
-b bm -d usb:
-SYSFS{idVendor}==0403, SYSFS{idProduct}==fe74, RUN+=/lib/brltty/brltty.sh 
-b bm -d usb:
-SYSFS{idVendor}==0403, SYSFS{idProduct}==fe75, RUN+=/lib/brltty/brltty.sh 
-b bm -d usb:
+SYSFS{idVendor}==0403, SYSFS{idProduct}==fe71, RUN+=/lib/brltty/brltty.sh 
bm usb:
+SYSFS{idVendor}==0403, SYSFS{idProduct}==fe72, RUN+=/lib/brltty/brltty.sh 
bm usb:
+SYSFS{idVendor}==0403, SYSFS{idProduct}==fe73, RUN+=/lib/brltty/brltty.sh 
bm usb:
+SYSFS{idVendor}==0403, SYSFS{idProduct}==fe74, RUN+=/lib/brltty/brltty.sh 
bm usb:
+SYSFS{idVendor}==0403, SYSFS{idProduct}==fe75, RUN+=/lib/brltty/brltty.sh 
bm usb:
 
 # FreedomScientific
-SYSFS{idVendor}==0f4e, SYSFS{idProduct}==0100, RUN+=/lib/brltty/brltty.sh 
-b fs -d usb:
-SYSFS{idVendor}==0f4e, SYSFS{idProduct}==0111, RUN+=/lib/brltty/brltty.sh 
-b fs -d usb:
-SYSFS{idVendor}==0f4e, SYSFS{idProduct}==0112, RUN+=/lib/brltty/brltty.sh 
-b fs -d usb:
+SYSFS{idVendor}==0f4e, SYSFS{idProduct}==0100, RUN+=/lib/brltty/brltty.sh 
fs usb:
+SYSFS{idVendor}==0f4e, SYSFS{idProduct}==0111, RUN+=/lib/brltty/brltty.sh 
fs usb:
+SYSFS{idVendor}==0f4e, SYSFS{idProduct}==0112, RUN+=/lib/brltty/brltty.sh 
fs usb:
 
 # HandyTech
-SYSFS{idVendor}==0921, SYSFS{idProduct}==1200, RUN+=/lib/brltty/brltty.sh 
-b ht -d usb:
-SYSFS{idVendor}==0403, SYSFS{idProduct}==6001, RUN+=/lib/brltty/brltty.sh 
-b ht -d usb:
+SYSFS{idVendor}==0921, SYSFS{idProduct}==1200, RUN+=/lib/brltty/brltty.sh 
ht usb:
+SYSFS{idVendor}==0403, SYSFS{idProduct}==6001, RUN+=/lib/brltty/brltty.sh 
ht usb:
 
 # Papenmeier
-SYSFS{idVendor}==0403, SYSFS{idProduct}==f208, RUN+=/lib/brltty/brltty.sh 
-b pm -d usb:
+SYSFS{idVendor}==0403, SYSFS{idProduct}==f208, RUN+=/lib/brltty/brltty.sh 
pm usb:
 
 # Voyager
-SYSFS{idVendor}==0798, SYSFS{idProduct}==0001, RUN+=/lib/brltty/brltty.sh 
-b vo -d usb:
+SYSFS{idVendor}==0798, SYSFS{idProduct}==0001, RUN+=/lib/brltty/brltty.sh 
vo usb:
 
 LABEL=brltty_rules_end
diff -urN brltty-3.7.2/debian/control brltty-3.7.2-3/debian/control
--- brltty-3.7.2/debian/control 2006-08-27 04:43:06.0 +0200
+++ brltty-3.7.2-3/debian/control   2006-08-27 13:24:28.0 +0200
@@ -3,7 +3,8 @@
 Priority: extra
 Maintainer: Mario Lang [EMAIL PROTECTED]
 Build-Depends: debhelper (= 4.2), bison, doxygen, linuxdoc-tools, groff,
- flite1-dev, libncurses5-dev, libxaw7-dev, libatspi-dev, libbluetooth2-dev | 
libbluetooth-dev
+ flite1-dev, libncurses5-dev, libxaw7-dev, libatspi-dev,
+ libbluetooth2-dev | libbluetooth-dev, po-debconf
 Standards-Version: 3.6.1
 
 Package: brltty
@@ -69,7 +70,8 @@
 XC-Package-Type: udeb
 Section: debian-installer
 Priority: extra
-Depends: ${shlibs:Depends}
+Depends: ${shlibs:Depends}, debconf, localechooser
+XB-Installer-Menu-Item: 10
 Description: Access software for a blind person using a soft braille terminal
  This is a small version of brltty, optimized for use on install media.
 
diff -urN brltty-3.7.2/debian/po/en.po brltty-3.7.2-3/debian/po/en.po
--- brltty-3.7.2/debian/po/en.po1970-01-01 01:00:00.0 +0100
+++ brltty-3.7.2-3/debian/po/en.po  2006-08-27 14:41:03.0 +0200
@@ -0,0 +1,65 @@
+# French messages for brltty-udeb.
+# Copyright (C) 2006
+# This file is distributed under the same license as the brltty package.
+# Samuel Thibault [EMAIL PROTECTED], 2006.
+#
+msgid 
+msgstr 
+Project-Id-Version: en\n
+Report-Msgid-Bugs-To: [EMAIL PROTECTED]
+POT-Creation-Date: 2006-08-27 14:41+0200\n
+PO-Revision-Date: 2006-08-27 13:34+0200\n
+Last-Translator: Samuel Thibault [EMAIL PROTECTED]\n
+Language-Team: Debian Installer debian-boot@lists.debian.org\n
+MIME-Version: 1.0\n
+Content-Type: text/plain; charset=UTF-8\n
+Content-Transfer-Encoding: 8bit\n

Re: BrlTTY and debian-installer

[Samuel Thibault]

Miroslav Kure, le Sun 27 Aug 2006 16:51:56 +0200, a écrit :
 On Sun, Aug 27, 2006 at 04:49:29PM +0200, Christian Perrier wrote:
   +
   +Template: brltty/table
   +Type: select
   +# Translators, keep the first word as is, and please try to avoid 
   letters other
   +# than just plain a-z, because only a-z have standard braille 
   representations
   +_Choices: cz, da, da-lt, da-1252, de, es, fi1, fi2, fr-cbifs, fr_CA, 
   fr_FR, visiob, it, no-h, no-p, pl, ru, se, se-old, simple, uk, us, vni, 
   nabcc
  
  I deeply suggest to split out these choices as __Choices. This avoid
  many translator errors and also make easier to add/remove entries.
  
  I also suggest to add an Englih translation so that users of the
  English language may see Czech (cz) Danish (da), etc.
 
 Just a minor note, Czech as a language has code cs. cz is a code
 for Czech the country.

Yes I know, but the BrlTTY table is called this way (there are a few
other oddities like this).

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: BrlTTY and debian-installer

[Samuel Thibault]

.
+
+Template: brltty/extra
+Type: string
+_Description: Extra BrlTTY options:
diff -urN brltty-3.7.2/debian/brltty-udeb.udev.rules 
brltty-3.7.2-3/debian/brltty-udeb.udev.rules
--- brltty-3.7.2/debian/brltty-udeb.udev.rules  2006-08-27 04:43:06.0 
+0200
+++ brltty-3.7.2-3/debian/brltty-udeb.udev.rules2006-08-27 
04:54:39.0 +0200
@@ -5,28 +5,28 @@
 SUBSYSTEM!=usb_device, GOTO=brltty_rules_end
 
 # Alva
-SYSFS{idVendor}==06b0, SYSFS{idProduct}==0001, RUN+=/lib/brltty/brltty.sh 
-b al -d usb:
+SYSFS{idVendor}==06b0, SYSFS{idProduct}==0001, RUN+=/lib/brltty/brltty.sh 
al usb:
 
 # Baum
-SYSFS{idVendor}==0403, SYSFS{idProduct}==fe71, RUN+=/lib/brltty/brltty.sh 
-b bm -d usb:
-SYSFS{idVendor}==0403, SYSFS{idProduct}==fe72, RUN+=/lib/brltty/brltty.sh 
-b bm -d usb:
-SYSFS{idVendor}==0403, SYSFS{idProduct}==fe73, RUN+=/lib/brltty/brltty.sh 
-b bm -d usb:
-SYSFS{idVendor}==0403, SYSFS{idProduct}==fe74, RUN+=/lib/brltty/brltty.sh 
-b bm -d usb:
-SYSFS{idVendor}==0403, SYSFS{idProduct}==fe75, RUN+=/lib/brltty/brltty.sh 
-b bm -d usb:
+SYSFS{idVendor}==0403, SYSFS{idProduct}==fe71, RUN+=/lib/brltty/brltty.sh 
bm usb:
+SYSFS{idVendor}==0403, SYSFS{idProduct}==fe72, RUN+=/lib/brltty/brltty.sh 
bm usb:
+SYSFS{idVendor}==0403, SYSFS{idProduct}==fe73, RUN+=/lib/brltty/brltty.sh 
bm usb:
+SYSFS{idVendor}==0403, SYSFS{idProduct}==fe74, RUN+=/lib/brltty/brltty.sh 
bm usb:
+SYSFS{idVendor}==0403, SYSFS{idProduct}==fe75, RUN+=/lib/brltty/brltty.sh 
bm usb:
 
 # FreedomScientific
-SYSFS{idVendor}==0f4e, SYSFS{idProduct}==0100, RUN+=/lib/brltty/brltty.sh 
-b fs -d usb:
-SYSFS{idVendor}==0f4e, SYSFS{idProduct}==0111, RUN+=/lib/brltty/brltty.sh 
-b fs -d usb:
-SYSFS{idVendor}==0f4e, SYSFS{idProduct}==0112, RUN+=/lib/brltty/brltty.sh 
-b fs -d usb:
+SYSFS{idVendor}==0f4e, SYSFS{idProduct}==0100, RUN+=/lib/brltty/brltty.sh 
fs usb:
+SYSFS{idVendor}==0f4e, SYSFS{idProduct}==0111, RUN+=/lib/brltty/brltty.sh 
fs usb:
+SYSFS{idVendor}==0f4e, SYSFS{idProduct}==0112, RUN+=/lib/brltty/brltty.sh 
fs usb:
 
 # HandyTech
-SYSFS{idVendor}==0921, SYSFS{idProduct}==1200, RUN+=/lib/brltty/brltty.sh 
-b ht -d usb:
-SYSFS{idVendor}==0403, SYSFS{idProduct}==6001, RUN+=/lib/brltty/brltty.sh 
-b ht -d usb:
+SYSFS{idVendor}==0921, SYSFS{idProduct}==1200, RUN+=/lib/brltty/brltty.sh 
ht usb:
+SYSFS{idVendor}==0403, SYSFS{idProduct}==6001, RUN+=/lib/brltty/brltty.sh 
ht usb:
 
 # Papenmeier
-SYSFS{idVendor}==0403, SYSFS{idProduct}==f208, RUN+=/lib/brltty/brltty.sh 
-b pm -d usb:
+SYSFS{idVendor}==0403, SYSFS{idProduct}==f208, RUN+=/lib/brltty/brltty.sh 
pm usb:
 
 # Voyager
-SYSFS{idVendor}==0798, SYSFS{idProduct}==0001, RUN+=/lib/brltty/brltty.sh 
-b vo -d usb:
+SYSFS{idVendor}==0798, SYSFS{idProduct}==0001, RUN+=/lib/brltty/brltty.sh 
vo usb:
 
 LABEL=brltty_rules_end
diff -urN brltty-3.7.2/debian/control brltty-3.7.2-3/debian/control
--- brltty-3.7.2/debian/control 2006-08-27 04:43:06.0 +0200
+++ brltty-3.7.2-3/debian/control   2006-08-27 13:24:28.0 +0200
@@ -3,7 +3,8 @@
 Priority: extra
 Maintainer: Mario Lang [EMAIL PROTECTED]
 Build-Depends: debhelper (= 4.2), bison, doxygen, linuxdoc-tools, groff,
- flite1-dev, libncurses5-dev, libxaw7-dev, libatspi-dev, libbluetooth2-dev | 
libbluetooth-dev
+ flite1-dev, libncurses5-dev, libxaw7-dev, libatspi-dev,
+ libbluetooth2-dev | libbluetooth-dev, po-debconf
 Standards-Version: 3.6.1
 
 Package: brltty
@@ -69,7 +70,8 @@
 XC-Package-Type: udeb
 Section: debian-installer
 Priority: extra
-Depends: ${shlibs:Depends}
+Depends: ${shlibs:Depends}, debconf, localechooser
+XB-Installer-Menu-Item: 10
 Description: Access software for a blind person using a soft braille terminal
  This is a small version of brltty, optimized for use on install media.
 
diff -urN brltty-3.7.2/debian/po/en.po brltty-3.7.2-3/debian/po/en.po
--- brltty-3.7.2/debian/po/en.po1970-01-01 01:00:00.0 +0100
+++ brltty-3.7.2-3/debian/po/en.po  2006-08-27 17:27:01.0 +0200
@@ -0,0 +1,246 @@
+# French messages for brltty-udeb.
+# Copyright (C) 2006
+# This file is distributed under the same license as the brltty package.
+# Samuel Thibault [EMAIL PROTECTED], 2006.
+#
+msgid 
+msgstr 
+Project-Id-Version: en\n
+Report-Msgid-Bugs-To: [EMAIL PROTECTED]
+POT-Creation-Date: 2006-08-27 17:27+0200\n
+PO-Revision-Date: 2006-08-27 17:05+0200\n
+Last-Translator: Samuel Thibault [EMAIL PROTECTED]\n
+Language-Team: Debian Installer debian-boot@lists.debian.org\n
+MIME-Version: 1.0\n
+Content-Type: text/plain; charset=UTF-8\n
+Content-Transfer-Encoding: 8bit\n
+
+#. Type: text
+#. Description
+#: ../brltty-udeb.templates-in:1001
+msgid Choose Braille table
+msgstr 
+
+#. Type: string
+#. Description
+#: ../brltty-udeb.templates-in:2001
+msgid Braille driver:
+msgstr 
+
+#. Type: string
+#. Description
+#: ../brltty-udeb.templates-in:3001
+msgid Braille device:
+msgstr 
+
+#. Type: select
+#. Choices
+#. Translators, keep the first word as is, and please avoid letters other than
+#. just plain

Re: BrlTTY and debian-installer

[Samuel Thibault]

Hi,

Christian Perrier, le Sun 27 Aug 2006 16:49:29 +0200, a écrit :
 -knowing where to access the development repository do brltty. Mario,
 do you use a CVS or SVN ?
 -getting write access to that repository so that someone from the D-I
 i18n team may commit translations directly and save time to Mario. Of
 course, as a mutual agreemet, that access would only be meant for l10n
 maintenance

Actually, in case Mario doesn't use any repository, a small repository
can be set up just for this.

Samuel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#531482: console-setup: add a console-setup-hp-ekmap?

[Samuel Thibault]

Anton Zinoviev, le Tue 02 Jun 2009 23:47:55 +0300, a écrit :
  I also notice in kbd-chooser the mention of hil, which is available in 
  xkb-data as hp(hil), maybe a console-setup-hp-ekmap package should be 
  added, providing it?
 
 I have no idea what hp(hil) is for,

It's in xkb/keycodes/hp.

 but there is no mention about HIL in console-data.  So it seems
 the usual pc105 keycodes work on hppa and there is no need for
 console-setup-hp-ekmap.

That doesn't mean console-data was not buggued and hp(hil) support
wouldn't be welcome :)

Samuel



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: [D-I] Please test Debian Installer with console-setup

[Samuel Thibault]

Frans Pop, le Wed 03 Jun 2009 19:23:01 +0200, a écrit :
 So I'd appreciate if the people who've worked on console-setup up till now 
 could list the issues or TODO items they are aware of.

The TODO list is on
http://wiki.debian.org/DebianInstaller/ConsoleSetupSwitch

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: [D-I] Please test Debian Installer with console-setup

[Samuel Thibault]

Frans Pop, le Thu 04 Jun 2009 00:36:55 +0200, a écrit :
 So I was wondering if there are issues that people who've worked on
 c-s are aware of but that have not been listed.

I don't think there are.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: [D-I] Please test Debian Installer with console-setup

[Samuel Thibault]

Miroslav Kure, le Thu 11 Jun 2009 13:35:57 +0200, a écrit :
  * Some accented letters can't be written on the console (under X
everything is fine). The accented letters that have their own key
(e.g. pressing '2' will write 'ě') can be used without any
problems, but some letters need to be written using so called 'dead
key' (for Czech it is '=' key on the English keyboards) and these
do not work. E.g. 'ť' does not have its own key, so we need to
write that as 'Shift+=' (this does not produce any character yet)
followed by 't' - 'ť' should appear. Instead of the expected
result, two-character sequence appears:'^t'.

Mmm, this works for French's ê for instance, so I guess what could be
missing is the composition table for non-latin1 fonts.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: [D-I] Please test Debian Installer with console-setup

[Samuel Thibault]

Samuel Thibault, le Thu 11 Jun 2009 14:24:34 +0200, a écrit :
 so I guess what could be missing is the composition table for
 non-latin1 fonts.

Maybe console-setup should parse libx11's Compose file to get them.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: [D-I] Please test Debian Installer with console-setup

[Samuel Thibault]

Anton Zinoviev, le Fri 12 Jun 2009 17:49:15 +0300, a écrit :
 the console layout used circumflex instead of caron because dead_caron
 is not properly supported by the kernel.

That used to be the case: in k_dead() there is only a handful of
diacriticals: `, ', ^, ~,  and ,. But nowadays there is dead2 (key type
13, right between slock and brl), which can handle 256 diacriticals.
The mapping is up to userspace through the compose table.

That means that to make dead_caron working, we can make console-setup
use a 'v' diacritical for instance: add compose entries like v + c -
č, and make dead_caron emit K(13,'v').

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#533096: bdf2psf: make it possible to create unicode complement fonts

[Samuel Thibault]

Package: bdf2psf
Version: 1.28
Severity: wishlist

Hello,

I wanted to generate a tibetan font for the console for a blind friend
of mine who is learning tibetan.  Unifont covers it so it was just a
matter of extracting the U+0Fxy part of it and load it as second font
in addition to his usual latin1 font.  However, bdf2psf assumes that we
want to convert a whole font, and for instance reserves 0x20 - 0x7e:

for my $c (0x20 ... 0x7e) {
$position_type[$c] = 0;
}

so I had to disable this code.  To generate the font I then used the
attached symbol file, which could be included in the bdf2psf package.

Samuel

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bdf2psf depends on:
ii  perl  5.10.0-22  Larry Wall's Practical Extraction 

bdf2psf recommends no packages.

bdf2psf suggests no packages.

-- no debconf information
U+0F00
U+0F01
U+0F02
U+0F03
U+0F04
U+0F05
U+0F06
U+0F07
U+0F08
U+0F09
U+0F0A
U+0F0B
U+0F0C
U+0F0D
U+0F0E
U+0F0F
U+0F10
U+0F11
U+0F12
U+0F13
U+0F14
U+0F15
U+0F16
U+0F17
U+0F18
U+0F19
U+0F1A
U+0F1B
U+0F1C
U+0F1D
U+0F1E
U+0F1F
U+0F20
U+0F21
U+0F22
U+0F23
U+0F24
U+0F25
U+0F26
U+0F27
U+0F28
U+0F29
U+0F2A
U+0F2B
U+0F2C
U+0F2D
U+0F2E
U+0F2F
U+0F30
U+0F31
U+0F32
U+0F33
U+0F34
U+0F35
U+0F36
U+0F37
U+0F38
U+0F39
U+0F3A
U+0F3B
U+0F3C
U+0F3D
U+0F3E
U+0F3F
U+0F40
U+0F41
U+0F42
U+0F43
U+0F44
U+0F45
U+0F46
U+0F47
U+0F48
U+0F49
U+0F4A
U+0F4B
U+0F4C
U+0F4D
U+0F4E
U+0F4F
U+0F50
U+0F51
U+0F52
U+0F53
U+0F54
U+0F55
U+0F56
U+0F57
U+0F58
U+0F59
U+0F5A
U+0F5B
U+0F5C
U+0F5D
U+0F5E
U+0F5F
U+0F60
U+0F61
U+0F62
U+0F63
U+0F64
U+0F65
U+0F66
U+0F67
U+0F68
U+0F69
U+0F6A
U+0F6B
U+0F6C
U+0F6D
U+0F6E
U+0F6F
U+0F70
U+0F71
U+0F72
U+0F73
U+0F74
U+0F75
U+0F76
U+0F77
U+0F78
U+0F79
U+0F7A
U+0F7B
U+0F7C
U+0F7D
U+0F7E
U+0F7F
U+0F80
U+0F81
U+0F82
U+0F83
U+0F84
U+0F85
U+0F86
U+0F87
U+0F88
U+0F89
U+0F8A
U+0F8B
U+0F8C
U+0F8D
U+0F8E
U+0F8F
U+0F90
U+0F91
U+0F92
U+0F93
U+0F94
U+0F95
U+0F96
U+0F97
U+0F98
U+0F99
U+0F9A
U+0F9B
U+0F9C
U+0F9D
U+0F9E
U+0F9F
U+0FA0
U+0FA1
U+0FA2
U+0FA3
U+0FA4
U+0FA5
U+0FA6
U+0FA7
U+0FA8
U+0FA9
U+0FAA
U+0FAB
U+0FAC
U+0FAD
U+0FAE
U+0FAF
U+0FB0
U+0FB1
U+0FB2
U+0FB3
U+0FB4
U+0FB5
U+0FB6
U+0FB7
U+0FB8
U+0FB9
U+0FBA
U+0FBB
U+0FBC
U+0FBD
U+0FBE
U+0FBF
U+0FC0
U+0FC1
U+0FC2
U+0FC3
U+0FC4
U+0FC5
U+0FC6
U+0FC7
U+0FC8
U+0FC9
U+0FCA
U+0FCB
U+0FCC
U+0FCD
U+0FCE
U+0FCF
U+0FD0
U+0FD1
U+0FD2
U+0FD3
U+0FD4
U+0FD5
U+0FD6
U+0FD7
U+0FD8
U+0FD9
U+0FDA
U+0FDB
U+0FDC
U+0FDD
U+0FDE
U+0FDF
U+0FE0
U+0FE1
U+0FE2
U+0FE3
U+0FE4
U+0FE5
U+0FE6
U+0FE7
U+0FE8
U+0FE9
U+0FEA
U+0FEB
U+0FEC
U+0FED
U+0FEE
U+0FEF
U+0FF0
U+0FF1
U+0FF2
U+0FF3
U+0FF4
U+0FF5
U+0FF6
U+0FF7
U+0FF8
U+0FF9
U+0FFA
U+0FFB
U+0FFC
U+0FFD
U+0FFE
U+0FFF

Bug#531292: WARNING: Undefined kernel key code for

[Samuel Thibault]

Anders Lagerås, le Sun 31 May 2009 11:49:28 +0200, a écrit :
 WARNING: Undefined kernel key code for 150

So, these are due to missing matching between X keycodes and Linux
scancodes.  I'm wondering, however: shouldn't console-setup just use
the evdev keycodes instead of the xfree86 keycodes, as the former map
trivially to Linux scancodes?

Samuel



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#534260: installation-guide: Add link to braille keybindings

[Samuel Thibault]

Package: installation-guide
Version: 20090427
Severity: wishlist
Tags: patch

The installation guide advises to enter the preference menu to change
the current braille table.  The BRLTTY website now gives online help
about how to enter the preference menu, the installation guide should
reference that for newcomers to BRLTTY.

Samuel

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#534260: installation-guide: Add link to braille keybindings

[Samuel Thibault]

Sorry, I forgot the patch.

Samuel
Index: en/boot-installer/accessibility.xml
===
--- en/boot-installer/accessibility.xml (révision 59043)
+++ en/boot-installer/accessibility.xml (copie de travail)
@@ -28,7 +28,9 @@
 braille display will be automatically installed on the target system.
 You can thus just press enterkey; at the boot menu.
 Once classnamebrltty/classname is started, you can choose a braille
-table by entering the preference menu.
+table by entering the preference menu. Documentation on key
+bindings for braille devices is available on the ulink
+url=url-brltty-driver-help;classnamebrltty/classname website/ulink.
 
 /para
   /sect2
@@ -49,7 +51,9 @@
 the default. replaceabletable/replaceable is the name of the braille
 table to be used (see the ulink url=url-brltty-table-codes;table code
 list/ulink); the English table is the default. Note that the table can
-be changed later by entering the preference menu.
+be changed later by entering the preference menu. Documentation on key
+bindings for braille devices is available on the ulink
+url=url-brltty-driver-help;classnamebrltty/classname website/ulink.
 
 /para
   /sect2
Index: build/entities/urls.ent
===
--- build/entities/urls.ent (révision 59043)
+++ build/entities/urls.ent (copie de travail)
@@ -204,6 +204,7 @@
 
 !ENTITY url-brltty http://www.mielke.cc/brltty/;
 !ENTITY url-brltty-driver-codes 
http://www.mielke.cc/brltty/doc/Manual-BRLTTY/English/BRLTTY-11.html;
+!ENTITY url-brltty-driver-help http://www.mielke.cc/brltty/doc/drivers/;
 !ENTITY url-brltty-table-codes 
http://www.mielke.cc/brltty/doc/Manual-BRLTTY/English/BRLTTY-6.html;
 
 !ENTITY url-speakup http://www.linux-speakup.org/;

Bug#531292: WARNING: Undefined kernel key code for

[Samuel Thibault]

Anton Zinoviev, le Fri 26 Jun 2009 22:34:32 +0300, a écrit :
 On Tue, Jun 23, 2009 at 12:14:10AM +0200, Samuel Thibault wrote:
  Anders Lagerås, le Sun 31 May 2009 11:49:28 +0200, a écrit :
   WARNING: Undefined kernel key code for 150
  
  So, these are due to missing matching between X keycodes and Linux
  scancodes.  I'm wondering, however: shouldn't console-setup just use
  the evdev keycodes instead of the xfree86 keycodes, as the former map
  trivially to Linux scancodes?
 
 This is determined not by console-setup but by /usr/share/X11/xkb/rules/xorg.

Errr, but couldn't we not use xorg and directly evdev instead?  Xorg
actually usually uses evdev nowadays.

Samuel



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Review of console-setup wrt D-I [very long]

[Samuel Thibault]

Anton Zinoviev, le Fri 26 Jun 2009 21:27:48 +0300, a écrit :
  Let's have a look (I hope I counted correctly):
  1) keyboard model, ~150 options ... WTF?
 
 I don't know.

They correspond to the variety of keyboards with additional keys. For
instance, my Internet keyboard has a few navigation keys.
Unfortunately they are incompatible one with the other.

  If Netherlands is selected I get the layout question with:
 Netherlands
 Netherlands - Macintosh
 Netherlands - Standard
 Netherlands - Sun dead keys
  OK, the last 3 should probably not be there, but Netherlands 
  and Netherlands - standard? Is Netherlands not standard enough?
  Possibly Standard should be Sun Standard instead?
 
 I have no idea what the difference between Netherlands and 
 Netherlands - Standard is.

I believe that's a bit like the battle between the legacy french
layout and the current french layout: concerning standard keyboards,
they are just the same, but they extend it in a different way.

 Such problems have to be reported upstream.

Or we could whitelist or blacklist some layouts.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Bug#531292: WARNING: Undefined kernel key code for

[Samuel Thibault]

Anton Zinoviev, le Sat 27 Jun 2009 12:29:17 +0300, a écrit :
 On Fri, Jun 26, 2009 at 10:53:55PM +0200, Samuel Thibault wrote:
  Anton Zinoviev, le Fri 26 Jun 2009 22:34:32 +0300, a écrit :
   On Tue, Jun 23, 2009 at 12:14:10AM +0200, Samuel Thibault wrote:

So, these are due to missing matching between X keycodes and Linux
scancodes.  I'm wondering, however: shouldn't console-setup just use
the evdev keycodes instead of the xfree86 keycodes, as the former map
trivially to Linux scancodes?
   
   This is determined not by console-setup but by 
   /usr/share/X11/xkb/rules/xorg.
  
  Errr, but couldn't we not use xorg and directly evdev instead?  Xorg
  actually usually uses evdev nowadays.
 
 Do you mean Xorg uses /usr/share/X11/xkb/rules/evdev?

When using the evdev driver instead of the legacy kbd driver yes.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: [D-I] Please test Debian Installer with console-setup

[Samuel Thibault]

Anton Zinoviev, le Sat 27 Jun 2009 18:52:34 +0300, a écrit :
 This was because setfont can not load compressed fonts without gzip. I 
 changed console-setup-fonts-udeb to include uncompressed fonts. 
 Console-setup-fonts-udeb is not required so if the space is tight it can 
 be dropped.

Err, isn't it less costly to include gzip than to include uncompressed
fonts?

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: [D-I] Please test Debian Installer with console-setup

[Samuel Thibault]

Anton Zinoviev, le Sat 27 Jun 2009 22:12:19 +0300, a écrit :
 On Sat, Jun 27, 2009 at 08:35:44PM +0200, Samuel Thibault wrote:
  Anton Zinoviev, le Sat 27 Jun 2009 18:52:34 +0300, a écrit :
   This was because setfont can not load compressed fonts without gzip. I 
   changed console-setup-fonts-udeb to include uncompressed fonts. 
   Console-setup-fonts-udeb is not required so if the space is tight it can 
   be dropped.
  
  Err, isn't it less costly to include gzip than to include uncompressed
  fonts?
 
 Only if gzip is smaller than 90K.

€ ls /bin/gzip -l
-rwxr-xr-x 1 root root 63K fév 28 03:59 /bin/gzip*

And it's not even a lightweight version :)

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Review of console-setup wrt D-I [very long]

[Samuel Thibault]

Hello,

Colin Watson, le Sat 27 Jun 2009 23:57:54 +0100, a écrit :
   If Netherlands is selected I get the layout question with:
  Netherlands
  Netherlands - Macintosh
  Netherlands - Standard
  Netherlands - Sun dead keys
   OK, the last 3 should probably not be there, but Netherlands 
   and Netherlands - standard? Is Netherlands not standard enough?
   Possibly Standard should be Sun Standard instead?
  
  I have no idea what the difference between Netherlands and 
  Netherlands - Standard is.  Such problems have to be reported 
  upstream.
 
 There are a fair number of differences between those two variants in
 /usr/share/X11/xkb/symbols/nl, albeit mostly at higher shift levels. I
 agree, this should be taken up with XKB upstream if it's an issue,
 rather than us carving out our own little silo.

It's not exactly this issue, but it's still related to Frans' concern
about origin of keyboards:
http://bugs.freedesktop.org/show_bug.cgi?id=21046
Bug 21046 – express that the us layout makes the majority in a bunch
of countries

In short, upstream agreed that the nl layout should have something like
a uk variant, however Sergey doesn't know how that should be called,
and neither do I. Could NL people comment on the bug?

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Review of console-setup wrt D-I [very long]

[Samuel Thibault]

Hello,

Frans Pop, le Sun 28 Jun 2009 09:09:20 +0200, a écrit :
  http://bugs.freedesktop.org/show_bug.cgi?id=21046
  Could NL people comment on the bug?
 
 Eh, I *am* an NL person...

I know.

 I thought I'd already made my comments clear and explained the Dutch
 situation.

I know the situation. What I'm talking about is this:

 3) Both Dutch keymaps and American English keymaps are in use, but the
Dutch ones are a relatively small minority.
 4) If one of the variants currently listed under Netherlands really
is the American English layout then that is absolutely not obvious.
I would *NEVER* have understood that from the current descriptions.

That's why it I prompted for choosing a correct naming for the upstream
bug report above.

 2) Origin as question sucks majorly.

The problem is: how should things be called? kbd-chooser used to just
throw one list at the user. It used to not be so big, but that's not a
scalable solution, as there _are_ a lot of different keyboards. Maybe we
can clean some variants out (like all the dvorak variants which
double the number of variants), but that still leaves a long list.

Here, Origin means where you bought the keyboard, it is a quite clear
question, provided that there is a US variant listed in the different
layouts for countries which usually sell it.

Another way I had thought about would be to first show a list of all
the keyboards known to be used by the combination of country/language
given at the localechooser stage, for instance en_CA would just propose
the american layout while the fr_CA would just propose the canadian
layout.  And a choice like not in this list, which brings to a second
list with all the keyboards known to be used in the country (i.e. the
Origin question is not asked, it just defaults to the localechooser
country). Again a not in this list choice would bring to a third list
with a list of layouts for all countries, but with a lot of variants
removed (e.g. legacy, dvorak). Eventually, a not in this list would
bring to a fourth list with really all the variants.

 5) Dutch people very much *do* still type accented characters.

ERrr, really? That's not what dutch people I've talked with told
me. Anyway, that's not the question at stake.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Review of console-setup wrt D-I [very long]

[Samuel Thibault]

Frans Pop, le Sun 28 Jun 2009 13:00:19 +0200, a écrit :
 BTW, I would expect there are people in NL using Dvorak, but it's not 
 being offered as a choice there...

Because xkb doesn't have that layout.

   5) Dutch people very much *do* still type accented characters.
 
  ERrr, really? That's not what dutch people I've talked with told
  me. Anyway, that's not the question at stake.
 
 See these pages from a Dutch on-line newspaper:
 http://www.telegraaf.nl/binnenland/4270616/__Strengere_controle_op_prive-gebruik_zakenauto__.html?p=40,1
 http://www.telegraaf.nl/buitenland/4270520/__Belgisch_pardon_voor_illegalen__.html?p=40,2

That's newspaper, not everyday writing.

 I'll believe you if people say they don't bother in informal emails or 
 SMS, but ask them if they also don't bother when writing an application 
 for a job...

They told me rather for writing their PhD.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Review of console-setup wrt D-I [very long]

[Samuel Thibault]

Samuel Thibault, le Sun 28 Jun 2009 11:59:26 +0200, a écrit :
 Another way I had thought about would be to first show a list of all
 the keyboards known to be used by the combination of country/language
 given at the localechooser stage,

Note: there is enough information in xkb-data to achieve this
automatically, I can work on it (I have already done something similar
actually).

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Review of console-setup wrt D-I [very long]

[Samuel Thibault]

Frans Pop, le Sun 28 Jun 2009 13:45:33 +0200, a écrit :
 On Sunday 28 June 2009, Samuel Thibault wrote:
  Frans Pop, le Sun 28 Jun 2009 13:00:19 +0200, a ?crit :
   BTW, I would expect there are people in NL using Dvorak, but it's not
   being offered as a choice there...
 
  Because xkb doesn't have that layout.
 
 Do you mean that xkb has a _separate_ layout for Netherlands - American 
 English? That is... insane.

Err, no, it has an entry in the nl part that includes the american layout.

 In that case there really _should_ be a Netherlands - Dvorak layout as 
 well.

If someone could implement the dutch dvorak, sure. Remember that dvorak
is per-language. You can always use the english dvorak for Dutch, but
that's not efficient.

 What could possibly work is some ability to define cheap symlinks, but 
 duplicating entire layouts really is insane (IMHO).

xkb uses cheap symlinks. They just need to be defined. Talk with the
upstream bug report, really.

 5) Dutch people very much *do* still type accented characters.
   
ERrr, really? That's not what dutch people I've talked with told
me. Anyway, that's not the question at stake.
  
   See these pages from a Dutch on-line newspaper:
   http://www.telegraaf.nl/binnenland/4270616/__Strengere_controle_op_pr
  ive-gebruik_zakenauto__.html?p=40,1
   http://www.telegraaf.nl/buitenland/4270520/__Belgisch_pardon_voor_ill
  egalen__.html?p=40,2
 
  That's newspaper, not everyday writing.
 
 So newspaper people are not allowed to use Debian?

Don't make me say what I didn't say. I actually don't know why you
raised that point at all.

   I'll believe you if people say they don't bother in informal emails
   or SMS, but ask them if they also don't bother when writing an
   application for a job...
 
  They told me rather for writing their PhD.
 
 And that gets accepted? /me cries...

AGAIN, don't make me say what I didn't say, or ask for better wording. I
meant that they didn't care about accents before having to write their
PhD.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Review of console-setup wrt D-I [very long]

[Samuel Thibault]

Frans Pop, le Sun 28 Jun 2009 14:36:25 +0200, a écrit :
 On Sunday 28 June 2009, Samuel Thibault wrote:
   In that case there really _should_ be a Netherlands - Dvorak layout
   as well.
 
  If someone could implement the dutch dvorak, sure. Remember that dvorak
  is per-language. You can always use the english dvorak for Dutch, but
  that's not efficient.
 
 It is a necessary consequence of the proposal to make the *country* the 
 primary selection mechanism instead of selecting the correct nationality 
 for the standard.

I don't understand how dvorak being language-based is a consequence of
that.  It's an intrisic of dvorak layouts to be language-based.

   What could possibly work is some ability to define cheap symlinks, but 
   duplicating entire layouts really is insane (IMHO).
 
  xkb uses cheap symlinks. They just need to be defined. Talk with the
  upstream bug report, really.
 
 No thanks, I have no interest in helping to promote an insane scheme.

Which scheme are you talking about?  Calling it insane doesn't help
the discussion, really.  I'm here talking about arranging variants in
the nl layout so that in my proposal (several size-increasing lists of
layouts), the us variant appears in the very first list thanks to being
announced in xkb-data's nl layout, the rationale being that it's really
widespread in NL (that wouldn't be the case for FR for instance).

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Reducing the complication of choices in console-setup udeb config: first thought

[Samuel Thibault]

Hello,

Christian Perrier, le Sun 28 Jun 2009 19:43:01 +0200, a écrit :
 The general rule would then be: one language, one layoutwith
 exceptions when established practice needs them.

I'd even say, one language/country, one layout. Note for instance
french, for which there are a lot of layouts, from BE, CA, CH, FR,
... But there is little chance getting wrong when taking the country
into account too.  That's why I proposed to first have a list for each
country/language pair. Then a list for each language can be used if the
user is not happy with the former.

 Here is what I come with (to be completed...I stopped at Kazakh):

No need to do it by hand, it can be automated from xkeyboard-config's
data.  Any divergence from a hand-written version is just a bug in
xkeyboard-config.

 probably around 70 for i386|amd64 and much much less for
 arches where there is a need for a dedicated list

Why a dedicated list?

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Reducing the complication of choices in console-setup udeb config: first thought

[Samuel Thibault]

Christian Perrier, le Mon 29 Jun 2009 06:58:21 +0200, a écrit :
 My point was *not* about showing a different list to users depending
 on the language they selected.
 
 It was just about building *one* list that would offer users all
 reasonable choices.

Ah. I'm still afraid that's not very scalable (you already announced
~70 choices, and I expect to see the list still growing, as there are
something like a hundred scripts in Unicode, latin being just one while
accounting for a lot of already existing keymaps...). When the default
choice is correct, that should be ok, but for borderline cases, it will
not be convenient for the user to browse it.

   Here is what I come with (to be completed...I stopped at Kazakh):
  
  No need to do it by hand, it can be automated from xkeyboard-config's
  data.  Any divergence from a hand-written version is just a bug in
  xkeyboard-config.
 
 I don't really see how such a list could be derived from
 xkeyboard-config.

With your point of view, that may be different indeed.

 What there does tell me that I need a keymap for fr_FR, another for
 fr_BE and fr_CH or fr_CAwhile de_DE and de_AT are happy with the
 same one?

Thanks to the language/country tags attached to layouts and variants.
The FR layout has a fra language tag, the BE layout has ger and a fra
tags, the CH layout has ger and gsw tags, while its fr variant has a fra
tag, the CA layout has a fra tag, the DE layout has a ger tag. There
is no AT layout, but upstream will be happy to include one that just
includes the DE one (and not the CH one). Yes, it would wear a different
name than the DE one, but that's probably an opportunity to make the
name clearer for the user. Yes, thus the list would get very long, and
that's why I proposed to show several size-increasing versions.

My point is: why should Debian maintain that information while it should
already be in the xkb database?

   probably around 70 for i386|amd64 and much much less for
   arches where there is a need for a dedicated list
  
  Why a dedicated list?
 
 Because I see this as the only way to keep things simple. We would
 then have to just maintain that selection of common keymaps.

Why only the common keymaps? To mimic Franc's way of asking: aren't
people using uncommon keymaps allowed to install Debian?

I do agree that we should blacklist exotic keymaps like my keymap with
a lot of stuff to type unicode arrows in d-i, but there are keymaps for
a lot of languages, and you are proposing to handle additions by hand,
that's a pain.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: The question about which language we use in the first is good

[Samuel Thibault]

Hideki Yamane, le Tue 30 Jun 2009 21:15:48 +0900, a écrit :
  I used ubuntu-server edition CD, it seems to be good, because it asks 
  which language we use.

I guess you mean even before the boot parameters?
(because else it's already the case)

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: The question about which language we use in the first is good

[Samuel Thibault]

Hello,

Just a reminder: these boot loader are not accessible, so it shouldn't
be assumed that the user choosing the default value means he meant it,
it can also mean he just couldn't read it, and so the question should be
asked again after booting.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Reducing the complication of choices in console-setup udeb config: first thought

[Samuel Thibault]

Christian Perrier, le Sat 04 Jul 2009 11:31:07 +0200, a écrit :
 I went through all languages.

That approach misses things. For instance, Andorra (AD)'s official
language is catalan (cat), for which you only provide es' cat variant
layout. Xorg does have an ad layout which is quite different from es'
cat variant.  And that is only the first one in the xkb list.

Ok, that's no regression from what we had previously and we have no
AD locale for now, but should we really select keyboards by hand and
restrict ourselves from just automatically supporting such keyboard?

I have a script that can automatically generate the attached perl hash
(kbds), which I had meant to use to automatically determine the default
keyboard to use depending on the country/language pair, to replace the
handcrafted switch statement of console-setup's config.  That brings 137
keyboard layouts which we should ideally support (kbds2).

Samuel
%locales_keyboards = (
'AD' = {
'ca' = { 'layout' = 'ad' },
},
'AE' = {
'ar' = { 'layout' = 'ara' },
},
'AF' = {
'ps' = { 'layout' = 'af', 'variant' = 'ps' },
'uz' = { 'layout' = 'af', 'variant' = 'uz' },
},
'AL' = {
'sq' = { 'layout' = 'al' },
},
'AM' = {
'hy' = { 'layout' = 'am' },
},
'AR' = {
'es' = { 'layout' = 'latam' },
},
'AZ' = {
'az' = { 'layout' = 'az' },
},
'BA' = {
'bs' = { 'layout' = 'ba' },
},
'BD' = {
'bn' = { 'layout' = 'bd' },
},
'BE' = {
'de' = { 'layout' = 'be' },
'fr' = { 'layout' = 'be' },
},
'BG' = {
'bg' = { 'layout' = 'bg' },
},
'BH' = {
'ar' = { 'layout' = 'ara' },
},
'BO' = {
'es' = { 'layout' = 'latam' },
},
'BR' = {
'eo' = { 'layout' = 'br', 'variant' = 'nativo-epo' },
'pt' = { 'layout' = 'br' },
},
'BT' = {
'dz' = { 'layout' = 'bt' },
},
'BY' = {
'be' = { 'layout' = 'by' },
},
'CA' = {
'en' = { 'layout' = 'ca', 'variant' = 'eng' },
'fr' = { 'layout' = 'ca' },
'iu' = { 'layout' = 'ca', 'variant' = 'ike' },
},
'CD' = {
'fr' = { 'layout' = 'cd' },
},
'CH' = {
'de' = { 'layout' = 'ch' },
'fr' = { 'layout' = 'ch', 'variant' = 'fr' },
'gsw' = { 'layout' = 'ch' },
},
'CL' = {
'es' = { 'layout' = 'latam' },
},
'CN' = {
'bo' = { 'layout' = 'cn', 'variant' = 'tib' },
'zh' = { 'layout' = 'cn' },
},
'CO' = {
'es' = { 'layout' = 'latam' },
},
'CR' = {
'es' = { 'layout' = 'latam' },
},
'CU' = {
'es' = { 'layout' = 'latam' },
},
'CZ' = {
'cs' = { 'layout' = 'cz' },
},
'DE' = {
'de' = { 'layout' = 'de' },
'dsb' = { 'layout' = 'de', 'variant' = 'dsb' },
},
'DK' = {
'da' = { 'layout' = 'dk' },
},
'DO' = {
'es' = { 'layout' = 'latam' },
},
'DZ' = {
'ar' = { 'layout' = 'ara' },
},
'EC' = {
'es' = { 'layout' = 'latam' },
},
'EE' = {
'et' = { 'layout' = 'ee' },
},
'EG' = {
'ar' = { 'layout' = 'ara' },
},
'EH' = {
'ar' = { 'layout' = 'ara' },
},
'ES' = {
'ast' = { 'layout' = 'es', 'variant' = 'ast' },
'ca' = { 'layout' = 'es', 'variant' = 'cat' },
'es' = { 'layout' = 'es' },
},
'ET' = {
'am' = { 'layout' = 'et' },
},
'FI' = {
'fi' = { 'layout' = 'fi' },
'se' = { 'layout' = 'fi', 'variant' = 'smi' },
'smi' = { 'layout' = 'fi', 'variant' = 'smi' },
},
'FO' = {
'fo' = { 'layout' = 'fo' },
},
'FR' = {
'fr' = { 'layout' = 'fr' },
'ka' = { 'layout' = 'fr', 'variant' = 'geo' },
},
'GB' = {
'en' = { 'layout' = 'gb' },
},
'GE' = {
'ka' = { 'layout' = 'ge' },
'os' = { 'layout' = 'ge', 'variant' = 'os' },
'ru' = { 'layout' = 'ge', 'variant' = 'ru' },
},
'GH' = {
'ak' = { 'layout' = 'gh', 'variant' = 'akan' },
'ee' = { 'layout' = 'gh', 'variant' = 'ewe' },
'en' = { 'layout' = 'gh' },
'ff' = { 'layout' = 'gh', 'variant' = 'fula' },
'gaa' = { 'layout' = 'gh', 'variant' = 'ga' },
'ha' = { 'layout' = 'gh', 'variant' = 'hausa' },
},
'GN' = {
'fr' = { 'layout' = 'gn' },
},
'GR' = {
'el' = { 'layout' = 'gr' },
},
'GT' = {
'es' = { 'layout' = 'latam' },
},
'HN' = {
'es' = { 'layout' = 'latam' },
},
'HR' = {
'hr' = { 'layout' = 'hr' },
},
'HT' = {
'es' = { 'layout' = 'latam' },
},
'HU' = {
'hu' = { 'layout' = 'hu' },
},
'IE' = {
'en' = { 'layout' = 'ie' },
'gd' = { 'layout' = 'ie', 'variant' = 'CloGaelach' },
},
'IL' = {
'he' = { 'layout' = 'il' },
},

Re: Reducing the complication of choices in console-setup udeb config: first thought

[Samuel Thibault]

Christian Perrier, le Sat 04 Jul 2009 22:19:19 +0200, a écrit :
  Ok, that's no regression from what we had previously and we have no
  AD locale for now, but should we really select keyboards by hand and
 
 There *is* a ca_AD locale...

Oh, right, I was looking for a cat_AD locale.

 However, I still think we should be selective in it. For instance, I
 don't see any purpose in having a keymap for Oriya/India while we
 don't support Oriya in D-I.

Why not?  Even if we're not able to provide messages in the native
language of the user, it's still _very_ useful for the user to be able
to type mails in his own language.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

iso9660, dots and install.386

[Samuel Thibault]

Hello,

Having a hard time remastering a CD with libisofs, I realized that while
iso9660 says that `Directory names shall not use dots at all', d-i
uses install.386 as directory name and thus libisofs was renaming into
install_386.

isolinux can handle filenames up to 31 without problems so could we
rename it to avoid the conflict?

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Reducing the complication of choices in console-setup udeb config: first thought

[Samuel Thibault]

Christian Perrier, le Mon 06 Jul 2009 07:15:45 +0200, a écrit :
  Why not?  Even if we're not able to provide messages in the native
  language of the user, it's still _very_ useful for the user to be able
  to type mails in his own language.
 
 This is not how the reasoning was made all along D-I early development
 and not how console-data was maintained.

Ok.

 Keymaps were added to the udeb of console-data only when the given
 language was supported. And, as of now, there has been no deep
 complaint that it should be done otherwise.

I fear that users who need the support just do not dare asking for it,
used to having poor support from Microsoft for instance.

 Still, that's quite a minor issue (whether we have 68 or 107 proposed
 keymaps).

Well, a menu with a hundred entries is maybe not so convenient. My
point was that there are a lot of different keyboards for the various
languages (please note that my script doesn't show any variant) and at
some point we could want to support them all, so we have to wonder how
to present the choice among a hundred of them.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Size numbers for the console-setup-enabled version of D-I

[Samuel Thibault]

Christian Perrier, le Wed 08 Jul 2009 21:42:13 +0200, a écrit :
 initrd size : +328Kb
 memory  : -136Kb!!
 
 
 Odd, isn't it?

Strings were not compressed in memory with kbd-chooser, were they?

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: [D-I] Please test Debian Installer with console-setup (3rd version)

[Samuel Thibault]

Christian Perrier, le Thu 09 Jul 2009 06:47:00 +0200, a écrit :
 Apparently, though, these No dead keys and Georgian variants
 appear for all layouts! I also get a Georgian variant for the
 France layout.
 Sounds like a bug somewhere.

No, there really are Georgian variants for fr and it, and a lot of
layouts have a nodeadkeys variant.

  At the _first_ boot, before the Setting the system clock. message, I got
  --8 (3)
  WARNING: undefined kernel key code for 153
  WARNING: undefined kernel key code for 160
  WARNING: undefined kernel key code for 162
  ... - other messages with other numbers
  WARNING: undefined kernel key code for 245
 
 I'm not sure about this one

That's odd, it's supposed to be fixed in the current release.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: remastering ISOs to append boot options

[Samuel Thibault]

Vincent Danjean, le Mon 06 Jul 2009 11:55:08 +0200, a écrit :
 I needed it to boot on a PC with no screen. It had only a terminal (an
 old french Minitel 1B) on its serial line.
   I did it by using the USB key boot methods and changing the correct files
 (I do not remember exactly what I did). But I remember having been surprised
 that booting on a serial line was not well documented in the Debian
 documentation.

I'm not sure how d-i is supposed to handle such case. debian-boot,
opinions?

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: [D-I] Please test Debian Installer with console-setup (3rd version)

[Samuel Thibault]

Anton Zinoviev, le Fri 10 Jul 2009 17:42:46 +0300, a écrit :
 On Fri, Jul 10, 2009 at 07:19:43AM +0200, Christian Perrier wrote:
  
  That means having a specific way to ask for layouts *in a single 
  question* mor eor less combining the layout/variant (and maybe model) 
  questions.
 
 This is exactly what the upstream of xkeyboard-config wants to achieve.  
 Only one question!  Not one question that includes all layouts around 
 the world but one question customized for your teritory.

Right, but I do agree that in the case of FR for instance, proposing
all of nodeadkeys, sundeadkeys, oss, oss_latin9, oss_nodeadkeys,
oss_sundeadkeys, latin9, latin9_nodeadkeyts, latin9_sundeadkeys, bepo,
bepo_latin9, dvorak, mac, bre, oci and geo variants is insane. Just
proposing the basic fr layout and the us layout should be fine.

Now the questions would rather be: should the selection be done by the
d-i team or (probably better) by upstream xkeyboard-config. I'll see
with upstream what they think about it.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: remastering ISOs to append boot options

[Samuel Thibault]

MaTa, le Sat 11 Jul 2009 15:39:06 +0200, a écrit :
 I'm sorry if I'm not an expert, but you can try with DEBIAN_FRONTEND=text
 boot parameter, to install using the serial port.

The question is: how do you type this with a PC that has no screen or
keyboard, just a USB plug?

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#536723: console-setup: shift+altgr vs altgr+shift

[Samuel Thibault]

Package: console-setup
Version: 1.36
Severity: normal

Hello,

With my current config, I can use altgr+shift+keycode 3 to type ?.
Sometimes I happen to type shift+altgr+keycode 3, and that does not type
?.  The reason is that dumpkeys shows

keycode 100 = AltGr
shift   keycode 100 = Alt
shift   control keycode 100 = Alt
shift   shiftl  shiftr  keycode 100 = Alt
shift   control shiftl  shiftr  keycode 100 = Alt
shift   ctrll   keycode 100 = Alt
shift   control ctrll   keycode 100 = Alt
shift   shiftl  shiftr  ctrll   keycode 100 = Alt
shift   control shiftl  shiftr  ctrll   keycode 100 = Alt

and indeed, ckbcomp fr prints

keycode 100 = AltGr Alt AltGr AltGr AltGr Alt AltGr AltGr AltGr AltGr AltGr 
AltGr AltGr AltGr AltGr AltGr AltGr Alt AltGr AltGr AltGr Alt AltGr AltGr AltGr 
AltGr AltGr AltGr AltGr AltGr AltGr AltGr AltGr Alt AltGr AltGr AltGr Alt AltGr 
AltGr AltGr AltGr AltGr AltGr AltGr AltGr AltGr AltGr AltGr Alt AltGr AltGr 
AltGr Alt AltGr AltGr AltGr AltGr AltGr AltGr AltGr AltGr AltGr AltGr AltGr Alt 
AltGr AltGr AltGr Alt AltGr AltGr AltGr AltGr AltGr AltGr AltGr AltGr AltGr 
AltGr AltGr Alt AltGr AltGr AltGr Alt AltGr AltGr AltGr AltGr AltGr AltGr AltGr 
AltGr AltGr AltGr AltGr Alt AltGr AltGr AltGr Alt AltGr AltGr AltGr AltGr AltGr 
AltGr AltGr AltGr AltGr AltGr AltGr Alt AltGr AltGr AltGr Alt AltGr AltGr AltGr 
AltGr AltGr AltGr AltGr AltGr AltGr AltGr

Shouldn't that be all AltGr?

Samuel

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages console-setup depends on:
ii  console-terminus  4.28-1 Fixed-width fonts for fast reading
ii  debconf [debconf-2.0] 1.5.26 Debian configuration management sy
ii  xkb-data  1.6-1  X Keyboard Extension (XKB) configu

Versions of packages console-setup recommends:
ii  kbd  1.15-1youpi Linux console font and keytable ut

Versions of packages console-setup suggests:
ii  locales   2.9-12 GNU C Library: National Language (
ii  locales-all [locales] 2.9-12 GNU C Library: Precompiled locale 
ii  lsb-base  3.2-22 Linux Standard Base 3.2 init scrip

-- debconf information:
* console-setup/variant: France
  console-setup/unsupported_options: true
  console-setup/modelcode: geniuskb19e
  console-setup/use_system_font:
  console-setup/fontsize: 8
* console-setup/unsupported_layout: true
  console-setup/layoutcode: fr
  debian-installer/console-setup/title:
  console-setup/codesetcode: Lat15
  console-setup/altgr: No AltGr key
* console-setup/ttys: /dev/tty[1-6]
* console-setup/codeset: # Latin1 and Latin5 - western Europe and Turkic 
languages
  console-setup/toggle: No toggling
* console-setup/fontface: VGA
* console-setup/fontsize-text: 8
  console-setup/compose: Left Logo key
  debian-installer/console-setup-udeb/title:
  console-setup/switch: No temporary switch
  console-setup/unsupported_config_layout: true
* console-setup/charmap: UTF-8
* console-setup/optionscode: grp:caps_toggle,compose:lwin,nbsp:level3n
  console-setup/unsupported_config_options: true
* console-setup/layout: France
  console-setup/variantcode:
* console-setup/model: Genius KB-19e NB
  console-setup/fontsize-fb: 8

-- 
Samuel Thibault samuel.thiba...@fnac.net
O ?a peut ?tre une madeleine ? sous munitions (avec des composants,
par exemple)
 -+- #runtime -+-



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: remastering ISOs to append boot options

[Samuel Thibault]

MaTa, le Sat 11 Jul 2009 18:21:16 +0200, a écrit :
 The PC have a RJ-45 connector? Can be that a net plug is a serial console
 too.

It could not have.  My question is about rs-232 console.

 I have installed Debian in SunFire V120 (Sparc maquine with RJ-45 connector
 serial console) through hyperterminal with the standard Debian installation
 CD
 
 A possible alternate way can be a preseed installation (a preconfigured file)

Ok, but how do you proceed?  Don't you need to either pass options to
the kernel or prepare a particular image with the preseed config file?

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: remastering ISOs to append boot options

[Samuel Thibault]

MaTa, le Wed 15 Jul 2009 22:40:28 +0200, a écrit :
 2009/7/15 Samuel Thibault sthiba...@debian.org
 I have installed Debian in SunFire V120 (Sparc maquine with RJ-45 
  connector
 serial console) through hyperterminal with the standard Debian 
  installation
 CD

 A possible alternate way can be a preseed installation (a preconfigured 
  file)
 
Ok, but how do you proceed?  Don't you need to either pass options to
the kernel or prepare a particular image with the preseed config file?
 
 The preseed file it's only a text file with options that you can choose in
 installer predefined in a file. To install a system using it needs to
 remaster de CD with a little modification in boot options and include the
 preseed file. It's no very complicated

That's precisely my point.  You are saying it's not very complicated,
but it's not very trivial either (no need to give me info, it's already
in the wiki etc), while I think it could be trivialized with a few
helper tools, I'm just wondering where such tools could be maintained
and advertized.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: remastering ISOs to append boot options

[Samuel Thibault]

MaTa, le Thu 16 Jul 2009 08:13:24 +0200, a écrit :
   • live-magic
   • debian-cd
   • simple-cdd
   • live-helper

I don't want to rebuild a whole CD from scratch, I want to just patch an
existing debian installer image that I have downloaded (our bought and
ripped), doing exactly what you mentioned earlier, but through the use
of just one command. I guess you missed the start of the discussion on
debian-devel:

http://lists.debian.org/debian-devel/2009/07/msg00162.html

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#541291: console-setup: No special characters after update

[Samuel Thibault]

Did you usually use a UTF-8 locale or a latin1 locale before?  It may
be that setupcon doesn't properly detect whether you're using a unicode
console or not.  This is configured in /etc/default/console-setup, maybe
the upgrade path didn't work for you.

Harald Braumann, le Thu 13 Aug 2009 13:31:51 +0200, a écrit :
 It is completely beyond me how setting an environment variable can
 influence keyboard/console output.

It can in that readline uses it to know how to process characters.

 It also makes it impossible for different users to use different locale
 settings.

They at least need to use either 8bit locales or UTF-8 locales,
according to the /etc/default/console-setup CHARMAP's parameter. The
POSIX locale can be both. Of course, don't expect to be able to type
non-ascii characters at the shell of a POSIX locale.

Samuel



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Keymap problems in D-I (was: Re: Bugs in the latest Debian Sid installer)

[Samuel Thibault]

Uwe Bugla, le Mon 24 Aug 2009 14:33:31 +0200, a écrit :
 If I do describe accurately a problem dealing with netinst image, and, as a 
 consequence, I am asked to perform a test with a netboot image (which has 
 technologically nothing to do with the netinst one - I do not have discless 
 workstations and I do not have NICs with boot PROMs), this is a gesture that 
 doesn't even intend to solve the problem itself, but instead tries to play it 
 down with the proved intention that I give up filing bugs.

??!!

Asking for checking with another kind of image is just the best way to
check whether the problem is in the common content of them or somewhere
in the difference between them.  So such test is definitely a good thing
to do.

 This is just one example of Mr. Perriers behaviour far beyond of good and bad 
 and this is the reason why I lose temper and thus decide not to cooperate 
 with 
 him any longer

I fear you won't find many people to work with.  Googling a bit gives me
a lot of results where developers have lost patience with you.

 a. I as user (administrator) give a precise description of the problem that I 
 have. Two or three feedback questions come back in some cases asking me to 
 describe the thing more precisely if I am not good enough doing the 
 description.
 b. But then the time is right to take action as far as the developer's part 
 is 
 concerned.

What you're forgetting is at least two things:

- the developer may have no idea where the problem is, and thus can of
  course _not_ take any action but asking for more tests.
- the developer may not have the time to take action _immediately_ and
  thus asks for more tests so that when he gets some time he will have
  more clues about the issue.  Acting this way asks for more time from
  you, yes, but overall the problem can be fixed sooner, as the
  developer can then take much more appropriate action.

 I guess there are far better developers than Christian Perrier, not only as 
 part of the Debian community.

When reading your mails they'll probably just refuse to interact with
you.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Keymap problems in D-I (was: Re: Bugs in the latest Debian Sid installer)

[Samuel Thibault]

Uwe Bugla, le Mon 24 Aug 2009 16:52:48 +0200, a écrit :
 The solution of the problem would have been to immediately have a look 
 whether 
 one of the following packages is part of the netinst image:
 Either:
 a. console-data plus console-common   or even
 b. console-setup

Possibly, yes, but that assumes having the time to do it.

   This is just one example of Mr. Perriers behaviour far beyond of good and
   bad and this is the reason why I lose temper and thus decide not to
   cooperate with him any longer
 
  I fear you won't find many people to work with.  Googling a bit gives me
  a lot of results where developers have lost patience with you.
 
 Nothing but superficial verbal crap! Next time please ask me before you 
 intend 
 to use anything like that against me, or I will strictly ignore you for being 
 superficial cause I hate superficial people! Otherwise stay quiet please!

Wow.

  What you're forgetting is at least two things:
 
  - the developer may have no idea where the problem is, and thus can of
course _not_ take any action but asking for more tests.
 
 He received two hints from two sides - so forget about that point..
 
  - the developer may not have the time to take action _immediately_ and
thus asks for more tests
 
 In that specific case more tests are completely irrelevant,

Why so? See the very first paragraph of my mail: the difference between
both was precisely the presence of console-setup, so making sure that
things work with one image and not with another while the developer is
away can not hurt, on the contrary.

so that when he gets some time he will have
more clues about the issue.  Acting this way asks for more time from
you, yes, but overall the problem can be fixed sooner, as the
developer can then take much more appropriate action.
 
   I guess there are far better developers than Christian Perrier, not only
   as part of the Debian community.
 
  When reading your mails they'll probably just refuse to interact with
  you.
 
 Their bad luck - not mine! I do prefer real men with butts in their trousers.

Wow.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#543478: console-setup: Add a way to set the font mapping

[Samuel Thibault]

Package: console-setup
Version: 1.44
Severity: normal

Some fonts (e.g. lat9u-10) do not embed their unicode mapping. They
can be selected through /etc/default/console-setup's FONT, but
no unicode mapping is loaded. There should be a way to set in
/etc/default/console-setup the mapping file to be used (e.g. lat9u.uni),
to be passed to setfont through the -u option.

Samuel

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages console-setup depends on:
ii  console-terminus  4.28-1 Fixed-width fonts for fast reading
ii  debconf [debconf-2.0] 1.5.27 Debian configuration management sy
ii  xkb-data  1.6-1  X Keyboard Extension (XKB) configu

Versions of packages console-setup recommends:
ii  kbd   1.15-3 Linux console font and keytable ut

Versions of packages console-setup suggests:
ii  locales   2.9-23 GNU C Library: National Language (
ii  locales-all [locales] 2.9-23 GNU C Library: Precompiled locale 
ii  lsb-base  3.2-23 Linux Standard Base 3.2 init scrip

-- debconf information excluded

-- 
Samuel Thibault samuel.thiba...@fnac.net
 La carte r�seau fournie par cybercable (sn2000) ne va-t-elle que sur
 bus isa ou peut-on aussi la mettre sur bus PCI.
 Merci de m'�clairer.
 -+- JP in le Neuneu P�te un C�ble : Une carte dans chaque port -+-



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

MS-DOS boot [Was: Installation report: SETUP.EXE dysfunctional]

[Samuel Thibault]

Lee Winter, le Sat 29 Aug 2009 22:09:14 -0400, a écrit :
 Getting an image of the CD onto a disk drive is not hard.  Even PC-DOS can
 handle that.  But once the image or copy resides on the drive the expected
 installation mechanism seems to be completely useless.

BTW, now that 518807 is fixed, is there a reason why

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518808
(Documentation about booting from DOS)

is still not fixed?

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: MS-DOS boot [Was: Installation report: SETUP.EXE dysfunctional]

[Samuel Thibault]

Lee Winter, le Sun 30 Aug 2009 10:35:46 -0400, a écrit :
 On Sun, Aug 30, 2009 at 8:06 AM, Samuel Thibault sthiba...@debian.org wrote:
 
 Lee Winter, le Sat 29 Aug 2009 22:09:14 -0400, a écrit :
  Getting an image of the CD onto a disk drive is not hard.  Even PC-DOS
 can
  handle that.  But once the image or copy resides on the drive the
 expected
  installation mechanism seems to be completely useless.
 
 BTW, now that 518807 is fixed, is there a reason why
 
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518808
 (Documentation about booting from DOS)
 
 is still not fixed?
 
 
 In my case booting from DOS or anything else is not necessary.

Maybe not necessary, but should work.

 The only requirement I have is to override the installer's insistence
 on mounting a CD and using it as the source for the install.

Are you using the hd-media image?

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: MS-DOS boot [Was: Installation report: SETUP.EXE dysfunctional]

[Samuel Thibault]

Lee Winter, le Sun 30 Aug 2009 11:42:15 -0400, a écrit :
 On Sun, Aug 30, 2009 at 10:44 AM, Samuel Thibault sthiba...@debian.org 
 wrote:
 Lee Winter, le Sun 30 Aug 2009 10:35:46 -0400, a écrit :
 
  The only requirement I have is to override the installer's insistence
  on mounting a CD and using it as the source for the install.
 
 Are you using the hd-media image?
 
 
 No, I am using the netinst image.

For the linux kernel  initrd too?

 Is the hd-media image less fanatical?

At least that's what you are supposed to use for an installation from an
HD...

http://www.debian.org/releases/stable/i386/apas02.html.fr#howto-getting-images-hard-disk

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: MS-DOS boot [Was: Installation report: SETUP.EXE dysfunctional]

[Samuel Thibault]

Lee Winter, le Sun 30 Aug 2009 18:26:29 -0400, a écrit :
 On Sun, Aug 30, 2009 at 11:54 AM, Samuel Thibault sthiba...@debian.org 
 wrote:
 
 Lee Winter, le Sun 30 Aug 2009 11:42:15 -0400, a écrit :
  On Sun, Aug 30, 2009 at 10:44 AM, Samuel Thibault sthiba...@debian.org
 wrote:
      Lee Winter, le Sun 30 Aug 2009 10:35:46 -0400, a écrit :
 
       The only requirement I have is to override the installer's
 insistence
       on mounting a CD and using it as the source for the install.
 
      Are you using the hd-media image?
 
 
  No, I am using the netinst image.
 
 For the linux kernel  initrd too?
 
 Not too.  Only AFAICT.

I'm lost.  What you need is hd-image's kernel and initrd, and a CD image
(whatever it is, actually).  In such case d-i shouldn't ever ask for a
real CD.

  Is the hd-media image less fanatical?
 
 At least that's what you are supposed to use for an installation from an
 HD...
 
 http://www.debian.org/releases/stable/i386/apas02.html.fr#
 howto-getting-images-hard-disk
 
 
 OK (i hink), mais ma francaise est trop ancien.

Damn nationalized links, it should have been

http://www.debian.org/releases/stable/i386/apas02.html#howto-getting-images-hard-disk

of course.

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#546640: console-setup: Lat15 name is confounding

[Samuel Thibault]

Package: console-setup
Version: 1.44
Severity: normal

Hello,

The Lat15 name is confounding: it could suggest that a latin15
charsets exists while it doesn't, and sounds similar to iso-8859-15,
which it does indeed implement, but not only. The description itself is
also not complete:

# Latin1 and Latin5 - western Europe and Turkic languages

It's not only latin1 and latin5, but also latin9, mandatory for the euro
symbol. Maybe just calling it Lat159 and adding latin9 to the list above
would solve the issue.

Samuel

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages console-setup depends on:
ii  console-terminus  4.28-1 Fixed-width fonts for fast reading
ii  debconf [debconf-2.0] 1.5.27 Debian configuration management sy
ii  xkb-data  1.6-1  X Keyboard Extension (XKB) configu

Versions of packages console-setup recommends:
ii  kbd   1.15-4 Linux console font and keytable ut

Versions of packages console-setup suggests:
ii  locales   2.9-25 GNU C Library: National Language (
ii  locales-all [locales] 2.9-25 GNU C Library: Precompiled locale 
ii  lsb-base  3.2-23 Linux Standard Base 3.2 init scrip

-- debconf information:
* console-setup/variant: France
  console-setup/unsupported_options: true
  console-setup/ctrl_alt_bksp: false
  console-setup/modelcode: geniuskb19e
  console-setup/use_system_font:
  console-setup/fontsize: 8
* console-setup/unsupported_layout: true
  console-setup/layoutcode: fr,brai
  debian-installer/console-setup/title:
  console-setup/codesetcode: Lat15
  console-setup/altgr: The default for the keyboard layout
* console-setup/ttys: /dev/tty[1-6]
* console-setup/codeset: # Latin1 and Latin5 - western Europe and Turkic 
languages
  console-setup/toggle: Alt+Caps Lock
* console-setup/fontface: VGA
* console-setup/fontsize-text: 8
  console-setup/compose: Right Logo key
  debian-installer/console-setup-udeb/title:
  console-setup/other:
  console-setup/switch: No temporary switch
* console-setup/unsupported_config_layout: true
* console-setup/charmap: UTF-8
* console-setup/optionscode: grp:alt_caps_toggle,compose:rwin,nbsp:level3n
  console-setup/unsupported_config_options: true
* console-setup/layout: France
  console-setup/variantcode: oss,
* console-setup/model: Genius KB-19e NB
  console-setup/fontsize-fb: 8

-- 
Samuel Thibault samuel.thiba...@fnac.net
...very few phenomena can pull someone out of Deep Hack Mode, with two
noted exceptions: being struck by lightning, or worse, your *computer*
being struck by lightning.
(By Matt Welsh)



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org