12.xhtml 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188
  1. <?xml version="1.0" encoding="utf-8"?>
  2. <!--
  3. h t t :: / / t /
  4. h t t :: // // t //
  5. h ttttt ttttt ppppp sssss // // y y sssss ttttt //
  6. hhhh t t p p s // // y y s t //
  7. h hh t t ppppp sssss // // yyyyy sssss t //
  8. h h t t p s :: / / y .. s t .. /
  9. h h t t p sssss :: / / yyyyy .. sssss t .. /
  10. <https://y.st./>
  11. Copyright © 2016 Alex Yst <mailto:copyright@y.st>
  12. This program is free software: you can redistribute it and/or modify
  13. it under the terms of the GNU General Public License as published by
  14. the Free Software Foundation, either version 3 of the License, or
  15. (at your option) any later version.
  16. This program is distributed in the hope that it will be useful,
  17. but WITHOUT ANY WARRANTY; without even the implied warranty of
  18. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  19. GNU General Public License for more details.
  20. You should have received a copy of the GNU General Public License
  21. along with this program. If not, see <https://www.gnu.org./licenses/>.
  22. -->
  23. <!DOCTYPE html>
  24. <html xmlns="http://www.w3.org/1999/xhtml">
  25. <head>
  26. <base href="https://y.st./en/weblog/2016/10-October/12.xhtml" />
  27. <title>Writing essays in XHTML &lt;https://y.st./en/weblog/2016/10-October/12.xhtml&gt;</title>
  28. <link rel="icon" type="image/png" href="/link/CC_BY-SA_4.0/y.st./icon.png" />
  29. <link rel="stylesheet" type="text/css" href="/link/basic.css" />
  30. <link rel="stylesheet" type="text/css" href="/link/site-specific.css" />
  31. <script type="text/javascript" src="/script/javascript.js" />
  32. <meta name="viewport" content="width=device-width" />
  33. </head>
  34. <body>
  35. <nav>
  36. <p>
  37. <a href="/en/">Home</a> |
  38. <a href="/en/a/about.xhtml">About</a> |
  39. <a href="/en/a/contact.xhtml">Contact</a> |
  40. <a href="/a/canary.txt">Canary</a> |
  41. <a href="/en/URI_research/"><abbr title="Uniform Resource Identifier">URI</abbr> research</a> |
  42. <a href="/en/opinion/">Opinions</a> |
  43. <a href="/en/coursework/">Coursework</a> |
  44. <a href="/en/law/">Law</a> |
  45. <a href="/en/a/links.xhtml">Links</a> |
  46. <a href="/en/weblog/2016/10-October/12.xhtml.asc">{this page}.asc</a>
  47. </p>
  48. <hr/>
  49. <p>
  50. Weblog index:
  51. <a href="/en/weblog/"><abbr title="American Standard Code for Information Interchange">ASCII</abbr> calendars</a> |
  52. <a href="/en/weblog/index_ol_ascending.xhtml">Ascending list</a> |
  53. <a href="/en/weblog/index_ol_descending.xhtml">Descending list</a>
  54. </p>
  55. <hr/>
  56. <p>
  57. Jump to entry:
  58. <a href="/en/weblog/2015/03-March/07.xhtml">&lt;&lt;First</a>
  59. <a rel="prev" href="/en/weblog/2016/10-October/11.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2016/10-October/13.xhtml">Next&gt;</a>
  61. <a href="/en/weblog/latest.xhtml">Latest&gt;&gt;</a>
  62. </p>
  63. <hr/>
  64. </nav>
  65. <header>
  66. <h1>Writing essays in <abbr title="Extensible Hypertext Markup Language">XHTML</abbr></h1>
  67. <p>Day 00585: Wednesday, 2016 October 12</p>
  68. </header>
  69. <img src="/img/CC_BY-SA_4.0/y.st./weblog/2016/10/12.jpg" alt="Pumpkins and autumn flowers" class="weblog-header-image" width="811" height="480" />
  70. <p>
  71. Current countdowns:
  72. </p>
  73. <ul>
  74. <li>5 days until my old domain registrar can no longer counter my charge dispute</li>
  75. <li>11 months worth of weblog entries to correct misuse of the <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> <code>&lt;q/&gt;</code> tag in</li>
  76. <li>249 scheme-specific <abbr title="Uniform Resource Identifier">URI</abbr>-parsing classes to write and add to <a href="https://git.vola7ileiax4ueow.onion/y.st./include.d">include.d</a></li>
  77. </ul>
  78. <p>
  79. My GT-i9100M went back to refusing to shut off again.
  80. I thought that I was going to go out and get a screwdriver after all, but by the time it came to that, that problem had gone away again.
  81. Having formatted my <code>/data</code> partition while trying to fix things, <a href="file:///storage/sdcard0/"><code>/storage/sdcard0/</code></a> had become read-only and I couldn&apos;t seem to find a way to fix it.
  82. It seemed that <code>/storage/sdcard0/</code> was supposed to be a symbolic link to <a href="file:///data/media/0/"><code>/data/media/0/</code></a>, but for some reason, it had become a regular directory.
  83. Of course, the directory that that directory was in was on a read-only file system, so that had made <code>/storage/sdcard0/</code> read-only as well.
  84. I tried deleting that directory and replacing it with the symbolic link, but after rebooting, my changes would always be reverted.
  85. All the while, while dealing with both the file system issue and the inability to shut off the device, the GT-i9100M kept complaining that it didn&apos;t like the file system formatting on the <abbr title="Secure Digital">SD</abbr> card.
  86. Strangely, it was still reading the files on the <abbr title="Secure Digital">SD</abbr> card, despite saying that the card was unreadable.
  87. I assumed that it was yet another problem that the device was having, but eventually, just to shut the thing up, I agreed to allow it to format the <abbr title="Secure Digital">SD</abbr> card.
  88. I figured that I&apos;d fix the formatting back to Ext4 later.
  89. However, upon agreeing to allow the device to format the <abbr title="Secure Digital">SD</abbr> card, a miraculous thing occurred.
  90. The device fixed the file system issues with the internal storage! The device had no problem with the actual <abbr title="Secure Digital">SD</abbr> card.
  91. It had been asking permission to fix itself! It was due to Google&apos;s confusing naming of the internal storage as the &quot;<abbr title="Secure Digital">SD</abbr> card&quot; that had effectively created a language barrier between my device and me.
  92. Oddly, this cleared up the shut down issue as well, at least for now.
  93. I might still go out to get a screwdriver in case this sort of thing happens again, but the day to do that isn&apos;t today.
  94. </p>
  95. <p>
  96. By the way, I&apos;ve also located some physical damage on the device&apos;s battery.
  97. I&apos;m told that a malfunctioning battery could potentially somehow prevent the device from shutting off, and though the only damage that I can see is to the plastic case on the end of the battery, it&apos;s a sign that there&apos;s been some sort of impact on the battery.
  98. Something inside may be damaged as well.
  99. </p>
  100. <p>
  101. I went over the paragraphs accompanying my <a href="https://y.st./en/coursework/UNIV1001/Notes.xhtml">notes on nuclear energy</a> and made some corrections, but I didn&apos;t go over the notes themselves.
  102. I also reread my essay on <a href="https://y.st./en/coursework/POLS1503/The_Canadian_Magazine_Dispute_and_an_Exemption_for_Whaling.xhtml">the Canadian magazine dispute and the attempts to get an exception for the global whaling ban</a> and touched that up a bit.
  103. Both were due today, so after making these last-minute changes, I submitted them.
  104. I also found that the University of the People submission form has an option to allow direct <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> input, so starting today, I&apos;m going to make heavy use of that.
  105. I already have to format my work in <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> before uploading it to my own website, so why format it a second time for the University of the People website if I don&apos;t have to? Additionally, <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> is much easier to control than the main submission form&apos;s formatting capabilities.
  106. Until today, I&apos;ve been using LibreOffice Writer to format my essays, then copying them and pasting them into the submission form.
  107. The submission form, for the most part, takes the formatting from LibreOffice without issue.
  108. However, it seems that when pasting something that&apos;s been indented with spaces, most of the spaces are lost.
  109. This only happens when pasting something from LibreOffice Writer though; it doesn&apos;t happen when pasting something from <a href="apt:geany">Geany</a>.
  110. Also, as I already knew, pasting something containing tab characters causes <strong>*all*</strong> tab characters to be removed.
  111. Being able to write up my submissions in <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> will prevent a lot of formatting difficulties.
  112. </p>
  113. <p>
  114. Josh Woodward just released three more songs, though I didn&apos;t notice the email until it was about time to do homework again.
  115. I&apos;ll have to listen to them later.
  116. These new songs are <a href="https://www.joshwoodward.com/song/LetsSlashGrandmasTires">Let&apos;s Slash Grandma&apos;s Tires</a>, <a href="https://www.joshwoodward.com/song/VeganZombies">Vegan Zombies</a>, and <a href="https://www.joshwoodward.com/song/BeyondtheSky">Beyond the Sky</a>.
  117. I&apos;ve actually heard Vegan Zombies before, and it&apos;s kind of funny.
  118. I don&apos;t like that all the &quot;vegan&quot; zombies relapse and eat human brains though.
  119. It sounds like it&apos;s saying that vegans are bound to relapse, with few if any exceptions.
  120. Perhaps I&apos;m reading too much into that though.
  121. </p>
  122. <p>
  123. The course registration period at University of the People started two days ago, but I didn&apos;t notice! I thought that they were going to send an email notification, so I wasn&apos;t watching.
  124. I should probably register for courses as soon as I have time, but not tonight.
  125. Tonight, I instead got started on the newly-available homework.
  126. </p>
  127. <p>
  128. I wondered if any other students had had the same idea as I did on the paper on our choice of the Canadian magazine dispute or the attempt to get an exception for the global ban on whaling, to I checked that out first.
  129. Our papers were supposed to be at least seven hundred words on <strong>*one*</strong> of the two topics.
  130. Instead, I wrote over seven hundred words on <strong>*each*</strong> topic, then merged the two essays, treating each of the former essays as a section of the larger essay, then added an introduction and conclusion to tie it all together.
  131. The result was a paper that was over three times the minimum word count and addressed both topics.
  132. Had anyone else done that as well? Two of the essays that I&apos;m supposed to grade only discussed one of the topics, which was fine.
  133. However, the third essay was disappointing; the student had had the inverse idea as I did.
  134. Instead of using the split topic as an excuse to put more effort in, they used it as an excuse to put <strong>*less*</strong> effort in.
  135. They wrote about both topics like I had, and their total word count was above the minimum, but their word count on each topic individually was lacking.
  136. By writing about both topics, they were able look like they&apos;d met the minimum word count without actually putting any effort or details into their assignment.
  137. I&apos;m not sure how that will effect the grade of the essay yet though, as the assessment form is strangely missing from the webpage.
  138. I&apos;m certainly going to mark them down if the word count is to be graded though, and I&apos;ll include in my note to them that that kind of attempt to get out of the effort isn&apos;t acceptable.
  139. </p>
  140. <p>
  141. I also took a look at the grading criteria for the notes on nuclear energy that we took.
  142. I tried to take good notes, but &quot;good&quot; is subjective.
  143. I find the facts about how things work more interesting, so that&apos;s what I took notes about.
  144. I threw in a few names and dates, but honestly, names and dates are useless, so I didn&apos;t include many of them.
  145. I worried that the grading criteria might ask that the notes be checked for certain criteria and that my notes wouldn&apos;t make the cut.
  146. I had been worried over nothing though! The rubric simply asks that the grader check to see that notes are present.
  147. I submitted plenty of notes, so I&apos;m good.
  148. </p>
  149. <p>
  150. My <span title="Online Education Strategies">UNIV 1001</span> reading assignment for the week consisted of six webpages:
  151. </p>
  152. <ul>
  153. <li><a href="https://pickthebrain.com./blog/5-ways-to-develop-independent-thought/">How to Develop Independent ThoughtPick the Brain | Motivation and Self Improvement</a></li>
  154. <li><a href="http://philosophy.hku.hk./think/critical/">[Module C] Critical thinking</a></li>
  155. <li><a href="http://www.mindtools.com/pages/article/newCT_91.htm">Attention Required! | CloudFlare</a></li>
  156. <li><a href="http://www.mindtools.com/pages/article/newTMC_5W.htm">Attention Required! | CloudFlare</a></li>
  157. <li><a href="http://www.mindtools.com/pages/article/newTMC_80.htm">Attention Required! | CloudFlare</a></li>
  158. <li><a href="http://www.mindtools.com/pages/article/newTMC_91.htm">Attention Required! | CloudFlare</a></li>
  159. </ul>
  160. <p>
  161. The second page turned out to be just an index leading to several other pages though, beefing up the reading assignment.
  162. I started the reading assignment, but by midnight, I still hadn&apos;t finished it.
  163. </p>
  164. <p>
  165. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  166. </p>
  167. <hr/>
  168. <p>
  169. Copyright © 2016 Alex Yst;
  170. You may modify and/or redistribute this document under the terms of the <a rel="license" href="/license/gpl-3.0-standalone.xhtml"><abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License version Three or later">GPLv3+</abbr></a>.
  171. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  172. My address is in the source comments near the top of this document.
  173. This license also applies to embedded content such as images.
  174. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  175. </p>
  176. <p>
  177. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  178. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F10-October%2F12.xhtml"><abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.1</a> specification and uses style sheets that conform to the <a href="http://jigsaw.w3.org./css-validator/validator?uri=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F10-October%2F12.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  179. </p>
  180. </body>
  181. </html>