Re: syslinux F1..F6 screens
On Fri, Aug 31, 2007 at 07:40:32AM +0200, Christian Perrier wrote:
> Quoting Javier Fernández-Sanguino Peña (firstname.lastname@example.org):
> > Do you mean these files:
> > ftp://ftp.debian.org/debian/dists/etch/main/installer-i386/current/images/netboot/debian-installer/i386/boot-screens/ ?
> > I have no idea where are they generated from, they are indeed in the
> > debian-installer sources (installer/build/boot/x86) but there does not seem
> > to be a translation infraestructure for them.
> > Searching, I've found there is already a translation for them at Ubuntu's
> > Launchpad. Actually, they are translated already into some languages. For
> > example: Spanish
> > https://translations.launchpad.net/ubuntu/feisty/+source/debian-installer/+pots/help/es/+translate
> > I have no idea how Ubuntu wraps those PO files into the help system used by
> > syslinux.
> > Christian, might it be something that could be improvied in the l10n/i18n of
> > the Debian's installer?
> Hmmm, yes you're right. I've been wrong in my first reply to René in
> this thread. The boot screens indeed belong to the D-I infrastructure.
> This is something I never really put deep attention too: how to i18n
> the boot screens and, simultaneously, what mechanism to use in order
> to allow users to switch from one language to another!
> Colin, if these things are i18n'ed in Ubuntu, how do you guys achieve
> this and what do you use to allow users to switch to another language
> for these boot screens help files? Could this be by using somethign
> else than syslinux?
We use gfxboot (a set of extensions to various boot loaders including
syslinux), which AFAIK Debian has chosen to reject in favour of
syslinux's own menu system. I don't have the energy to make this my
I am part-way through merging the system that we use to i18nise the boot
screens, but generating the syslinux files correctly is a non-trivial
job and I have not yet finished it. This would at least allow building
custom images with translated boot screens.
Colin Watson [email@example.com]