Bug 117109 - HTML attribute for Sanskrit not passed to rendering layer
Summary: HTML attribute for Sanskrit not passed to rendering layer
Status: RESOLVED DUPLICATE of bug 77568
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 420+
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-01 06:16 PDT by Steve White
Modified: 2013-06-03 02:27 PDT (History)
1 user (show)

See Also:


Attachments
proper display in Firefox on Linux (63.96 KB, image/png)
2013-06-01 06:16 PDT, Steve White
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Steve White 2013-06-01 06:16:42 PDT
Created attachment 203489 [details]
proper display in Firefox on Linux

Hi,

It seems the HTML attribute for Sanskrit language text
     lang="sa"
is not properly passed to the font rendering layer as OpenType tag 
     'SAN '

Firefox does it right, and using a font which makes a distinction betwen
Sanskrit and Hindi in Devanagari script, it makes a big difference with
fonts

Herre a test file: works 
  * with GNU FreeFont installed, and
  * using recent Firefox.
 ==========================================
<!doctype html>
<html>
<head>
    <title>Sanskrit vs Hindi</title>
<style type="text/css">
    body, td { font-family: freeserif; }
</style>
</head>
<body>
<p><em>Requires a font that distinguishes Sanskrit and Hindi.</em></p>
    <p>[ <span lang="sa">क्क</span> ] [ <span lang="hi">क्क</span> ]</p>
    <p>[ <span lang="sa">ङ्य</span> ] [ <span lang="hi">ङ्य</span> ]</p>
    <p>[ <span lang="sa">ष्ट्र्य</span> ] [ <span lang="hi">ष्ट्र्य</span> ]</p>
</body>
</html>
Comment 1 Alexey Proskuryakov 2013-06-01 18:49:19 PDT

*** This bug has been marked as a duplicate of bug 77568 ***
Comment 2 Steve White 2013-06-03 02:27:54 PDT
Hi, Alexey,

I'm surprised that you marked this report as a duplicate of bug 77568.

That bug is about the OpenType 'locl' feature -- this one is about the HTML 'lang' attribute.

These seem very different to me, and I'm sure relate to quite different parts of the source code.  I think it would be possible to fix the other bug and fail to fix this one.

Can you explain why the two bugs should be identified?