Re: wrong rendering of certain HTML entities

Boris,

I am not sure. First of all, the subset sign does display properly on
IE, and I do not believe that is part of Arial either. Furthermore, if
what you say is true, I could copy a text from the the IE screen, paste
it into an UTF aware editor (I use jEdit) and, using a suitable unicode
font, I would see the right characters. I tried it and it does not work...

Ivan

Boris Motik wrote:
> Hello,
> 
> I don't think it is the encoding that confuses MSIE. It seems to me that the problem lies in the fact that MSIE draws the correct
> glyph, but it uses the currently selected font. Now the problem lies in the fact that, on Windows, the standard fonts (Arial, Times
> New Roman, etc.) do not contain the characters for the mathematical entities. Thus, to draw some of these characters, we would need
> to change the font to Symbol each time manually. This, of course, would be quite bad: Symbol is a font available only on Windows, so
> the page would render incorrectly with all other browsers.
> 
> BTW, there is one other problem with MSIE 7: it does not display the words "Grammar:" and "Example:" in the respective boxes. This
> is because MSIE doesn't support CSS correctly.
> 
> I really believe that we should not worry about MSIE. At best we can put a disclaimer on the documents saying that the documents are
> best viewed with a W3C-compatible browser.
> 
> Regards,
> 
>  Boris
> 
>> -----Original Message-----
>> From: public-owl-wg-request@w3.org [mailto:public-owl-wg-request@w3.org] On Behalf Of Bijan Parsia
>> Sent: 03 November 2008 12:51
>> To: Sandro Hawke
>> Cc: Ivan Herman; Michael Schneider; public-owl-wg@w3.org
>> Subject: Re: wrong rendering of certain HTML entities
>>
>>
>> On 3 Nov 2008, at 12:41, Sandro Hawke wrote:
>>
>>>> Just wondering... what about using UTF-8 everywhere instead of the
>>>> entities? That might work.
>>>>
>>>> I of course know that it is a royal pain to copy paste UTF
>>>> characters,
>>>> but it would make us independent of possible browser problems
>>> We could also use entities on the wiki and unicode in the TRs.  In
>>> fact,
>>> the tool chain goes to unicode (since it works with the text in DOM
>>> form) and back to entities at the end.  I decided to use entities
>>> in the
>>> TR to keep the html-diff between the TR and wiki clean.
>>>
>>> This is somewhat related to the notion that we should have PDF version
>>> of these documents.  That would give IE<8 users another option. If
>>> anyone really knows how to generate them, that'd be great.  (I'm
>>> not up
>>> to speed on the current tools there.  The last one I used was pre-
>>> CSS.)
>> PrinceXML does wonders. I have some students working with it now on
>> generating nice pdf from S5 presentations. It has good, page oriented
>> CSS support.
>>
>> Cheers,
>> Bijan.
>>
> 
> 

-- 

Ivan Herman, W3C Semantic Web Activity Lead
Home: http://www.w3.org/People/Ivan/
PGP Key: http://www.ivan-herman.net/pgpkey.html
FOAF: http://www.ivan-herman.net/foaf.rdf