7thSea/Current/DocBook/append-append.xml

<appendix>
  <title>Appendix — Notes</title>
  <section xml:id="october-6">
    <title>2023 October 6</title>
    <para>
      Created the Appendix it includes:
    </para>
    <itemizedlist>
      <listitem>
        <para>
          Introduction — Notes
        </para>
      </listitem>
      <listitem>
        <para>
          Characters — Notes
        </para>
      </listitem>
      <listitem>
        <para>
          Appendix — Notes
        </para>
      </listitem>
    </itemizedlist>
    <para>
      It probably will have an index at some point, but currently we
      don’t have a way that we want to note things in the index, or even
      much of an idea of how to we would even index things.
    </para>
    <para>
      I feel that I’ll for now put some technical stuff about the whole
      thing in this index.
    </para>
    <section xml:id="arrangement-of-chapters">
      <title>Arrangement of Chapters</title>
      <para>
        Currently we have Introduction and Characters, then the Appendix
        in the same order. But that might not continue as such. Moving
        stuff around probably will need to be noted here.
      </para>
      <para>
        As it currently stands the &quot;Hero&quot; or Character chapter
        is really hard to find stuff in the file as it’s 500 lines long,
        and it just takes a while to scroll through it.
      </para>
    </section>
    <section xml:id="line-lengths">
      <title>Line lengths</title>
      <para>
        Also, these long lines... Or what are paragraphs as a single
        line in the file, need to go as I come across them. It would be
        nice if it actually did it automatically. As this file currently
        is, it is 23 lines long, but it has multiple longer paragraphs
        formatted that way.
      </para>
      <para>
        After adding new lines, I end up with …35 lines. That’s a more
        realistic way to look at it. Also, it can help with finding
        where more specific errors are, as the long lines will be more
        listed as a single line, but the shorter lines can be each
        listed.
      </para>
      <para>
        The problem I’ve run into is reformatting when I end up changing
        a line in the middle of a paragraph. All of that can be handled
        on an as needed basis though.
      </para>
    </section>
    <section xml:id="makefile">
      <title>Makefile</title>
      <para>
        This isn’t so much the book itself, but it is kind of important.
        I have a Makefile created which hopefully allows the creation of
        the book at least for display purposes. I
        <emphasis>think</emphasis> the reason that the table of contents
        wasn’t correct, is because it needs to run through twice, or at
        least it <emphasis>might</emphasis> need to run through twice,
        to have the updates in the table of contents (and index I
        think).
      </para>
    </section>
    <section xml:id="closing-thoughts">
      <title>Closing Thoughts</title>
      <para>
        Most of what I have done in terms of this has been to just
        finish with notes on the changes for the day in the other
        sections of the appendix. I know that I have some notes here
        that should be dealt with better. I’ll get to them. I promise...
      </para>
    </section>
  </section>
  <section xml:id="october-7">
    <title>2023 October 7</title>
    <para>
      Mostly not doing much of anything today, but I decided to throw
      here a little playing with the LaTeXand a more
      &quot;authentic&quot; version...
    </para>
    <para>
      LaTeX
    </para>
    <para>
      $\Lambda\kern-0.1667em\raise.5ex\hbox{$\alpha$}\kern -.0625em\raise.5ex\hbox{$T\kern -.25em\lower.5ex\hbox{$\epsilon$}\kern -.125em \chi$}$
    </para>
    <para>
      These are just silly playing, but I feel they are worth keeping
      here for now.
    </para>
  </section>
  <section>
    <title>2023 October 20</title>
    <para>
        I haven't worked on this much for a while.  There is a bit of a major change in what I'm doing here.  I decided that I wanted to have more flexibility in my output formats (someone mentioned markdown as a format for print documents using Pandoc), so I have converted the previous version to DocBook, which I'm currently able to create a LaTeX file, which I can create a 
        PDF from.
    </para>
    <para>
        This is an improvement in many ways, as I hope that will make converting it to something like an epub or html document easier.  Though I'm not convinced of that yet.
    </para>
    <para>
        In some ways it is a lot worse though.  The PDF currently being produced is much worse.  Working in DocBook, is harder than working in LaTeX.  A lot of the formatting that was for LaTeX is lost, and may be a huge pain to restore in the end.
    </para>
    <para>
        While some of the formatting I did have was just not working, or not working well.  I had something that I could "work with."  This so far, is a step backwards, for reasons that don't entirely make sense to me.  
    </para>
    <para>
        Well, not entirely make sense to me, as in I don't see that this will end up being a better option in the end.
    </para>
    <para>
        So, I feel what I'm going to probably aim to do, is copy this change here, back to the LaTeX version.  If I'm going to do other versions, do the conversion based on that.  The current LaTeX version is actually preferable.  That is a worthwhile thing to have figured out.
    </para>
    <para>
        Also, I think having a working workflow to the point I currently have it, is also worthwhile, as it is certainly going to make things easier to handle when (and if), I decided to produce a different format than the LaTeX PDF/Print version.
    </para>
  </section>
</appendix>