Since I'm not sure I'll be attending to the d-i meeting, I'd like to write down about the current status of g-i and what IMO needs to be done. My main concern is getting g-i as stable and reliable as d-i and , with this in mind, these are the topics that IMO are top priority: * Finalize fonts we need some udebs. In a nutshell we need the following: ttf-freefont (there's an udeb which can't be used) ttf-cjk-compact-udeb (OK) ttf-farsiweb (no udeb available) ttf-dejavu (no udeb available) This list is valid only once #254113 is fixed. ATM the workaround is using the tarballs available in [2] and looks like the only proble is Vietnavese for which some glyphs are missing. This is intended for beta2 languages: other languages will be supported after beta2 and will need other font files. * Fix AMD64 crash when switching to VT2 There's not a bug tracking this problem which IMO is very serious, since there's no way to access to a console. The fix for #339379 did not have any effect on this. * DFBTerm -> GtkWidget port (see #339855) Denis Oliver Kropp (author of Diretctfb and DFBTerm itself) recently showed interest in taking care of this. Besides being necessary, IMO this would be the coolest feature of g-i (Here I'm thinking about g-i as "just a nother interface" for the installer) * g-i themes (see #339735) Luca Bruno is currently working on a theme for the g-i and will also try to integrate a theme for visually impaired people ([1]). Themes are fully supported with 2.10.x libraries: it's probably not worth the effort trying to use them with 2.0.9 (missing libpixbuf) regards, Davide [1] http://cvs.gnome.org/viewcvs/gnome-themes/HighContrastLargePrintInverse/ [2] http://d-i.alioth.debian.org/gtk-frontend/
Attachment:
signature.asc
Description: Digital signature