Bug#600425: cdebconf: text frontend for selection isn't documented enough
Hi,
untested, probably/surely incomplete and not working, just as an exercise:
===================================================================
--- debian/cdebconf-text-udeb.templates (revision 65058)
+++ debian/cdebconf-text-udeb.templates (working copy)
@@ -48,6 +48,11 @@
# :sl4:
_Description: Prompt: '%c' for help, default=%s>
+Template: debconf/text-prompt-default-multiselect
+Type: text
+# :sl4:
+_Description: Prompt: '%c' for help, default=%s, multiple choices separated
by spaces>
+
Template: debconf/cont-prompt
Type: text
# :sl4:
Index: src/modules/frontend/text/text.c
===================================================================
--- src/modules/frontend/text/text.c (revision 65058)
+++ src/modules/frontend/text/text.c (working copy)
@@ -432,8 +432,8 @@
DISPLAY:
printlist (obj, q, count, choices_translated, tindex, selected);
- printf(question_get_text(obj, "debconf/text-prompt-default-string",
- "Prompt: '%c' for help, default=%s> "), CHAR_HELP, defval);
+ printf(question_get_text(obj, "debconf/text-prompt-default-multiselect",
+ "Prompt: '%c' for help, default=%s, multiple choices separated by
spaces> "), CHAR_HELP, defval);
get_answer(answer, sizeof(answer));
if (answer[0] == CHAR_HELP && answer[1] == 0)
{
What is missing? THe message needs to be added also to a .pot?
--
Melhores cumprimentos/Best regards,
Miguel Figueiredo
http://www.DebianPT.org
A Segunda 18 Outubro 2010 23:16:43 Samuel Thibault você escreveu:
> Miguel Figueiredo, le Mon 18 Oct 2010 22:48:48 +0100, a écrit :
> > i tried to reproduce it, i booted with DEBIAN_FRONTEND=text but everytime
> > i get:
> >
> > Prompt '?' for help, default=1 10>
> >
> > tasks 1 and 10 selected by default.
>
> Well, I'd say that's merely by luck :)
> For instance, if you boot in export mode you will get the "additional
> locales" question, where the issue is the same (and the default is
> empty). Of course that's just an instance, there are probably a lot
> others.
>
> Just a side note: this is actually a bug concerning accessibility, for
> the cases where a linear text is way simpler for the screen reader to
> follow, and thus using the dialog frontend is not really an option.
>
> Samuel
Reply to: