lynx-dev Re: LYNX-DEV Lynx bookmark display problems

[Jacob Poon]

On Mon, 6 Apr 1998, Leonid Pauzner wrote:

> >      * From: Jacob Poon <address@hidden>
> >      * Date: Sun, 5 Apr 1998 17:09:07 -0400
> >      * Reply-To: address@hidden
> >      * Sender: address@hidden
> >      _________________________________________________________________
> 
> > BTW, just out of curiosity, what does character number 129 in ISO Latin 1
> > character set looks like?
> 
> There is no valid letters in 128-159 range for ISO LATIN 1 (2,3,4...)
> it is so called C1 control area, this may be a cursor moving codes in xterm
> for example.

Under Windows, codes 128-159 depend on the font for the 'ANSI character
set'.  Arial, Courier New, Times New Roman use following translations: 

128,129,141,142,143,144,157,158: square, probably a built-in Windows/True
Type mechanism to show undefined codes/characters. 

130: ",", a comma/cedilla symbol.

131: "f", or more correctly, florin or formula symbol

132: ",,", double commas/cedillae.

133: "...", 3 dots, or ellipsis.

134: "+", a dagger.

135: "+"
      + , double dagger, with two daggers joins vertically.

136: "^", caret/circumflex symbol.  Looks smaller than the one in code 94.

137: "%o", percent sign with 2 zeros on the right.

138: "v"
      S , capital S with caron.

139: "<", open angle bracket.

140: "OE", capital ligature OE.

145: "'", close single quotation.

146: "`", open single quotation.

147: "''", open double quotation.

148: "``", close double quotation.

149: ".", dot at the middle.

150: "-", en dash.

151: "-", em dash.

152: "~", tilde on top.  BTW, these fonts put the tilde of code 126 to the
middle.

153: "TM", trademark.

154: "v"
      s , small s with caron.

155: ">", close angle bracket.

156: "oe", small ligature oe.

159: ". ."
       Y  , Capital Y with umlaut/diaeresis.

Others:  Follows ISO-8859-1 definitions.

MS LineDraw uses IBM ASCII character set, except in code 127.

Symbol, while using a character set of its own, does not touch the codes
between 128 and 159.

BTW does anyone know if Lynx supports character translation fallback?  For
example, if a given DCS does cannot show certain codes, will Lynx use '7
bit approximations' for them instead? 

Also another thing about character translation:

Quoted from Lynx documentation:

> - some minor changes: sometimes invalid characters are displayed in a hex
>   notation Uxxxx (helps debugging, but I also regard it as at least not
>   worse than showing the wrong char without warning).

Shouldn't these untranslated characters be highlighted in someway (eg bold
attribute) to avoid confusions?  This will help more on debugging.  Also,
I also want an option to see them the way they are coded before codepage x
-> Unicode conversion, which will have notation 'Rxxxx' or '&#xxxx;'
(Netscape uses the latter for viewing 'document source').