LaTeX.org

I'm not very familiar with font, so parsing the catalogue is no substitute for trying, which would be tedious for every font. The first example would be fine if `foo`'s was more "awesome". In the second example, the hashtag is too meek. Any suggestion?

\documentclass{minimal}
\usepackage ...

Are there examples that show how to cite regulations, pieces of legislation, parliamentary debates in LaTeX? What entry types should I use (article, collection etc.)?

I was hoping biblatex offered a command similar to \textquote of csquote . Anyone?
@MANUAL{theman,
author = {John Smith},
title = {Manual},
shorttitle = {Man},
series = {S},
year = {2000},
organization = {Org}
}

\documentclass{article}
\usepackage[english]{babel}
\usepackage{csquotes ...

This leaves a big gap before printing from/to. And how can I ensure it matches a 240mm×150mm envelope?

\documentclass[12pt,envelope]{article}
\usepackage[english]{babel}
\usepackage{envbig}

\from{John\\ address\\ city/state}
\to{Peter\\ address\\ city/state}

\begin{document}
\envelope
\end ...

I wonder what is the purpose of \makelabels . Below, it adds a page after the letter with RECIPIENT in the top left corner. I was hoping I there would something like \DeclareOption{enveloppe-format} and that SENDER and RECIPIENT print where they're supposed to in that envelope format. That's 240mm ...

I feel "Sincerly, Signature" is positioned more to the right than I'm accustomed to see. Is this the standard English letter format?
\documentclass{letter}
\usepackage[english]{babel}
\usepackage{marvosym} %\Mobilefone %\fax %\email
\usepackage{wasysym} %\phone
%\DeclareOption{a4paper ...

I still don't understand. Why do you want that \baz contains unexpanded contents that is not defined?

I don't see how saying that \foo is part of the overhead of \baz conveys that. In any case, I didn't mean it, and I have acknowledged this constraint:

You either have to expand \foo in the ...

The solution with \@temp seems to work, but I have to wrap my mind around it. The one with \global\let has not worked. The one with multiple expandafter seems to emulate \xdef , doesn't it?

Meanwhile let me rephrase my goal.

Let's say that \gdef\baz (not \xdef\baz ) is the public interface of a ...

The behavior of the code below for each variant of baz is as I'd expect. The one that is `not OK', however, expresses what I'm aiming for: \foo is accesible within the definition of \baz after \endgroup , but is otherwise `hidden' (in particular, it does not clash with \def\foo{Oops} defined after ...

Some blogs have limited support for LaTeX, but I still would rather use that than transform LaTeX output to html. Let's say this is my input:


\newcommand\sub{\LaTeX}
\newcommand\vrb{is}
\newcommand\compl{a programming language}
\sub\ \vrb\ \compl.


and it can't be parsed by my blog. But this ...