|
|
Posted by Jim Higson on 06/20/06 21:15
>> Both Javascript and a plugin could work on a page-by-page basis.
>>
>> You last sentence makes it sound like you intend to parse each page's
>> HTML and CSS to determine what font(s) it is using. Is that the case?
>> Because you'll end up reimplementing (quirks and all) a hefty chunk of
>> the browser's parsing engine if that's the case.
>>
>
> What I am hoping to be able to do is to hook into the parsing engine and
> directly retrieve the results of the parse.
You can do this to the degree that the renderers provide hooks for you to
use. I can't imagine why they would provide these hooks, and probably most
renderers don't.
To what degree do you control the environment this is run on? If you can
deploy an open source browser you could add your own hooks to the engine to
get whatever you want.
There might be a js hack where you use the DOM to get the current style.
However, the sizes in the style might be specified in percentages, in which
case things become more difficult.
>> If you are willing to be less mysterious about the larger problem you're
>> trying to solve, we might be able to provide better advice. As it is,
>> we're left with a lot to guess at.
>
> New product development requires secrecy because first to market could
> provide the difference between success and failure.
Perhaps true. The product being impossible is probably a bigger difference
though :)
--
Jim
Navigation:
[Reply to this message]
|