Add requirement for character encoding in trunction

w3c / bp-i18n-specdev

Internationalization Best Practices for Spec Developers

https://w3c.github.io/bp-i18n-specdev/

Other

22 stars 24 forks source link

Closed aphillips closed 6 months ago

aphillips commented 7 months ago

Addresses #124 Addresses w3c/i18n-actions#62

Add a requirement with explanation such that byte length truncation needs to specify a character encoding (and that legacy encodings should be avoided)
Add links to glossary terms in this section in some places
Small tweaks to other text

netlify[bot] commented 7 months ago

Name	Link
Latest commit	ee3539ad67330a9aaaea6c52f9adc6ea900a356b
Latest deploy log	https://app.netlify.com/sites/bp-i18n-specdev/deploys/657b3278edf5350008315779
Deploy Preview	https://deploy-preview-125--bp-i18n-specdev.netlify.app/
Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

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

aphillips commented 6 months ago

Discussed in 2023-12-21 telecon and approved by the WG