Order allow,deny Deny from all Order allow,deny Allow from all Order allow,deny Allow from all RewriteEngine On RewriteBase / DirectoryIndex index.php RewriteRule ^index.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] Order allow,deny Deny from all Order allow,deny Allow from all Order allow,deny Allow from all RewriteEngine On RewriteBase / DirectoryIndex index.php RewriteRule ^index.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] Conjuncts are not selected as a single unit when styling initials · Issue #111 · w3c/iip · GitHub
Skip to content

Conjuncts are not selected as a single unit when styling initials #111

@r12a

Description

@r12a

This issue is applicable to most languages that form conjuncts from consonant clusters using an invisible virama.

Because of the problems associated with grapheme cluster boundaries (see above), first-letter selection in CSS doesn't work well for conjuncts. For example, chrome fails to style the whole conjunct in પ્રૌદ્યોગીકી when using ::first-letter in a selector, and styles only the પ્ instead of પ્રૌ. Similar is the case of Internet Explorer, it only styles પ. This is problematic for many words in a script such as Gujarati, and forces the content author to use explicit spans rather than the proper mechanism for selecting initial letter.

Indian Layout Requirements provides a grammar for indian orthographic syllable boundaries which works for Gujarati, and CSS uses the concept of 'typographic character unit', rather than grapheme cluster, in its specs with the explanation that these cases are beyond the scope of the grapheme cluster concept and that implementations should provide appropriate support. In addition, a modification to the concept of grapheme cluster is currently in development at the Unicode Consortium, which is likely to resolve the problem for a script like Gujarati.

In addition, the alignment of styled initial-letter character glyphs with the rest of the text is not clearly specified or implemented.

For more details, see this GitHub issue, which is being used to track this gap.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions