Context: LaTeX is a typesetting system. When compiling a document, a lot of really in-depth debugging information is printed, which can be borderline incomprehensible to anyone but LaTeX experts. It can also be a visual hindrance when looking for important information like errors.

  • Kairos@lemmy.today
    link
    fedilink
    arrow-up
    13
    arrow-down
    2
    ·
    edit-2
    4 months ago

    Its always bothered me that a language meant to get rid of formatting there seems to be a lot of fucking formatting. There’s no way to change the way things look outside of explicit formatting (like themes). It’s basically all formatting.

    And it’s a fucking mess. How in the fuck do I make titles? What about subtitles? Why is there no paragraph spacing? What’s the point of \title if it’s completely indistinguishable from other text?

    I want a markdown editor that supports math LaTeX and a ton of plugins. Markdown is dead simple for a reason.

    • BCsven@lemmy.ca
      link
      fedilink
      arrow-up
      9
      ·
      4 months ago

      Your editor shoul show you \title as another colour

      And subtitle would be \large after title line

      It is all formatting rules. But eliminates formatting the body text.

      At least you know output will be same, not like MS Word

      • Kairos@lemmy.today
        link
        fedilink
        arrow-up
        10
        arrow-down
        3
        ·
        4 months ago

        Oh thank goodness, body text is notoriously the hardest thing to format in a document

        • Treczoks@lemmy.world
          link
          fedilink
          arrow-up
          10
          ·
          4 months ago

          If you had seen some of the Word documents I have, you would not joke about that. People can really f-up text bodies.

          Example: one guy wanted to keep two paragraphs together. He did not know about the necessary formatting option, but he knew that chapter titles did what he wanted. So he made the first paragraph a title and just reset font, size, etc to resemble a normal text. F-ed up quite some things…

          • Kairos@lemmy.today
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            4 months ago

            That’s just an effect of shitty software that does too much (and yes I’m advocating for a simpler Word or something. Markdown is fine for 95% of use cases.)

            • Treczoks@lemmy.world
              link
              fedilink
              arrow-up
              2
              ·
              4 months ago

              Guess what? I have moved my large text layouts over to HTML. Creating printed TOCs in a PDF takes some effort, but once I got that under control, it worked. Takes a makefile, though, and a bit of discipline in the HTML file, but the result is surprisingly good.

              • Kairos@lemmy.today
                link
                fedilink
                arrow-up
                2
                ·
                4 months ago

                Anything you put that amount of effort into should be good, as long as you actually care about it.

              • bleistift2@sopuli.xyz
                link
                fedilink
                English
                arrow-up
                2
                ·
                4 months ago

                I’ve come to that conclusion, too. If only printing support were better, I wouldn’t write anything but HTML.

                • Treczoks@lemmy.world
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  4 months ago

                  Have you tried weasyprint? It turns .html into .pdf. Then I use a script with pdfinfo with the -dests option to get the page numbers of the chapters, mixes it with chapter titles from the .html file to create a ToC, which, in turn, gets included into the .html file again - just like TeX does it.

                  This is helpful in an environment where inputs are either HTML or EPUB files, and output is PDF for printing, HTML for the web site, and/or EPUB-formate.

                  • bleistift2@sopuli.xyz
                    link
                    fedilink
                    English
                    arrow-up
                    2
                    ·
                    4 months ago

                    I haven’t. Thanks for the tip. This might come in handy when we need to create automated documents again.

            • Treczoks@lemmy.world
              link
              fedilink
              arrow-up
              1
              ·
              4 months ago

              I don’t know if that person would have the intellectual capacity to actually understand the very concept of TeX: Writing a source and compiling it into a document. That idea would probably fry his mind.

    • CapeWearingAeroplane@sopuli.xyz
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      4 months ago

      I see a lot of strange takes around here, and honestly cannot understand where you are coming from. Like really: I’ve written several 100+ page documents with everything from basic tables, figures and equations, to various custom-formatted environments and programmatically generated sections, and I’ve never encountered even a third of these formatting issues people are talking about.

      You literally just \documentclass[whatever]{my doc type}, \usepackage{stuff} and fire away. To be honest, I’ve seen some absolutely horrifying preambles and unnecessary style sheets, and feel the need to ask: How are you people making latex so hard?

    • chellomere@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      4 months ago

      I’ve used LyX with good results, it’s a GUI that abstracts away many of the complexities of latex.