w3c / w3c/afrlreq

Joining for Adlam drop caps

Open
#6 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

l:ff question s:adlm
Dominant language
HTML
Stars
11
Forks
4
PR merge metrics
No merged PRs in 30d

Description

There are four possible permutations of joining behaviour when a drop cap appears. https://github.com/w3c/afrlreq/issues/4 shows one, but i'd like to be clear whether that is what is specifically required, or whether it's just what happened to be produced by the application that created the text.

I need to ask, since the CSS spec was recently changed to say that for cursive scripts the default effect produced would be: (a) use an isolated form for dropped character, (b) use a right-joining glyph for the character that follows it. The example in https://github.com/w3c/afrlreq/issues/4 doesn't match either of those, so it's important to clarify whether different rules need to be applied for Adlam.

Here are the 4 possibilities (the text doesn't make sense, i chose the first word to show clear shapes). Remember that there is no markup separating the first letter from the second, so in some cases the joining behaviour has to be inhibited by the application.

A. Non-joining + non-joining (this is my interpretation of the example in the other issue).

NN

B. Non-joining + joining (the current CSS proposal)

NJ

C. Joining + non-joining (an unlikely choice, perhaps)

JN

D. Joining + joining (like Uighur)

JJ

Which of the above would be the preferred approach for Adlam script text?

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 by reading the referenced afrlreq issue 4 and the CSS proposal described in this issue, then compare the four illustrated joining permutations. Determine which behavior is preferred for Adlam and record the resolved requirement; completion requires an agreed answer rather than a code change.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
internationalization
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.