Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
How can I learn how to create LaTeX styles?
The normal way when creating a LaTeX document is to start with something like.
\documentclass[a4paper]{report}
\documentclass[a4paper]{article}
\documentclass[a4paper]{letter}
And that seems to call a .cls (and a .sty) file like letter.cls,
that is controlling the actual layout of the document.
Is there a good way to learn how to create this type of "latex style files"?
Has someone created a howto, step-by-step or simply a good manual on the topic?
Thanks
Johan
update:
I guess that tex.stackexchange.com is the answer on how to continue learning LaTeX.
With questions like this: https://tex.stackexchange.com/questions/528/style-class-tutorials
There are two good papers in the PracTeX journal:
Minutes in Less Than Hours: Using LaTeX Resources by Jim Hefferon,
Rolling your own Document Class by Peter Flynn.
A very useful resource is LATEX2e for class and package writers.
This question is also discussed here: Style/class tutorials. You are kindly invited to use the links there and perhaps join the discussion there if you like.
This isn't a direct answer to your question, but may give you a better return on the time invested, depending on how you see your future use of LaTeX.
Memoir for documents, Beamer for presentations.
"All the LaTeX styles you'll ever
need!"
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I am kind of obsessed with how I document and organize my projects. I am curious about best practices for readme files, and looking to learn more about what should be in it. I am mostly using rails. But I believe that readme should make no assumptions about the reader and explain everything with from scratch. So what would be your ideal descriptive timeless readme file for web application projects? Also It would ve very helpful if you attach the readme files you like.
content? short info the about app? language, framework? screenshot? format? markdown vs plain? ideal deployment? etc..
If you don't make assumptions about the reader then plain text is the best choice. Any markup language needs to be parsed and converted which may not be possible when viewing the readme locally. Sites such as Github support various markup formats which is good but you're limited to what they support.
It terms of content: it should explain everything that the user would possibly want to do, such as compile, build, run, modify, et cetera.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I have been producing documents (both mathematical and non-mathematical) with Latex for about two years, and I feel rather confortable with it. Now I would like to learn Tex, but I wonder if there are any real reasons to do it rather than just for the fun of it... Is there really anyone using Tex when that person could well be using Latex?
"Learn TeX only if you would like to become a typesetter",
this is a memorable sentence our school project leader answered this question to my colleague years ago... :-)
LaTeX will do the job 99% people need. There is a perfect book about TeX - TexBook naruby, unfortunatelly in Czech only (I doubt it was translated). But just look at it just to get shocked and assure that you really don't want to learn TeX :-)
Advantage of plain tex over latex
reference: http://www.tug.org/pipermail/texhax/2009-October/013645.html
LaTeX moreover, gives very limited access to the features of the TeX
engine. This is just due to the effiency idea of LaTeX. When most urgent
things have been done and you can afford spending some time learning about
what is behind LaTeX and what TeX really offers.
This may help you in understanding difficulties with LaTeX,
why you need some extra packages for certain fine tuning, you may then mix
Plain TeX code into your LaTeX code for fine tuning, you can write your own
LaTeX packages getting more control of TeX ...
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am trying to format my book for a Kindle 3. I'm writing the book using LaTeX. I am ok with transferring the file in PDF format but I need it formatted to be small.
I have tried:
\documentclass[12pt,b7paper]{book}
\usepackage[top=0.5cm, bottom=0.5cm, left=0.5cm, right=0.5cm]{geometry}
But this is too small. I have also tried something like:
\usepackage[paperwidth=9cm, paperheight=12cm, top=1cm, left=1cm, right=1cm, bottom=1.5cm, includefoot]{geometry}
But that doesn't work well either. Has anyone found a good way to format a LaTeX PDF for the Kindle? (Not the big DX version.)
This works well. I found it important to remove paper size from the dvips command. Forgetting to adjust that setting through me off for a while.
\documentclass[12pt]{book}
\usepackage[paperwidth=9cm, paperheight=12cm, top=0.5cm, bottom=0.5cm, left=0.0cm, right=0.5cm]{geometry}
\special{papersize=9cm,12cm}
Why don't you convert the LaTeX to HTML and create a Mobipocket document from that? That way, the Kindle will be able to reflow the document, which it cannot do if you load it in PDF form.
This may be much more than you need, but it's worth pointing out that there's a much more comprehensive answer over on tex.stackexchange
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
Here is my problem:
Im writing my thesis using the book class. I want my thesis to be onesided (left and right margins of same size), but I would also like to use the fancyhdr package to give me chapter names in the pagehead of even pages and section names in the pagehead of odd pages.
Trying to do so together with the "oneside" option gives me a warning when compiling saying that the [E] option is useless when the book is "onesided".
Example code:
\documentclass[11pt,a4paper, oneside]{book}
...
\fancyhf{}
\pagestyle{fancy}
\headheight 20pt
\fancyhead[LE]{\rightmark}
Any good ideas would be much appreciated!
You could use two-sided pages and then set the margins manually, e.g. with the geometry package. More capable alternatives to the standard classes like scrbook or memoir support this out of the box, and also don't need the fancyhdr package.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
Does anyone have or know where to find o bibliography style file like IEEEtr or IEEEtran for BibLaTeX? I've been searching all over, but could only find the ones for BibTeX. BibTeX can't really do the things I want, but my thesis has to conform with the IEEE standards...
I'd be really thankful if anyone could give me a hint how to use IEEE styles with BibLaTeX
Thanks a lot, Simon
Good news,
biblatex-ieee was released (Feb/12) by Joseph Wright. See at http://www.mail-archive.com/ctan-ann#dante.de/msg03710.html
Greetings!
JF
\usepackage[style=ieee]{biblatex}
see Ieee style files for biblatex.
Well, I'm interested in the same thing - and I guess the answer is, biblatex can NOT use the style files that bibtex, like ieeetr.bst. The reason I think that is:
Re: Biblatex: "patent" record type
I'm currently working on porting a BibTeX style for my subject area
(chemistry) to biblatex.
CTAN: directory: /tex-archive/macros/latex/contrib/biblatex-contrib
biblatex-apa/
biblatex-chem/
biblatex-chicago/
... that is - apparently you have to build your own biblatex style, if you want to to be the same as a bibtex style.