That’s how I got a free netbook. The netbook had 32GB flash with windows and office occupying 27+GB. Then windows wanted to do an update - with an 8+GB file. Spot the problem. And windows can get quite annoying with updates. As the netbook could not be expanded, and attempts to redirect the update to a USB stick did not work, a newer netbook was bought, and I got the old one. Linux plus libreoffice plus a bunch of extras happily sat in 4GB…

I know. I was there, before Sanford Wallace invented the email spam and forced any sane SMTP server into password protections and whitelists.

“Low volume” vs. “A few hundred mails per month”

OK, what of the above?

You should put fixed IP addresses outside the DHCP allocation range. While a DHCP server might be smart enough to exclude a fixed address automatically, this is not a must. So better safe than sorry.

Which system/distribution/device does show this message?

I’m using IONOS for more than a decade now, and it works fine. I’m not into too much of web design, though, the personal web site is just a storage facility to move files around. I think they have quite some tools to develop professional web sites. Also allows for SSH access, which was helpful when I could not delete some files with filezilla.

Mail is good, too (Domain + 10 email accounts + catchall).

It is always a question of chosing the right tool for the right task. My core code is in C (but probably better structured than most C++ programs), and it needs to be this way. But I also do a lot of stuff in PERL. When I have to generate a source code or smart-edit a file, it is faster and easier to do this in PERL, especially if the execution time is so short that one would not notice a difference anyway.

Or the code that generates files for the production: Yes, a single run may take a minute (in the background), but it produces the files necessary for the production of goods of over 100k worth. And the run is still faster than the surrounding processes like getting the request from production, calculating the necessary parameters, then wrapping all the necessary files with the results of the run into a reply to the production department.

Well, you can use a tool, and acquire just enough knowledge to use it without too many accidents. And then simply give up on progressing any farther. Or you can keep digging into the mountain of knowledge to improve your skills farther and deeper. It is always your choice.

This is not a bandaid, this is the solution. What you try is, at least for this scenario, the band aid.

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.

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.

I already explained this in my post of yesterday in this thread. I’ve been the TeX admin at our university in my student times. I’ve been creating styles and \shipout macros. I know this stuff inside out. Heck, I’ve even read good parts of the source to understand some finer points.

If you work with LaTeX for five years and still have no idea what a hbox is or what that message means, you should not consider naming this “experience”.

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.

You could have used a thin space every four or eight hex digits, showing that it is not really a space but making it easier to read.

But you cannot blame TeX for not being able to break such a construct.

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…

As long as you let TeX do it’s job, you usually don’t get such issues. But there are many people who mistake TeX as a “Word for Scientists”, and just make the same mistakes they make in Word because they do not grok TeX.

Most probably a narrow column with a word near the end that TeX had problems hyphenating.

A line of text is basically a hbox. The words in this line are fixed in their lenght, so TeX distributes the space between them as evenly as possible to fill this hbox. It has a certain range for the length of a space, and tries to move words or parts of words with hyphenation around to stay in the OK range for the space width. If it can’t, it complains about under- or overfull hboxes.

I only tried GNOME long enough to see how crap it is, and have been a happy KDE user for years.

There are GSM modems that can be used by the server to send an SMS. I nearly bought one when it was cheap, but noticed just in time that the GSM level of that device was 3, which is no longer available here. And it needs a valid Sim card to work.