Login Register Active topics. Cite does not work? I'm a relative newbie, but am getting into it and understanding more and more. I'm using one large 'master file' which includes the other relevant sections. I'm currently trying to work out how to get my citations to work. I've tried including natbib as my buddy used and also commenting it out which i will probably prefer.
- Ben the Mountain Man.
- Cancelling an "end of sentence" space.
- Essays of Encouragement;
- Devils Twin Swords Book 7 - Edited!
Either way i get a Latext Warning: Spaces around binary operation and relation symbols are flexible for operations they are both stretchable and shrinkable, for relations only stretchable , so they can participate to the space adjustments made on a line for achieving justification. Compiling too early and too often.
Now you are spending your time working on fixing formatting and such that will change as soon as you add more text anyway and all the floats will move anyway. Using floats when you don't have to. Floats are the devil , yet all tutorials use them. Most of the time I know where I want the image, at least roughly, and didn't know for ages that I could just insert the image without wrapping it in a float, so I'd spend ages trying to get stuff to stop floating down multiple pages, or into the wrong section, etc.
As this is attracting a lot of debate: When I started every example shows you to insert an image in a float, so I thought you had to use float. Even a couple of months ago I thought you needed to put a table in a table environment; I'd still have to look up how to make a non-floating table. This is a problem as a lot of the time I need an image in a certain place. For example, if I'm typesetting a homework problem Something I did a lot as an undergrad, and am now doing again when I'm writing questions I can't have that image floating down into a different question; my TA or prof isn't going to go hunting for it, they are just going to dock me marks And I don't want to confusing anyone working on my problem set!
Also as the h option is a joke they usually float far away. I don't mind if a figure floats a few paragraphs, but three pages away is bad: Same page as the discussion or facing page only. I should always be able to see both figure and text at the same time, unless there are exceptional circumstances or a very large text I cut some slack when writing my thesis, as there were so many figures they wouldn't all fit on the same page as the text. There are times floats are the right choice; I'm using one in the document I'm working on right now.
However, they are just as often the wrong choice, and a lot of new users don't realize this. Using outdated packages that some website gave you My group drives me crazy since they use very outdated packages that have been superseeded. Relying on GUI text editors instead of understanding what is happening People at work also drive me crazy with refusing to use anything but the compile button in WinEdt. If that doesn't automatically work, they refuse to use the package Thus no biber, no biblatex, etc.
Hard drives are large, dammit. But it fails every time I've given my coworkers a new package to use, causing us to have to go into the interface and have it manually install. Limiting yourself to what chemistry journals allow for everything I dream of one day being editor of a big chemistry journal, just so I can go to the AMS or APS and borrow their code.
This has things like not using macros , not redefining things, not using excess packages or in one case, not using packages AT ALL. Not being willing to put in time understanding LaTeX The people I work with just want a solution now. They aren't willing to put in any time into making it work; they want something that works now, since the journal will reformat it anyway, so if it works and gets vaguely close to what they want, good enough.
The compiler should be either pdflatex or xelatex among other possibilities. Understanding this better, helped me understand when references, citations and page numbering went wonky. Switching to emacs and using a custom scripted compile helped sort out the kinks. My own take on this question is more about the mistakes beginners make because of us. I made too many shameful mistakes and still do at times , but with my first private beta, I realised that many beginner mistakes were in fact my beginner LaTeX developer mistakes.
I hope it is not off-topic… but thinking back, I would think that most of my own beginner mistakes were also often developer or documentation-writer mistakes. We are generally good at writing documentations, but we sometimes have a hard time finding the right words for both beginners and experts. Most of the beginner mistakes mentioned here are not really in the books… or at least they don't show up as sections, tutorials, etc.
It is no wonder beginners first look things up on google. We don't write documentations on debugging what we assume will work it works in the hands of a TeXnician, not in the hands of someone who does things at random. Compile early, compile often as with 'test early, test often' is good advice when spending a lot of time working with complex documents and multiple included files. Doing by hands what LaTeX should handle. Basically this applies to all kind of systems. How many keyboard shortcut in Word to learn, how many packages to remember in LaTeX It always depend on how much one is going to use some software.
Another one on meta-level: Many have used hours to find out things that I could have tell in a minute. They spend a significant time trying to make some packages work together and looking for answers to their problem. They spend a significant time trying to customise the class to achieve a pleasant layout, while they wether have the needed programming skills neither most probably the design skills. Is there any LaTeX introduction or tutorial that emphasises the choice of a document class and provides useful resources catalogue, comparison of features, application domain to choose one?
It seems to me, most of them pick one article and stick to it for the whole tutorial, while it could be more useful—once the basics of text and math typesettings have been covered—to drop that generic class in favour of a specialised one. To put it in one sentance: I don't mean the details, but the 'big picture'. They are not generally good - and typically much poorer than alternative programmes - at the things they are not intended to do. Some questions boil down to requests for TeX solutions to the problem of brewing the perfect cuppa.
This is a perfectly reasonable aim but the best answer involves advising a non-TeX solution. Other questions essentially ask for TeX-based cat-herding solutions. The best answer in this case involves recommending against adopting the goal set out in the question. This is a shame since these really are the best answers in these cases and appreciating TeX's limitations, as well as its strengths, is key to using it effectively.
Cup of tea is from openclipart. Some users think that the EPS images are no longer needed after running latex so they can be deleted.
Actually it is wrong because dvips still needs the EPS. Some users aggressively remove any auxiliary files generated by pdf latex compiler before the next invocations. It makes the cross-referencing always end with?? These auxiliary files must not be deleted until the cross-referencing is properly done. Another common misbehavior is reading package or class documentations from TeX mirrors the worst case, they read from sites with obsolete contents even though they already installed the complete, up-to-date packages and classes.
The technical and object cases are, for example, as follows. It actually does not produce the expected result. Beginner sometimes use longtable inside table because they assume longtable is the longer version of tabular which is able to be sandwiched in table. Not reading an introduction and package documentation. Aside from answering questions on this site when I don't have a clue what I'm talking about? There is a similar Community poll on meta: I don't really see how this can get sensible answers, I voted to close as "too broad". Isn't this a sort of "everyone rant here" question?
The most common mistake is spending too long on TeX coding and not getting the document written. I was expecting "Not using emacs for coding". PauloCereda I can't believe anyone makes that mistake. The most common mistake is spending too long on TeX coding for answering TeX. SX, ignoring families and friends, but not getting their own document written. In my experience, this is not a beginners' mistake at all. Quite the opposite, in fact. DavidCarlisle Leslie Lamport gave an interview about 13 years ago, see here: Worrying too much about formatting and not enough about content.
Here are some common, non-esoteric mistakes I help people fix on a regular basis: Formatting section headers by hand, using literal numbers and manual spacing: Can you elaborate on point 8? This is my 1 pet peeve, too but from physicists in my case! Navarro Oct 24 '13 at I was the first to plus one you yesterday.
Edit on 2015/07/07:
Using LaTeX only works if you forget about the visual appearance or if you're a guru. In both cases you need the structure offered by LaTeX. MarcvanDongen - Wow, thanks for the compliment!! DONT Read tutorials that advise best practices from the stone age. Especially german LaTeX tutorials advise something like this in the preamble: This is the most important post up until now, in my opinion.
Way too many tutorials on the internet are outdated, and people learn only stoneage-style LaTeX! I don't have such symbols on my keyboard and it is a lot easier for me to type an accent that way instead of googling the character to find a copy I can copy and paste into my document. With minimal transitional pain I write German, English, Swedish and the odd French word without switching anything. And, of course, all the programming symbols are where you need them. Not using version management for your document.
Yeah, I'm lazy about this. I don't like taking the time to set up a repository for each new project.
LaTeX and Friends
This is so true! But I'd say it's even more of a trouble with Word documents. I have seen people having thesis directories containing files like: Then just use one and pack them all in there, but by all means use one. Or use git and register separate projects as submodules. But versioning and Word documents don't mix well because they are binary so your repo will be huge if your document is MB.
Enforcing an "end of sentence" space
Whereas LaTeX gets away with 'cheap' copies Often beginners are not aware of the different whitespace and possible linebreaks: Cancelling an "end of sentence" space A space right after a period following a lowercase letter by default ends a sentence and LaTeX inserts an extra whitespace. Enforcing an "end of sentence" space A space right after a period following an uppercase letter by default represents an acronym and LaTeX does not insert an extra whitespace. For example, I left at Quite an improvement of the answer. Who will use I go to school now. Marienplatz Intra, not inter.
As in, I moved from Dr. I may be a little biased, but I'm quite happy with the way my thesis Circuit Quantum Electrodynamics turned out. I have now packaged up the source with a brief description of some of the tricks I used tweaking your latex is a great way to procrastinate when you should be writing a thesis!
If you find the sources useful, or further if you use my format as the basis of your own thesis, I would love to hear from you! I don't know if it qualifies for beautiful, but I'll let you decide. I used an archaich Romanian font for the headings, parcolumns for the side-by-side text, and LilyPond for the scores. Source code will eventually make its way on to GitHub as I clean it up.
The whole thing is obviously work in progress. A recent edition to the pstricks family is a set of "Vectorian ornaments" used for decorating text. It At the moment don't know whether it might be expanded it includes ornaments, listed by number:. The documentation showcases some of the styles around text. If you have time to spare, you can also have a look at my thesis Stochastic Multiplayer Games: My LaTeX class file is available at https: It offers beautiful typography down to details such that each paragraph is typeset as a perfect rectangle which means a lot of textual rewriting, so whether this is a good idea I leave open.
But it makes a wonderful coffee-table book, with a lot of very useful advice inside. Link to some sample pages as pdf. Some of this document typo are given as separated files in the typographyArchive folder. The main font is Lato it's publish under the SIL open font licence. The goal was to have a really "modern" design.
It is inspired from the flat design that is used for websites. It took me a lot of time and I hope the result was worth it. I spend some time on the table of content and the chapters headings. Besides, as I wanted something elegant, modern but still uncluttered, special efforts were made on the text look, and the document spacing. The tables are also customized to meet the flat style. Or to show that pi is rather long I'd like to add two new "styles of typography" which I created recently.
The content is not exactly impressive but perhaps the typography is. The first example document contains more of a regular "book style", with strong influence from the "tufte"-class, although I used somewhat different body text and captions. Here are the first four pages of the second chapter:. I also tried something more experimental. This more futuristic approach does not contain serifs, shows excessive use of notes in the margin, and it uses drop shadows for most figures. Also, I used a slightly less invasive colour pattern.
Whatever, I just wanted to twist some rules. Here are some example pages the real content has been substituted with sample text due to confidentiality issues:. For a project I had to typeset a text conversation between two people. I ended up writing a class that recreates the look and feel of the Kik messenger app. It's often said that the 19th century represented a nadir in typography, but I find many documents typeset in this period to be charmingly kitschy.
I've recently undertaken a project to reproduce "Persecution of New Ideas" , a notorious quacksalver 's advertisement from an old railroad atlas. Here is the LaTeX reproduction, warts and all:. Though there were some tricky bits, on the whole this wasn't terribly difficult to reproduce.
I try to pay attention to typography and in particular French typography details in the books I edit. Hopefully, the result is not too bad I don't pretend to a typographist nor a graphist:. Here are some examples taken on Android with Aldiko:. The thesis of Eivind Uggedal is very nice: Social Navigation on the Social Web: The source is at http: I cannot resist to show what all kinds of documents can be done by LaTeX, and I add this style for children books done by Paulo.
I got a directory "Beautiful TeX document" on my computer storing files that are beautiful and I might want to look at for inspiration when designing mine. All of them can be found in CTAN.
LaTeX companion 2nd edition has chapter-3 free on-line http: I think the typography is one of the finest. In addition I used the beamer class to create the slides for the final presentation. Both PDF files can be found here Bedienhaptik. The thesis was made using the koma class book and all the diagrams are made with pgfplots and tikz.
I also used the hyperref package of course. I used two colors red, blue in the document that are used for structure elements like section and headings and the colors are also used in diagrams. I used sans serif fonts for captions tables, figures and in diagrams. I think this looks nicer. The presentation was naturally done with the beamer class in combination with tikz and pgfplots. On slide 10 the presentation contains an animation pgfplots and animate package.
With the help of the community here I managed to work it out. Christoph Bier 's typokurz is beautiful and useful; it's a page guide to German micro typography in a nutshell. While it's just an article lengthwise scrartcl , to be precise , it masterfully modifies many features frequently discussed on Tex. What's even better is that the preamble is available as well, it even is extensively annotated, but — that will be the downside for most users here — in German, just like the entire document is.
Nonetheless, non-German speakers might still find their way around as well as some inspiration in the source code. OK, so here is one "from the Friends". I am a great admirer of typographic skill of Hans Hagen and Metafun manual is one of my favourites. Also available is Metafun manual source.
I dedicated quite a bit of time to the typesetting of my Master's thesis. Therefore I am more than happy to share it with you. It is open source and available at https: I wonder why nobody suggested the original works of Donald Knuth. To me they are beautiful examples of typesetting. As far as I know, his books and papers are typeset using TeX vs. LaTeX , but for the sake of the topic, I guess, it doesn't matter.
The complete list of Knuth's publications as well as preliminary drafts of the TAOCP Vol 4a chapters in post script files can be found on his home page. The sources of the TaOCP book tex files are also available in peer-to-peer networks. There have been requests on making the source code available. Since I don't want to release the full source, I've instead made a template available that you can then adapt to your own document. If you heavily base your own thesis report on this template I would appreciate if you made a small acknowledgement somewhere.
Other than that - go nuts! I really like the documentation of Philipp Lehman. The Font Installation Guide was mentioned in the question, but I also think for a simpler article rather than the book style his package documentation is hard to beat aesthetically, e. In biblatex manual [was: Can I make a document that looks like this?
I just want to come and vote this up! After reworking a few details, I ordered a printed copy recently, using zazzle: This is a great example to show how something can be re created in LaTeX.
Related Latex Is Not My Friend
Copyright 2019 - All Right Reserved