You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To commit new content with the GitHub API, the content must be base64-encoded. Non-ASCII characters will cause window.btoa() to throw InvalidCharacterError.
Users will try to use special characters in text fields, especially in long from writing like in Long Description. Should we make the validator disallow non-ASCII characters? Or is there a way to encoded non-ASCII characters and have them still be properly parsed by whatever program is reading the produced YAML file?
The text was updated successfully, but these errors were encountered:
To commit new content with the GitHub API, the content must be base64-encoded. Non-ASCII characters will cause window.btoa() to throw InvalidCharacterError.
Users will try to use special characters in text fields, especially in long from writing like in Long Description. Should we make the validator disallow non-ASCII characters? Or is there a way to encoded non-ASCII characters and have them still be properly parsed by whatever program is reading the produced YAML file?
The text was updated successfully, but these errors were encountered: