Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Trunction's relationship to character encoding #124

Open
aphillips opened this issue Dec 14, 2023 · 1 comment
Open

Trunction's relationship to character encoding #124

aphillips opened this issue Dec 14, 2023 · 1 comment
Assignees
@aphillips
Labels
enhancement

Comments

@aphillips
Copy link
Contributor

While investigating an issue, I found that we don't talk about character encoding in relation to string truncation. We should.
@aphillips aphillips self-assigned this Dec 14, 2023
@aphillips
Copy link
Contributor Author

w3c/i18n-actions#62

aphillips added a commit to aphillips/bp-i18n-specdev that referenced this issue Dec 14, 2023
@aphillips
Add requirement for character encoding in trunction
ee3539a 
Addresses w3c#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
@aphillips aphillips mentioned this issue Dec 14, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aphillips aphillips

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aphillips