1 <?xml version="1.0" encoding="utf-8" ?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
3 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
4 <!--http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd-->
5 <html xmlns="http://www.w3.org/1999/xhtml"
8 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
9 <meta name="generator" content="TeX4ht (http://www.cse.ohio-state.edu/~gurari/TeX4ht/)" />
10 <meta name="originator" content="TeX4ht (http://www.cse.ohio-state.edu/~gurari/TeX4ht/)" />
11 <!-- xhtml,charset=utf-8,html -->
12 <meta name="src" content="user_21-5.tex" />
13 <meta name="date" content="2011-01-30 16:35:00" />
14 <link rel="stylesheet" type="text/css" href="user_21-5.css" />
17 <div class="footnote-text">
18 <!--l. 2389--><p class="noindent" ><span class="footnote-mark"><a
19 id="fn25x0"> <sup class="textsuperscript">25</sup></a></span><span
20 class="cmr-9">The current mechanism isn’t perfect, because it sits on top of the scan code to character code translation performed by the</span>
22 class="cmr-9">BIOS. This means that key combinations that don’t produce any useful character on the US keyboard will be ignored by LILO.</span>
24 class="cmr-9">The advantage of this approach is its simplicity.</span></p></div>