On Wed, Oct 22, 2008 at 7:25 PM, Maciej Stachowiak <[EMAIL PROTECTED]> wrote:
>
> I think the general approach you outline makes sense. I think the best way
> to avoid transcoding content that shouldn't be is to key it off of both font
> and site, assuming that a relatively limited list of fonts and sites would
> provide enough compatibility.
>
> That means the transcoding would have to be done late, once styles are
> resolved. This is entirely feasible; CSS text-transform already does late
> transformation of text based on styles, and it works right with copy/paste
> and everything:
>
> <div style="text-transform: uppercase">this is a test</div>

That's very interesting, I had not thought about this ability and
figured it would have to be added. I was leaning toward not doing
anything because of the complexity I saw in this project, but now it
seems like this could be practical.

Brett
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
  • ... Brett Wilson
    • ... Maciej Stachowiak
      • ... Brett Wilson
        • ... Jungshik Shi =?UTF-8?Q?n_(=EC=8B=A0=EC=A0=95=EC=8B=9D, _=E7=94=B3=E6=94=BF=E6=B9=9C)?=
          • ... Maciej Stachowiak

Reply via email to