From 379a0406b6acd609e20abea644522a3aad6a74ac Mon Sep 17 00:00:00 2001 From: r12a Date: Wed, 10 Jul 2024 09:40:02 +0100 Subject: [PATCH] templates/gap-analysis/gap-analysis_template Various improvements, mainly to front matter --- .../gap-analysis/gap-analysis_template.html | 64 ++++++++++--------- 1 file changed, 34 insertions(+), 30 deletions(-) diff --git a/templates/gap-analysis/gap-analysis_template.html b/templates/gap-analysis/gap-analysis_template.html index 7f71411..bc40798 100644 --- a/templates/gap-analysis/gap-analysis_template.html +++ b/templates/gap-analysis/gap-analysis_template.html @@ -71,39 +71,40 @@
-

This document describes and prioritises gaps for the support of XXX on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders. This is a preliminary analysis.

+

This document describes and prioritises gaps for the support of the XX_SCRIPTNAME script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, such as HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.

-

This document describes and prioritises gaps for the support of XXX on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders. - -It is linked to from the language matrix that tracks Web support for many languages.

-

This document is an individual contribution, and is not currently a work item in any group, however, you can contact the Internationalization Working Group for more information. We welcome contributions to this and/or other documents.

+

This document describes and prioritises gaps for the support of the XX_SCRIPTNAME script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders. +It is linked to from the language matrix that tracks Web support for many languages.

+ +

The editor's draft of this document is being developed in the GitHub repository XX_REPOTITLE Language Enablement (XX_ACRONYM), with contributors from the W3C Internationalization Interest Group. It is published by the Internationalization Working Group. The end target for this document is a Working Group Note.

-
-

Introduction

+ + +
+

Introduction

+ +

Contributors

-

The original version of this document was created by Richard Ishida.

-

The original version of this document was created by XXXX. It was extended by Richard Ishida.

+

This document was created by Richard Ishida.

-

Other contributors can be found in the GitHub contributors list.

+

See also the GitHub contributors list for the XX_LANGNAME Language Enablement project, and the discussions related to the XX_SCRIPTNAME script.

@@ -116,11 +117,9 @@

About this document

The W3C needs to make sure that the needs of scripts and languages around the world are built in to technologies such as HTML, CSS, SVG, etc. so that Web pages and eBooks can look and behave as people expect around the world.

-

This page documents difficulties people encounter when trying to use the xxx language with the xxx script on the Web.

+

This page documents difficulties that people encounter when trying to use languages written in the XX_SCRIPTNAME script on the Web.

Having identified an issue, it investigates the current status with regards to web specifications and implementations by user agents (browsers, e-readers, etc.), and attempts to prioritise the severity of the issue for web users.

- -

A summary of this report and others can be found as part of the language matrix.

@@ -129,20 +128,6 @@

About this document

-
-

Work flow

- -

This version of the document is a preliminary analysis

- -

Gap analysis work usually starts with a preliminary analysis, conducted quickly by one or a small group of experts. Then a more detailed analysis is carried out, involving a wider range of experts. The detailed analysis may involve the development of tests, in order to illustrate issues and track results for browsers. The next phase is ongoing maintenance. It is expected that the resulting document will not be frozen: as gaps are fixed, this should be noted in the document. It is also possible that new gaps are noticed or arise, and they can be added to this document when that happens.

- - -
- - - - -

Prioritization

@@ -166,6 +151,21 @@

Prioritization

A cell can be scored as OK if the feature in question is specified in an appropriate specification, and is supported by user agents. A specification that is in CR or later and has two implementations in 'major' browsers will count. This means that the feature may not be supported in all browsers yet. (At some point in the future we may try to distinguish, visually, whether support is available in a specification but still pending in major browsers or applications.)

+ + + + + + +
@@ -176,6 +176,10 @@

Prioritization

+ + + +

Text direction