|
L2h menu keys are usually case sensitive, so check the "Caps Lock" key. (They are case sensitive if there is at least one uppercase menu key.)
If you just resized a linux terminal window, the next key is kept in limbo. Linux does that to punish you for criticizing its inability of opening terminals of the correct 80x24 size. The best thing to do is press the - key after a resize. And apologize very sincerely too.
The error message "Operating system error" is a catch-all phrase for all problems that the author of l2h thought should not occur. Very likely, the problem is really with the author's lousy coding instead of the operating system. Try the suggestions of section Problems with l2h itself.
A careful user could go into file readlog.ind (inside the data subfolder of the system-files subfolder of l2h) and add it. And maybe also add a corresponding section to errors.html and warnings.html, as appropriate. Follow the existing format.
Or better, e-mail me the index.log file, with a note about the problem. Then I can add it to errors.html or warnings.html, and the log file reader. If everybody does that, then these files will be much more comprehensive, and everybody benefits. (Errors.html and warnings.html are available on the web for everybody, not just l2h users. And the l2h log reader can be used without l2h too.)
If you have error messages while running latex with the "l" key, these must be fixed first. See the corresponding section. Otherwise see l2hfu. Note that most of the described problems have been fixed inside l2h. Especially when you run latex2html inside the l2h menu, or using makewebpages.bat. If you cannot figure it out, contact me.
This deals with converting jpeg (.jpg) files using the converters in the "convert" subfolder of l2h. For jpeg images in web pages, see the previous item. Version 1 of l2h has very old jpeg converters. They will not recognize jpeg files with newer features. Version 1.1 of l2h, still to be posted as I write this, will have more recent, 2013, IJG jpeg version 9 converters. Jpeg files may also become damaged. The most common damage is that the final part of the jpeg is corrupt or missing. In that case, the 1.1 converters will salvage the first part. You may also want to consider trying to process the problem image with another program like Photoshop, the gimp, MS Paint, etc. Some useful links on fixing corrupt jpeg images by other means:
Xubuntu desktop files are not compatible with Ubuntu ones. What a surprise! On Xubuntu, you will need to go into the make_..._transparent.desktop files and add a backslash, \, in front of the # character. Note that this will disable the "call" of these files from a terminal as described in nonGUI.html.
It does not if there are spaces in the paths. And never did. At least now it works in single-file mode for such paths.
This section is for if you have trouble with l2h itself, or its installation, instead of with LaTeX (problems with making index.pdf), or with LaTeX2HTML (making web pages).
Before reading the rest of this section, first load the latest version of this document from here or here and so check the list of already known problems. After that, scroll down until you are back in the latest version of this section.
If the above did not work, here are some ideas:
The how_to_get_started.html instructions tell you to try processing one of the unmodified examples 1 through 4 first. Use this section if while doing that, the "l" key produces errors or major warnings.
Before reading the rest of this section, first load the latest version of this document from here or here and so check the list of already known problems. After that, scroll down until you are back in the latest version of this section.
If the above did not work, here are some ideas:
The how_to_get_started.html instructions tell you to try processing one of the unmodified examples 1 through 4 first. This section assumes that while doing that, the chosen unmodified document processed without problems using the "l" key, (if not, see that section). However, no pdf was produced.
Before reading the rest of this section, first load the latest version of this document from here or here and so check the list of already known problems. After that, scroll down until you are back in the latest version of this section.
If the above did not work, here are some ideas:
The how_to_get_started.html instructions tell you to try processing one of the unmodified examples 1 through 4 first. This section assumes that the chosen unmodified document processed without problems using the "l" key, (if not, see the corresponding section). However, no web-pages were produced.
Before reading the rest of this section, first load the latest version of this document from here or here and so check the list of already known problems. After that, scroll down until you are back in the latest version of this section.
If the above did not work, here are some ideas:
The how_to_get_started.html instructions tell you to try processing one of the unmodified examples 1 through 4 first. This section assumes that you could do everything OK there. However, when you switched to the unmodified example 5 or 6, a problem developed.
Before reading the rest of this section, first load the latest version of this document from here or here and so check the list of already known problems. After that, scroll down until you are back in the latest version of this section.
If the above did not work, here are some ideas:
The how_to_get_started.html instructions tell you to try processing one of the unmodified examples 1 through 4 first. This section assumes that you could do everything OK there. You could make the pdf and web pages with no problems. And, if appropriate, you could process one of the unmodified examples 5 or 6 too. However, you got into trouble with a modified document.
Before reading the rest of this section, first load the latest version of this document from here or here and so check the list of already known problems. After that, scroll down until you are back in the latest version of this section.
If the above did not work, here are some ideas:
The first thing to decide is where you should go for help. If the problem is a LaTeX one, you should use one of the resources mentioned in intro_to_latex. One problem with e-mailing the l2h author about LaTeX errors is that he knows relatively little about TeX and LaTeX. I usually google my problems, or try things until it works. Nothing you cannot do yourself. If you get error messages or serious warnings while processing your document with the "l" key, the problem is almost surely a LaTeX one. (There are exceptions, like when html is specifically involved in some way.)
If processing your document with the "l" key does not produce problems, but something else does, it is more likely to be a l2h problem. See the section on that.
|