w3c / bp-i18n-specdev

Internationalization Best Practices for Spec Developers
https://w3c.github.io/bp-i18n-specdev/
Other
26 stars 17 forks source link

Add correct string recommendations [I18N-ACTION-1216] #82

Closed aphillips closed 1 year ago

aphillips commented 2 years ago

Added, edited, and rearranged requirements. Added a link to the Design Principles doc.

These edits depend on additions to the glossary in a separate pull request. More work is needed here, particularly discussing when the choose USVString (which we don't mention) and making clear how to work with byte strings/encodings.


Preview | Diff

netlify[bot] commented 2 years ago

Deploy Preview for bp-i18n-specdev ready!

Name Link
Latest commit ff699d7b7090a06c809312975d2c33014b7ee92d
Latest deploy log https://app.netlify.com/sites/bp-i18n-specdev/deploys/639b5649eeeca80008ed0d6e
Deploy Preview https://deploy-preview-82--bp-i18n-specdev.netlify.app/
Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

xfq commented 2 years ago

The text looks good to me. I only have one suggestion: we should probably add a link to the specific section of the Design Principles doc, to make it easier to find.

And I agree that we should add an entry for "surrogate" to the glossary. I also mentioned it in https://github.com/w3c/i18n-glossary/issues/17

aphillips commented 1 year ago

Merging per teleconference of 2022-12-15