Re: lynx-dev Display of SGML Greek characters

[Steve White]

David,

The passage (below) means that the user agent may obtain a correct
display for SGML Math characters by whatever means is appropriate. 
It makes it very clear that supporting them through ISO10646 is
NOT the only possibility.  Given this statement, the comments in the
DTDs are to be taken as *suggested* mappings.

Your argument is academic, anyway.  Does the user care how the display 
is obtained, so long as it is correct?  To developers, neater code is 
better, but if you can't have neat, you go for correct.

The current handling of SGML Greek mathematical entities by Lynx is 
incorrect, because it negates the stated purpose of those entities.  

I think I have arrived at a solution, which involves mapping the 
SGML Greek mathematical entities to a different range.  I'll post
it in a moment.  Have a look!

Cheers!

On Date: Mon, 12 Aug 2002 21:32:39 +0100 (BST)
David Woolley <address@hidden> wrote
>>      "To support these entities, user agents may support full [ISO10646]
>>      or use other means. Display of glyphs for these characters may be
>>      obtained by being able to display the relevant [ISO10646]
>>      characters or by other means, such as internally mapping the
>>      listed entities, numeric character references, and characters to
>>      the appropriate position in some font that contains the requisite
>>      glyphs."
>
>All this is saying is that if, like Lynx, you do have an internal 10646
>representation, you can go through that, but you can also short cut the
>process and translate directly to the glyph.
>
>However, the names for the Greek characters are defined as SGML entities,
>which map to numeric entities, which are in 10646.  The formal definition,
>in the DTD and supporting entity files, clearly states that the names
>refer to specific 10646 characters.
>



; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden