summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorThomas Voss <mail@thomasvoss.com> 2024-09-12 19:21:08 +0200
committerThomas Voss <mail@thomasvoss.com> 2024-09-12 19:21:08 +0200
commit052ebcbafc50a6e1e6e1bd26ff8e10c52699bc98 (patch)
treeafefcf6d2bee60b28fe70ff589bc51d246f9ce5a
parenta940f9ef0dd08898704dd29c24e41bb3acc8e1aa (diff)
:grep unicode | cdo s/unicode/Unicode/g
-rw-r--r--src/blog/extend/index.gsp26
1 files changed, 13 insertions, 13 deletions
diff --git a/src/blog/extend/index.gsp b/src/blog/extend/index.gsp
index c0bf478..069f255 100644
--- a/src/blog/extend/index.gsp
+++ b/src/blog/extend/index.gsp
@@ -74,7 +74,7 @@ html lang="en" {
}
figure {
- figcaption {-Kitty’s unicode input screen}
+ figcaption {-Kitty’s Unicode input screen}
img
alt="Kitty’s Unicode Input"
src="unicode.jpg"
@@ -86,24 +86,24 @@ html lang="en" {
Some of you have surely already figured out what my issue is with what
Kitty has done here, and why I think this is shitty software design.
For those that haven’t, allow me to ask you a question:
- @em{-what would be better than unicode input in your terminal?}
+ @em{-what would be better than Unicode input in your terminal?}
}
p {-
- The answer is simple: @em{-unicode input everywhere.}
+ The answer is simple: @em{-Unicode input everywhere.}
}
p {-
- Why should you be limited to unicode input in your terminal? What if
+ Why should you be limited to Unicode input in your terminal? What if
you’re texting your friend or sending an email, and want to include a
- unicode symbol such as ‘™’, or want to properly refer to a site you
+ Unicode symbol such as ‘™’, or want to properly refer to a site you
visited such as Ta’ Ħaġrat? Perhaps you even have a friend whose
surname is Mäkelä. Or maybe — you just want to send your friends a
middle-finger emoji sometimes.
}
p {-
- Wouldn’t it be nice if you had a @em{-global} menu for unicode input?
+ Wouldn’t it be nice if you had a @em{-global} menu for Unicode input?
Well turns out it’s actually really damn easy to do yourself, and
renders all that Kitty code absolutely useless.
}
@@ -111,7 +111,7 @@ html lang="en" {
h2 #scripting {-Writing the Script}
p {-
The first thing you’re probably going to need if you want to have your
- own unicode-input tool is a list of all the unicode characters out
+ own Unicode-input tool is a list of all the Unicode characters out
there. Luckily for you, I already went through the hell that is the
@a href="https://unicode.org" {-Unicode website} to find it for you.
}
@@ -134,7 +134,7 @@ html lang="en" {
}
p {-
- After processing, your unicode data file should look something like
+ After processing, your Unicode data file should look something like
this:
}
@@ -144,7 +144,7 @@ html lang="en" {
aside {
p {-
- You know how I inserted that sample of my unicode data file you see
+ You know how I inserted that sample of my Unicode data file you see
right above this? By using a small- and simple command-line tool in
the form of @code{-head} to grab the first 10 lines of the file, and
then using another small- and simple command-line tool in the form of
@@ -155,7 +155,7 @@ html lang="en" {
p {-
Now that you have your data file, we can begin scripting. The first
- thing we want is to get all of the names of the unicode characters.
+ thing we want is to get all of the names of the Unicode characters.
Turns out that is a very easy task thanks to the @code{-cut} utility.
We can split each line on a semicolon and extract the second field with
a simple command, and then we can compose it together with @code{-dmenu}
@@ -177,8 +177,8 @@ html lang="en" {
p {-
We have the users selection now, the @code{-$name} variable holds the
- name of the unicode character that the user selected. All that we need
- now is to actually get the unicode @em{-character} of our choosing.
+ name of the Unicode character that the user selected. All that we need
+ now is to actually get the Unicode @em{-character} of our choosing.
Luckily this is @em{-also} incredibly easy thanks to composition:
}
@@ -189,7 +189,7 @@ html lang="en" {
p {-
Congratulations! That entire script, which can be easily condensed down
into only 2 lines of code is all you need to create a graphical
- interface that allows you to pick a unicode character, and then copies
+ interface that allows you to pick a Unicode character, and then copies
your selection to your clipboard — and it was all done by taking simple
tools and combining them to make a greater application.
}