- From: himorin / Atsushi Shimono via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Mar 2023 11:22:43 +0000
- To: public-i18n-archive@w3.org
@aphillips Thank you for deep consideration. I've thought of that style of table a bit, but haven't went to that direction since that overlaps with next table... If we are to propose adding media types into a table of link relation, I'd rather propose to merge two, something like: | Relation-Type | Supported Media Types | Constraints | Remarks | |---|---|---|---| | `icon` | `image/png`, `image/jpeg` | | | | `service-doc` | `text/plain`, `text/html`, `text/markdown`, `text/pdf` | Linked files MUST use the UTF-8 character encoding. | Human readable documentation | Keeping two separated tables, both of which contain similar information (mime types), could be confusing for readers, and also difficult to compile information. With the last paragraph in @aphillips comment, attached below the integrated table, seems to be easier to tell all at one time. -- GitHub Notification of comment by himorin Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/1664#issuecomment-1461841696 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 March 2023 11:22:44 UTC