SPONSORED LINKS
On Friday, 24th October 1997, David Ross wrote: > (1) Will [a Briton] have service problems when he returns to the UK > [with a US machine]? (My impression was that all he has to do is > somehow reregister the machine...?) My guess would be Yes; he'd probably have to purchase a service contract for the UK, presuming that it's offered for a US machine. Of course, that's only a guess; I don't know for sure. > (2) How does he get the pound sign? (I assume that the Windows95 > British English setting will reassign some character to the pound - > but, if it is the US dollar sign, what happens to programs like TeX > which use this symbol?) Presuming that he only uses Windows 95 on the ThinkPad, the pound sign is always available (in the US/western European character set for Windows ["code page" 1252]) by turning the Num Lock on, holding down an Alt key, entering 0163 on the "numeric keypad" digits (i.e. the keys that substitute for a numeric keypad), and releasing the Alt key (and probably turning the Num Lock off). Alternatively, if the UK English keyboard input locale is installed and active, he could use Shift-3, as if he had a UK machine. Another possibility would be to run the Character Map accessory and doing cut-and-paste from it to wherever he'd need it. If he'd need the pound sign in a DOS session, he'd need to use Alt-156 (without the leading zero), which is its position in code pages 437 (US) and 850 (multinational), if not others. Code page 1252 is a superset of ISO 8859-1, so no character needs to be reässigned to the pound sign; it has its own position. In British seven-bit character sets, it was the US number sign position which got assigned to the pound sign. TeX, I'd guess, would accept whatever glyph is in the dollar sign position, rather than whatever position in which the dollar sign glyph happens to be; it's kind of like seeing yen signs rather than backslashes in some C code written in Japan, since at least one Japanese character set puts the yen sign in the US backslash position. Chris. -- Christian CAREY <ccarey@capaccess.org>