w3c / w3c/afrlreq

Lack of clarity on how to encode N'Ko te-kerende – FIXED !

Open
#36 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

doc:nkoo gap i:encoding i:segmentation l:nqo p:ok s:nkoo x:nkoo
Dominant language
HTML
Stars
11
Forks
4
PR merge metrics
No merged PRs in 30d

Description

This issue is applicable to N'Ko.

Certain constructs in N'Ko text mean 'each and every ....', and they appear with dash on the baseline with spaces either side. For example:
Screenshot 2023-05-16 at 17 51 06

This is also used in other locations where we might use a dash in Latin text.

The question is what is the appropriate character for the te-kerende and other similar looking uses.

More:

The GAP (2023)

Research showed that users are using ߺ U+07FA NKO LAJANYALAN with spaces either side for this. However, that character's main stated role in the Unicode Standard is to act like the Arabic tatweel and extend the baseline while joining the characters either side.

This approach works in all browsers.

See an [example](http://cormand.huma-num.fr/maninkabiblio/periodiques/silabosoona5.pdf) page 3, col 2 (from the right), below the picture.

The Unicode Standard doesn't provide any advice on this topic. The original proposal included a request for a te-kerende character, but it was not adopted.

Priority

This is already a de facto standard

Action taken

The question was raised at a Unicode Script Ad Hoc meeting.

Outcomes

The Unicode Script Ad Hoc committee considered the matter and agreed that the te-kerende should be represented using <space><lajanyalan><space>.

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

Read the issue's N'Ko section and the linked afrlreq N'Ko documentation, especially the te-kerende entry. The Unicode discussion and recorded outcome show that the question has already been resolved; any follow-up is done when the documentation consistently reflects that outcome.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, internationalization
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.