search

w3c / baggage

Propagation format for distributed context: Baggage
https://w3c.github.io/baggage/
Other
46 stars 18 forks source link

i18n review checklist for baggage #93

Closed kalyanaj closed 1 year ago

kalyanaj commented 2 years ago

Short i18n review checklist is here

  1. [ ] 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 baggage spec doesn't contain any natural language text that will be read by a human.

  2. [ ] 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 for Baggage spec.

  3. [ ] 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 for Baggage spec.

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

    N/A for Baggage spec.

  5. [ ] If the spec (or its implementation) sorts text

    N/A for Baggage spec.

  6. [ ] If the spec (or its implementation) captures user input

    N/A for Baggage spec.

  7. [ ] 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 for Baggage spec.

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

    N/A for Baggage spec.

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

    N/A for Baggage spec.

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

    N/A for Baggage spec.

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

    N/A for Baggage spec.

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

    TODO: N/A for baggage spec. When we did the TAG review, there was a question about the name of the spec "Baggage" and whether it relies on any cultural norms, the TAG team was satisfied with the answer we gave: https://github.com/w3c/baggage/issues/83

aphillips commented 2 years ago

I have updated your review request and set a target date of 2022-05-27. Please let me know if you need the I18N WG review sooner than this.

kalyanaj commented 2 years ago

Thanks @aphillips for the update and for the above target date - that sounds good.

kalyanaj commented 1 year ago

Closing this issue as the review has been completed and issues have been filed for the follow-up items.