Readit NewsThere are no technical solutions to what is fundamentally a problem of political culture.
Step 1 is establishing a secure means of communication.
/frysquint.jpg
vs=("a b" "c d")
for v in "${vs[@]}"
do #^♥ ♥^
echo "$v"
done
#= a b
#= c d
vs=("a b" "c d")
for v in ${vs[@]}
do #^! !^
echo "$v"
done
#= a
#= b
#= c
#= d
> [2] Another approach: instead of altering IFS, begin the loop with for arg in "$@" - double quoting the iteration variable. This changes loop semantics to produces the nicer behavior, and even handles a few edge cases better. The big problem is maintainability. It's easy for even experienced developers to forget to put in the double quotes. Even if the original author has managed to impeccably ingrain the habit, it's foolish to expect that all future maintainers will. In short, relying on quotes has a high risk of introducing subtle time-bomb bugs. Setting IFS renders this impossible.So does XSLT?
Even ascii used to use "overstriking" where the backspace character was treated as a joiner character to put accents above letters.
UTF-8 is so complicated, because it wants to be backwards compatible with ASCII.
What?! Google locked them out of Google. I'm sure they can still get search, email, and cloud services from many other providers.
The government can lock you away in a way that is far more impactful and much closer to "life stopped; locked out of everything" than "you can't have the data you gave us back".