W3C home > Mailing lists > Public > public-device-apis-log@w3.org > February 2023

[compute-pressure] Internationalization Checklist (#184)

From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
Date: Tue, 07 Feb 2023 08:49:05 +0000
To: public-device-apis-log@w3.org
Message-ID: <issues.opened-1573921675-1675759743-sysbot+gh@w3.org>
anssiko has just created a new issue for https://github.com/w3c/compute-pressure:

== Internationalization Checklist  ==
This issue is a record of the [Devices and Sensors Working Group](https://www.w3.org/das/)'s response to the [Internationalization Checklist](https://w3c.github.io/i18n-drafts/techniques/shortchecklist) for the [Compute Pressure API](https://www.w3.org/TR/compute-pressure/). Completed Checklist is required for the submission of the Internationalization review, one of the wide reviews tracked in #177.

>- [x] If the spec (or its implementation) contains any natural language text that will be read by a human (this includes error messages or other UI text, JSON strings, etc, etc),

The API specification contains two enums whose values are English strings:

```
enum PressureState { "nominal", "fair", "serious", "critical" };

enum PressureFactor { "thermal", "power-supply" };
```

The semantics of these strings are defined in the specification:
https://www.w3.org/TR/compute-pressure/#dom-pressurestate
https://www.w3.org/TR/compute-pressure/#dom-pressurefactor

These strings are only read by web developers and are not meant to be surfaces to the end user as is. In rare use cases where the state or pressure factor information is essential to be exposed to the end user (e.g. to aid debugging), web apps are expected to map these strings to language-aware strings as appropriate.

>- [ ] If the spec (or its implementation) allows content authors to produce typographically appealing text, either in its own right, or in association with graphics.

N/A

>- [ ] If the spec (or its implementation) allows the user to point into text, creates text fragments, concatenates text, allows the user to select or step through text (using a cursor or other methods), etc.

N/A

>- [ ] If the spec (or its implementation) allows searching or matching of text, including syntax and identifiers

N/A

>- [ ] If the spec (or its implementation) sorts text

N/A

>- [ ] If the spec (or its implementation) captures user input

N/A

>- [ ] If the spec (or its implementation) deals with time in any way that will be read by humans and/or crosses time zone boundaries

N/A

>- [ ] If the spec (or its implementation) allows any character encoding other than UTF-8.

N/A

>- [ ] If the spec (or its implementation) defines markup.

N/A

>- [ ] If the spec (or its implementation) deals with names, addresses, time & date formats, etc

N/A

>- [ ] If the spec (or its implementation) describes a format or data that is likely to need localization.

N/A

>- [ ] If the spec (or its implementation) makes any reference to or relies on any cultural norms

N/A

### Summary

Only consideration that applies is "If the spec (or its implementation) contains any natural language". This is an implementation detail in mainstream use cases.

Please view or discuss this issue at https://github.com/w3c/compute-pressure/issues/184 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 February 2023 08:49:07 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 7 February 2023 08:49:08 UTC