this post was submitted on 11 Jul 2024
701 points (98.7% liked)

linuxmemes

21469 readers
1695 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
    •  

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS
    [email protected]
    [email protected]
    [email protected]
    701
    5 years of experience, yet still not clue what "Underfull \hbox" means (lemmy.world)
    submitted 4 months ago* (last edited 4 months ago) by [email protected] to c/[email protected]
    84 comments fedilink hide all child comments
     

    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.

    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 1 points 4 months ago* (last edited 4 months ago) (1 children)

    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.)

    [–] [email protected] 2 points 4 months ago (2 children)

    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.

    [–] [email protected] 2 points 4 months ago

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

    [–] [email protected] 2 points 4 months ago (1 children)

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

    [–] [email protected] 1 points 4 months ago (1 children)

    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.

    [–] [email protected] 2 points 4 months ago

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