From de1f02bbe3abebf51858de5d14ec2e43e71f9c61 Mon Sep 17 00:00:00 2001 From: ElnuDev Date: Tue, 14 Jun 2022 11:49:25 -0700 Subject: [PATCH] Adjust headings for table of contents, fix images in ff playthrough --- content/posts/cleaning-up-html-with-tidy.md | 4 ++-- .../index.md | 14 +++++++------- themes/sakura-hugo-theme | 2 +- 3 files changed, 10 insertions(+), 10 deletions(-) diff --git a/content/posts/cleaning-up-html-with-tidy.md b/content/posts/cleaning-up-html-with-tidy.md index 5194ae2..d05a322 100644 --- a/content/posts/cleaning-up-html-with-tidy.md +++ b/content/posts/cleaning-up-html-with-tidy.md @@ -12,7 +12,7 @@ To my knowledge, Hugo and most other generators don't have built-in beautifiers. In addition, if your site or blog has a more technical audience that might possibly view your site's source, you're going to give a better impression if you have clean markup. -### HTML Tidy +## HTML Tidy `tidy` is the solution for this. Started in 2003 by Dave Raggett, it provides a simple command line tool with [a large number of configuration options](http://api.html-tidy.org/tidy/tidylib_api_5.2.0/tidy_config.html) for how you want your HTML to be "tidied." It is free and open source, with its source code available on [GitHub](https://github.com/htacg/tidy-html5). @@ -32,7 +32,7 @@ tidy -o output.html input.html However, the default configuration will probably not be to your liking. We'll go over configuration in the next section. -### My `tidy` configuration for usage with Hugo +## My `tidy` configuration for usage with Hugo I have created a simple, one line command for first building my site with `hugo`, then cleaning up all of the generated files by first using `find` to get all `*.html` files in `public` (where Hugo dumps generated content), and then finally running `tidy` on each file. diff --git a/content/posts/final-fantasy-japanese-playthrough-part-1/index.md b/content/posts/final-fantasy-japanese-playthrough-part-1/index.md index 0387d2c..83ff36c 100644 --- a/content/posts/final-fantasy-japanese-playthrough-part-1/index.md +++ b/content/posts/final-fantasy-japanese-playthrough-part-1/index.md @@ -13,7 +13,7 @@ Today I decided to try the original [*Final Fantasy*](https://en.wikipedia.org/w In this post, I'll be first be quickly going over what I used to run the game, and then text that I went over and the vocabulary I gained from it. -### Setup +## Setup To play, I first downloaded the revision B game ROM from [WoWroMs.com](https://wowroms.com/en/roms/nintendo-entertainment-system/final-fantasy-japan/22274.html). Not surprisingly, it's absolutely *tiny*: the entire ROM is less than a megabyte. @@ -21,9 +21,9 @@ To run it, I used RetroArch, an open source emulation frontend. You can get it f RetroArch itself is not an emulator, however: it just provides the frontend and tools to use emulators. In order to load an emulator into RetroArch, you need to install a *core*. Personally, I use the *Mesen* NES/Famicom core. On the standard version of RetroArch available on their website, you can install new cores directly inside of RetroArch through the core downloader. However, due to Steam's limitations, on the Steam version this menu isn't available. Instead, you get cores buy getting the (free) DLC on Steam, all of which are listed on RetroArch's store page. The Mesen core I use is available on Steam [here](https://store.steampowered.com/app/1205330/RetroArch__Mesen/). -### Content +## Content -[![Final Fantasy Japanese opening text](../final-fantasy-1.png)](../final-fantasy-1.png) +![Final Fantasy Japanese opening text](final-fantasy-1.png) I didn't spend too long on it, but I did read through the opening text (see screenshot) and get vocab from it. @@ -43,7 +43,7 @@ The Famicom didn't have enough memory for kanji, so all the text is purely in ka > > そしてそのてには　それぞれクリスタルにぎられていた -### Kanji and attempted translation +## Kanji and attempted translation > この[世]{せ}[界]{かい}は　[暗]{あん}[黒]{こく}に[包]{つつ}まれている @@ -83,13 +83,13 @@ Here, [染]{そ}まる is the passive form of [染]{そ}める, to dye. So liter ***and in each of their hands was a crystal.*** -### The official NES version +## The official NES version Now, let's see how accurate this was! Here is the official NES version of the opening text. -[![Final Fantasy English opening text](../final-fantasy-2.png)](../final-fantasy-2.png) +![Final Fantasy English opening text](final-fantasy-2.png) > The world is veiled in darkness. The wind stops, the see is wild, and the earth begins to rot. > @@ -107,7 +107,7 @@ Overall, I was pretty close, but I made a couple mistakes. 3. 「そまりしとき」was actually 染まりし時, so *when* the world is becomes tainted with darkness, specifying the time condition for the prophecy. I didn't recognize the construction here of *verb nominalization* + し (nominalization of する) + 時. Because I didn't realize that this line was a direction quotation of the prophecy, I didn't pick up on this, even though I should have. What the し is doing here is that it's rather like 〜にする, and turns it from being simply *the time when the world is tainted with darkness*, 染まり時, to *the time when the world **becomes** tainted with darkness*. -### Conclusion +## Conclusion This was a really fun practice. I honestly need to spend more time consuming native Japanese material; I honestly study way less than I should and my vocabulary game isn't where it should be. I put all of the new/forgotten vocabulary terms from this into my [Anki](https://apps.ankiweb.net/) deck. diff --git a/themes/sakura-hugo-theme b/themes/sakura-hugo-theme index 8165163..15ecb62 160000 --- a/themes/sakura-hugo-theme +++ b/themes/sakura-hugo-theme @@ -1 +1 @@ -Subproject commit 8165163089fab0a42f57152147ec5c0401d47765 +Subproject commit 15ecb623e9379a16057e9873c542361f4cb11ff7