Hello Jukka,
On 2011/09/14 3:33, Jukka K. Korpela wrote:
> I’m afraid this discussion, though on-topic in my opinion, has become
> rather specialized and technical (in terms of web techniques) for this
> list. I share Philippe’s concern for the change: changing the way
> browsers work in rendering texts is not a good thing when it changes the
> _default_ behavior.
>
> Even if a change, like using a ligature for “fi,” might be an
> improvement in the average, that’s not enough. There are too many things
> that may get broken that way—even if we don’t consider drastic (yet
> realistic) issues like intentionally monospace text.
>
> But I don’t think the Unicode Consortium, or the community supporting
> Unicode at large, could make a useful move in this issue.
Probably true.
> It really
> calls for common sense, rather than anything else, from browser vendors
> and CSS specs authors to realize that the default rendering should be
> left intact, as there are too many potential parameters to consider.
I think that rather than counting on their "common sense", it would be a
good idea for you (and anybody else concerned) to tell them.
Regards, Martin.
> I see this primarily as an _author_ choice. The user should have the
> last word, as he has if he really wants that, but for the most of it,
> typographic issues like ligatures are not something that users can and
> will deal with. Authors can be expected to do that, if they care, and it
> should not be too much of a burden to write an author stylesheet that
> suggest ligature behavior for all text, if that’s desirable and possible.
>
Received on Thu Sep 15 2011 - 21:50:57 CDT
This archive was generated by hypermail 2.2.0 : Thu Sep 15 2011 - 21:50:58 CDT