|
Feb 4 |
accepted | Why is tabu package reading what is inside \begin{htmlonly} tags? |
|
Feb 3 |
revised |
Why is tabu package reading what is inside \begin{htmlonly} tags? forgot to add item to code. |
|
Feb 3 |
asked | Why is tabu package reading what is inside \begin{htmlonly} tags? |
|
Jan 30 |
awarded | Critic |
|
Jan 30 |
accepted | How to use a counter to set section or chapter or subsection based on counter value? |
|
Jan 30 |
comment |
How to use a counter to set section or chapter or subsection based on counter value? @Eddy_Em, no I have not. This is advanced for me. As I said I am newbie in Latex programming. Will try it now and see. thanks. |
|
Jan 30 |
revised |
How to use a counter to set section or chapter or subsection based on counter value? added 480 characters in body |
|
Jan 30 |
asked | How to use a counter to set section or chapter or subsection based on counter value? |
|
Jan 28 |
comment |
syntax error when using tex4ht on Latex file that uses the standalone package @DavidCarlisle, I need this package, since I am building a tree that has latex files and I'd like to be able build each as separate, but also be able to build it all as one document. Please see this tex.stackexchange.com/questions/94822/… The idea is that I can make an HTML tree from the same latex files using htlatex, and also be able to make one PDF file from the whole tree using pdflatex. |
|
Jan 28 |
asked | syntax error when using tex4ht on Latex file that uses the standalone package |
|
Jan 28 |
accepted | handling href when importing separate standalone latex documents and assembling them into one document |
|
Jan 28 |
comment |
How to scale all mathematics of a document When you write \documentclass[1000pt]{article}, then the 1000 is ignored, becuase there is no suport for it. Only 10pt, 11pt, and 12pt can be used. |
|
Jan 28 |
comment |
How to scale all mathematics of a document Have you tried using the 12pt option to the documentclass as in \documentclass[12pt]{article} ? |
|
Jan 28 |
comment |
handling href when importing separate standalone latex documents and assembling them into one document excellent! It worked. I found that I can just use \providecommand{\currentimportpath}{\import@path} in both the parent and the child just the same and will work even when I build the child on its own. This is good, since in my tree, it is many levels, and a file can be both a child and a parent at the same time, so I need to be able to build at any level without changing things. Thanks again for your help. I also sent an email about the problem with currfiledir to the author of the package as you suggested. |
|
Jan 27 |
revised |
handling href when importing separate standalone latex documents and assembling them into one document added link to package |
|
Jan 27 |
revised |
handling href when importing separate standalone latex documents and assembling them into one document add problem description |
|
Jan 27 |
comment |
handling href when importing separate standalone latex documents and assembling them into one document Well, I have some bad news. I found a big problem in this package when I started to use it on my actual tree. Easier to explain with diagram. I'll add an update above. I need to also research this more to see if there is an option to avoid this. |
|
Jan 27 |
comment |
handling href when importing separate standalone latex documents and assembling them into one document Thank you so much! I did not know about this package. I just tried it on the above example, and it does worked very well. |
|
Jan 27 |
revised |
handling href when importing separate standalone latex documents and assembling them into one document clean |
|
Jan 27 |
asked | handling href when importing separate standalone latex documents and assembling them into one document |