ReSpec warnings on unused dfns
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 809
- Forks
- 66
- Avg merge
- 19m
- Merged PRs (30d)
- 1
Description
有一些术语我们在文中用<dfn>定义了，但是没有任何地方链接到该定义，所以ReSpec提出了warning。为了清除ReSpec提出的warning，有多种可能的解决方法：
- 删除
<dfn>，变回普通的文字 - 添加
lint-ignore类，让ReSpec跳过这个词的检查 - 在术语表里定义这个词（另见 issue #325），并删除这个
<dfn>
目前，这些术语包括：
- character frames (文字外框): https://github.com/w3c/clreq/pull/475
- character face (字面): https://github.com/w3c/clreq/pull/475
- Character advance (字幅): https://github.com/w3c/clreq/issues/472
- solid setting (密排): https://github.com/w3c/clreq/pull/475
- loose setting (疏排): https://github.com/w3c/clreq/pull/475
- Song (宋体): https://github.com/w3c/clreq/pull/475
- Kai (楷体): https://github.com/w3c/clreq/pull/475
- Hei (黑体): https://github.com/w3c/clreq/pull/475
- Fangsong (仿宋体): https://github.com/w3c/clreq/pull/475
- Line height (行高): https://github.com/w3c/clreq/pull/475
- interlinear annotation (行间注): https://github.com/w3c/clreq/pull/475
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the unused terms listed in the issue and the related pull request #475 and issue #472, then inspect the ReSpec warnings they produce. Decide for each term whether to remove the definition, add lint-ignore, or move it to the glossary as discussed in issue #325; done means the warnings are cleared.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100