[i18n-activity] iTXt should be preferred (#1617)

aphillips has just created a new issue for https://github.com/w3c/i18n-activity:

== iTXt should be preferred ==
## Proposed comment

Keywords and text strings
https://www.w3.org/TR/2022/WD-png-3-20221025/#11keywords

> In the [tEXt](https://www.w3.org/TR/2022/WD-png-3-20221025/#11tEXt) and [zTXt](https://www.w3.org/TR/2022/WD-png-3-20221025/#11zTXt) chunks, the text string associated with a keyword is restricted to the Latin-1 character set plus the linefeed character. Text strings in [zTXt](https://www.w3.org/TR/2022/WD-png-3-20221025/#11zTXt) are compressed into [zlib](https://www.w3.org/TR/2022/WD-png-3-20221025/#dfn-zlib) datastreams using [deflate](https://www.w3.org/TR/2022/WD-png-3-20221025/#dfn-deflate) compression (see [10.3 Other uses of compression](https://www.w3.org/TR/2022/WD-png-3-20221025/#10CompressionOtherUses)). The[ iTXt](https://www.w3.org/TR/2022/WD-png-3-20221025/#11iTXt) chunk can be used to convey characters outside the Latin-1 set. It uses the UTF-8 encoding [[rfc3629](https://www.w3.org/TR/2022/WD-png-3-20221025/#bib-rfc3629)]. There is an option to compress text strings in the [iTXt](https://www.w3.org/TR/2022/WD-png-3-20221025/#11iTXt) chunk.

The `iTXt` type, which is internationalized, should probably be more prominent in this paragraph and ideally should be recommended. This paragraph might say instead:

> The `iTXt` chunk uses the UTF-8 encoding and can be used to convey characters in any language. There is an option to compress text strings in the `iTXT` chunk. `iTXt` is RECOMMENDED for all text strings, as it supports Unicode. There are also `tEXt` and `zTXt` chunks, whose content is restricted to the printable Latin-1 character set plus the linefeed character. Text strings in `zTXt` are compressed into `zlib` datastreams using [deflate] compression (see 10.3 etc.)

Note the addition of the word "printable" to the description of the Latin-1 character set in my proposal: I think this is missing from the current text.


## Instructions: 

This follows the process at https://w3c.github.io/i18n-activity/guidelines/review-instructions.html

1. Create the review comment you want to propose by replacing the prompts above these instructions, but **LEAVE ALL THE INSTRUCTIONS INTACT** 

2. Set a label to identify the spec: this starts with s: followed by the spec's short name. If you are unable to do that, ask a W3C staff contact to help.

3. Ask the i18n WG to review your comment.

4. After discussion with the i18n WG, raise an issue in the repository of the WG that owns the spec. Use the text above these instructions as the starting point for that comment, but add any suggestions that arose from the i18n WG. In the other WG's repo, add an 'i18n-needs-resolution' label to the new issue. If you think any of the participants in layout requirements task force groups would be interested in following the discussion, add also the appropriate i18n-\*lreq label(s).

5. Delete the text below that says 'url_for_the_issue_raised', then add in its place the URL for the issue you raised in the other WG's repository. Do NOT remove the initial '§ '. Do NOT use \[...](...) notation – you need to delete the placeholder, then paste the URL.

6. Remove the 'pending' label, and add a 'needs-resolution' tag to this tracker issue. 

7. If you added an \*lreq label, add the label 'spec-type-issue', add the corresponding language label, and a label to indicate the relevant typographic feature(s), eg. 'i:line_breaking'. The latter represent categories related to the Language Enablement Index, and all start with i:.

8. Edit this issue to **REMOVE ALL THE INSTRUCTIONS & THE PROPOSED COMMENT**, ie. the line below that is '---' and all the text before it to the very start of the issue.

---


**This is a tracker issue.** Only discuss things here if they are i18n WG internal meta-discussions about the issue. **Contribute to the actual discussion at the following link:**


§ url_for_the_issue_raised


Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/1617 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 15 November 2022 22:02:49 UTC