w3c / w3c/clreq

Prioritization of different typographic features

Open
#458 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
809
Forks
66
Avg merge
19m
Merged PRs (30d)
1

Description

We can consider marking the importance of different typographic features in some way (kind of like the WCAG conformance levels), such as:

  • Must-have features
  • Important features
  • Features only used in advanced publishing

I think this information is useful to spec writers, {browser, e-book reader, word processor, desktop publishing software} vendors, and content authors/developers alike, because they can refer to the importance levels to determine priorities when writing specs, implementing specs, and creating content using features in software.

Currently, some prioritization information can be seen in the Gap Analysis document, but it is gap-oriented and not instructive enough (for example, for a vendor trying to implement a new browser).

Here are a few example features:

Must-have features
Important features
Features only used in advanced publishing

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Gap Analysis document and the linked sections covering punctuation, spacing, line breaking, vertical writing, Bopomofo, pinyin, and paragraph or line adjustment. Establish an agreed prioritization scheme, decide how it should be represented in the requirements, and apply it consistently to the relevant features.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation, internationalization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.