- <li>Currently, rEFInd can detect whether it's compiled for <i>x</i>86
- or <i>x</i>86-64 systems and displays this information in its
- "About" screen (<tt>AboutrEFInd()</tt> in <tt>main.c</tt>). I'd
- like to add detection for Itanium and ARM systems, but I have no
- way to test such changes.</li>
-
- <li>The code could be more flexible in its handling of the sizes of
- various graphical elements, and particularly drawn text. Prior to
- version 0.2.2, submenu text was invisible on UEFI-based PCs with
- 800x600 and smaller displays because of an inability to properly
- crop the graphics fields that hold the text. With version 0.2.2,
- I've put a band-aid on this problem by reducing the field size so
- that it now works on 800x600 displays, but smaller displays still
- suffer from this problem. This is just an example of the
- inflexibility of certain layout issues within rEFInd.</li>
-
- <li>Although the ICNS file format used by rEFInd supports multiple
- image sizes, if a size that rEFInd needs isn't present in the file,
- rEFInd can't use the icon. The ability to scale images to the
- desired size would be useful.</li>
-
- <li>I would like to be able to specify the volume on which a boot
- loader resides using a partition GUID value, but extracting a GUID
- from the partition data is harder than extracting the volume's
- label or counting up the filesystem numbers.</li>
-
- <li>Currently, if a filesystem's label comes up empty, rEFInd
- substitutes the size, so you get displays like <tt>boot
- EFI\foo\bar.efi from 90 GiB volume</tt>. I'd like to add more
- checks to substitute the GPT <i>partition</i> label if the
- <i>filesystem</i> label comes up empty, or add a filesystem type
- identifier to the size.</li>
-
- <li>The default_selection option in refind.conf could be improved by
- supporting a list of default options, so that if the first item
- isn't found, rEFInd will try to boot the second one in the list,
- and so on. This could be handy in case a driver fails to load, or
- to provide an override in case the user inserts a specific
- removable disk—by placing the removable disk's name first in
- the list, it will take precedence over the normal hard disk
- default.</li>
-
- <li>Along the lines of the previous item, the default_selection might
- be expanded to support some form of specification of disk types, as
- in a special entry for any optical disk or any external disk, no
- matter what its name is.</li>
+ <li>rEFInd's <tt>Makefile</tt>s and, to a lesser extent, C code,
+ support <i>x</i>86, <i>x</i>86-64, and ARM64 CPUs. EFI is also
+ available for Itanium (IA-64) and ARM32 CPUs, so I'd like to add
+ this support.</li>
+
+ <li>Currently, rEFInd can detect whether it's compiled for <i>x</i>86,
+ <i>x</i>86-64, or ARM64 systems and displays this information in
+ its "About" screen (<tt>AboutrEFInd()</tt> in <tt>main.c</tt>). I'd
+ like to add detection for Itanium and 32-bit ARM systems, but I
+ have no way to test such changes.</li>
+
+ <li>Further to the preceding, rEFInd's GPT-scanning code (used to
+ extract partition names) includes assumptions about byte order, and
+ so will work only on little-endian CPUs such as the x86 and
+ x86-64.</li>
+
+ <li>A way to set the color of the font would be useful for theming
+ purposes.</li>
+
+ <li>The program's font features could be greatly improved by enabling
+ use of a standard font format, by enabling use of non-ASCII
+ characters, and by enabling use of variable-width as well as
+ monospace fonts.</li>
+
+ <li>The <tt>default_selection</tt> might be expanded to support some
+ form of specification of disk types, as in a special entry for any
+ optical disk or any external disk, no matter what its name is.</li>