Aron Xu wrote:
> On my fresh Karmic installation, removing 49-sansserif.conf doesn't make
> sense for all sites, but changing it to what I attach here, everything
> works perfectly.
>
> ** Attachment added: "49-sansserif.conf"
> http://launchpadlibrarian.net/37404171/49-sansserif.con
this just happened to be working. "wqy-zenhei" is a file name,
not the font name. Because it does not match anything, it is
the same as to delete this file.
As determined from my tests in #38
<https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/207198/comments/38>,
I believe the fundamental
issue is that flash plugin does not support glyph fall-back, and
always use the first font to render everything, even for
glyphs it does not cover. It would be great that Adobe
developers are aware of this and work out a fix. However,
I strongly support to commit a work-around (many of them
are listed in this thread) first. This is a high-priority
bug, and effects millions of users. A work-around, even
not perfect, can save tons of hours before the upstreams
finish their fixes. Please react before the next release
arrives, otherwise, the wait will be hopelessly long.
Aron Xu wrote: launchpadlibrar ian.net/ 37404171/ 49-sansserif. con
> On my fresh Karmic installation, removing 49-sansserif.conf doesn't make
> sense for all sites, but changing it to what I attach here, everything
> works perfectly.
>
> ** Attachment added: "49-sansserif.conf"
> http://
this just happened to be working. "wqy-zenhei" is a file name,
not the font name. Because it does not match anything, it is
the same as to delete this file.
As determined from my tests in #38 /bugs.launchpad .net/ubuntu/ +source/ flashplugin- nonfree/ +bug/207198/ comments/ 38>,
<https:/
I believe the fundamental
issue is that flash plugin does not support glyph fall-back, and
always use the first font to render everything, even for
glyphs it does not cover. It would be great that Adobe
developers are aware of this and work out a fix. However,
I strongly support to commit a work-around (many of them
are listed in this thread) first. This is a high-priority
bug, and effects millions of users. A work-around, even
not perfect, can save tons of hours before the upstreams
finish their fixes. Please react before the next release
arrives, otherwise, the wait will be hopelessly long.