-
Notifications
You must be signed in to change notification settings - Fork 47
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.
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
Cut all trailing whitespace including funky unicode characters #393
Comments
Oh... U+00A0 are non breaking space characters in ISO/IEC 8859-1. aka LATIN-1. That is not UTF-8 all (there are invalid bytes and byte sequences in UTF8). Seeing this, we really must have some statement on the character encoding of our source documents for asciidoc and the markdown sources. This is not a statement about how to encode characters in the CF conforming data files. |
squaregoldfish
added a commit
to squaregoldfish/cf-conventions
that referenced
this issue
Sep 14, 2022
squaregoldfish
added a commit
to squaregoldfish/cf-conventions
that referenced
this issue
Sep 14, 2022
Removed all found whitespaces, including unicode non-breaking spaces
Merged
Merged
Repository owner
moved this from In Progress
to Done
in Housekeeping at 2022 workshop
Sep 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The AsciiDoc files, newly cleaned up as part of #387, still have trailing whitespace, including whitespace in the form of some funky unicode characters, e.g.
U+00A0
, which should be removed for code hygiene.Suggested as part of abiding by style guides in #373 (comment). While the specific style guides are being debated, all (sensible ones) will advocate for no trailing whitespace, so this is not controversial and can be done immediately, and should be done as one, like with the first stage clean-up #387, to aid reviewing and avoiding creating merge conflicts.
Assigning myself to try to do this now.
The text was updated successfully, but these errors were encountered: