\documentclass{article}
\usepackage{tikz}
\DeclareRobustCommand*\drawtheme[1]{%
\begin{tikzpicture}%
\node[draw,inner sep=5pt, minimum height=1.0cm, minimum width=\textwidth,thick,rounded corners=8pt,font=\large\bfseries] {#1};%
\end{tikzpicture}}%
\begin{document}
And now we go for the next section of
\drawtheme{Theme Hospital}
\end{document}
As a follow-up to Why is \[ ... \] preferable to $$?, what really is wrong with the vertical spacing as stated in l2tabu introduced by using $$...$$ instead of \[...\]?
As there does not seem to be an elaboration of this in l2tabu except for the remark that vertical spacing is modified and rende...
I've got something like
\documentclass{article}
\begin{document}
\tableofcontents
\section*{About this Article}
\section*{About this Author}
\section{First Step}
\section{Second Step}
\end{document}
My table of contents won't show the "About this Article" and "About this Author" sections.
...
Note: something appears to be wrong with the formatting engine. Please bear with me until I get it sorted on meta.
Here's an outline answer using tabularx and tikz.
I apologise for (a) Not filling in all the text and (b) not tuning the horizontal fit and spacing.
\documentclass[10pt]{article...
@PauloCereda I took the list out, and it was still bad, but after Martin's edit it's OK (Thanks, Martin). I wonder if it was my leading tabs that did it (ie some lines started with space space space space tab)
@BrentLongborough Don't worry, your input was actually right. :) The secret was to add 8 (eight!) spaces instead of 4 for making the code part of the list, or inserting an invisible HTML comment <!-- hello! --> before your code, in order to "cancel" the list scope. :)
@Brent: I added an answer to your meta question. :)
Oops, @MartinScharrer updated his answer. :) I'll probably delete my answer. :)
Ooh I can define styles with TikZ and use them later!
In my package I intend to write in expl3 syntax, how can I get access to the list of options passed to it on the document level via \usepackage[<option list>]{my-l3-pkg}?
I know more or less how to define and set keys using the functions provided by the l3keys package. I don't know yet, wh...
@AndrewStacey true although ideally you wouldn't see too many of those as the coding file with the l3 syntax shouldn't have too many natural language strings, which would normally be accessed via a command defined elsewhere (to allow localisation apart from anything else) like \figurename in 2e/babel
@PauloCereda It doesn't matter how you input ã: in the TeX input ~a will never produce ã; but if you put ã in the .sty file it will be interpreted as usual. However, it's best not to rely on UTF-8 characters; better write \~a in a .sty file, unless it's specific for XeTeX or LuaTeX
@PauloCereda Well, ~amay produce ã in a LaTeX document, if ~ is used as a shorthand (it used to be in Spanish, but now it's deprecated). But this would hold only after \begin{document} anyway. So what's read before doesn't obey the shorthand, generally.
@PauloCereda note the ~ is not the normal plain tex latex2e active ~ for a non breaking space it s a real (catcode 10) space character, so for example it is discarded if used after a command name. Any definition of active character ~ for use in the main document is not looked at at all in this context.
@egreg Gosh! I'm temporarily ahead of David! Mind you, today's reputation is currently 2/3 for a recycled hash and 1/3 for something that actually took some work (including loading the trace package).
After I used the L3 sorcery, I used \ExplSyntaxOff to come back to my other definitions. Is this the right way? Since I have some TikZ stuff going on, it was easier for me to disable the L3 syntax, so my spaces would be preserved (otherwise I had to go with colorbox/.style={draw=black!30,top~ color=white...)
@PauloCereda That's the way to go with TikZ. Also the colon has a special meaning in TikZ. This makes it quite difficult to make it cooperate with expl3: you can't use the "programmer syntax" when working with TikZ/PGF.
@egreg Thanks! I'm really happy with this new experience. :) I'm falling in love with this L3 stuff. :) Out of curiosity, can I go with \ExplSyntaxOff when dealing with Tikz and use \ExplSyntaxOn right after for more L3 goodies? :)
@PauloCereda yes it's just like \makeatletter/makeatother and similarly should not be needed explicitly once all code is in its proper file types. (So it's needed quite often when mixing 2e and l3:-)
@PauloCereda but try to avoid mixing the stuff inside a block too much (best not at all). I know it is tempting to go \expandafter or \def or \let (and I have been guilty about that for a long time initially) but it really helps if you force yourself to use \cs_set_eq:NN etc thoughout. It is a bit more work initially but once you get used to it it helps you to better think in the expl3 methology
@FrankMittelbach I'm trying to stick only with the new approaches (xparse is fantastic). :) So far, it's been a really nice experience. :) I put all the TikZ part together, like sit in the corner. :)
@MarcoDaniel I'm rewriting/porting my songbook to a clearer code. :)
@egreg: I want to write a small xindy style to use LaTeX commands for formatting. However can you help me to collect all possible input methods of \index? I will describe it. If you write \index{foo} the following think will happen:
@MarcoDaniel There's a different problem, however: if you want to use UTF-8 characters, then \protected@write is not the way to go. You get \IeC{\"a} for ä. Probably switching to \unexpanded will be necessary.
With other problems, of course. :(
@MarcoDaniel would you please remove all the center? They only add confusion.
@egreg I believe that's a really bad design flaw of inputenc. xmltex for instance (yay @DavidCarlisle !) just transforms utf8 characters into a control sequence, keeping the code, which can then be redefined in different contexts to do different things (for instance, yield the utf8 code back). What happens if you use utf8 characters in a \label.
I understand that's a historical legacy from pre-unicode times, to allow switching input encoding, for instance to load files with different encodings without having a common global coding system to map everything to. Still, it has severe disadvantages nowadays.
@JosephWright It's not even neccesary to push UTF8 input. It would be sufficient if inputenc just transformed any encoding into UTF8 (assuming all characters can be mapped ;-) .
@PauloCereda why not? as due to all the good guys like @Joseph, @Will, @Bruno, to name a few it is gathering momentum again so a logo at some point would be nice
@StephanLehmke High bit UTF-8 characters should expand to themselves when in a \protected@write. Probably defining them with \protected would be better, but it's e-TeX, you know. And there's a strict policy on this, I believe.
@StephanLehmke Each of the bytes is active and has a definition. If this were given as \protected\def they would be written literally. And then the input would recognize them again.
@StephanLehmke the idea of inputenc and xmltex is really the same there though that any iinput is normalised to an internal form. inputenc uses (7bit ascii safe) command sequence xmltex uses (essentially) utf8. At the time that inputenc was written unicode didn't have enough math characters defined to support even a basic set of tex math commands, so normalising to utf8 wasn't really an option 9and it's not particularly convenient normal form for classic tex anyway)
@DavidCarlisle In that case it should be possible to add something to \protected@... so that UTF8 characters transform back to UTF8, as it works with xmltex.
@StephanLehmke yes but no. inputenc design is that you can have a chapter written in utf8 that writes a toc entry that gets read back in the frontmatter where the current encoding is latin-2 or something. So writing the characters as utf8 would be wrong, which is why it goes to some lengths not to do it:-)
An alternative design would be to read all auxiliary files back as utf8 whatever the document encoding, but any such design change would have to be for a future version of latex...
@egreg we could have a strict version where only 7bit ascii were allowed and you had to write in English. That way 90% of the complication would go... We could call it TeX2
@DavidCarlisle Well what about some Unicode based command syntax which always denotes a unicode character no matter what the current input encoding is. For instance, in XML &#xyz; notation always encodes unicode points no matter what the declared encoding of the XML file is.
@DavidCarlisle And it really doesn't matter whether the operating system understands UTF-8, as TeX works strictly on 8 bit input and output. But there's the ^^ convention, you see. :(
@StephanLehmke Browsers are 16bit engines and last time I checked utf8 was still only just creeping towards being the most common encoding. The thing is end users produce what they produce and typically it's quite hard to see what encoding a file is in if the software being used detects the encoding and does the right thing regardless.
@DavidCarlisle I used this for recognizing if the engine is Unicode or not: define something to expand to ^^^^0000, which is ignored in Unicode engines, and compare it to \empty. Then I discovered that Heiko Oberdiek had already used the trick. :)
@StephanLehmke you could make ^^^^ work on classic tex most likely with some protected active definition that acted as a superscript in math or detected runs of ^^^^ otherwise
@DavidCarlisle Maybe I was expressing myself unclearly. With the "Unicode based command syntax" I meant what \protected@write should write to files so it could be read as Unicode regardless what input encoding is active at the time of reading.
@DavidCarlisle Cool idea. Maybe a base for a modern reimplementation of inputenc ;-)
@StephanLehmke as I say it would be easy to do, but as a matter of an interest what are you doing with the data read back, presumably not typesetting it otherwise the command forms would be fine.
@egreg I’m testing the – very useful – regexpatch package. I’ve just noticed that \xpatchcmd expands the success argument if patching fails and both the success and the failure argument if the command to be patched is undefined.
I run the following simple example using MikTeX 2.9 (complete installation) that is regularly updated (this is one of the first examples in TikZ manual):
\documentclass{article}
\usepackage{tikz}
\usetikzlibrary{arrows,calc,intersections}
\begin{document}
\begin{tikzpicture}
\path [name path=on...
@Werner I did not see a dispute. I noticed the flag, read the non-answer, converted it to a comment, that's all. I think the OP is still able to see Andrew's comment in his inbox, so I did not move Andrew's comment as it's only for the OP.
Interesting! If I add this line: \index[ica]{\songindextitle@\songliturgy \songtitle} inside a command definition in my .sty file, I get an Undefined control sequence.. The line works outside. Any hints? :)
@PauloCereda The space in \songindextitle @ is ignored anyway. But without it you're specifying the \songindextitle@ control sequence (that's undefined). It doesn't happen in normal text because there @ is not a letter, so it stops the parsing of the control sequence name.
@PauloCereda Well, but there really are no more keywords in my example, and if that's the case, I didn't find a mention about it in the documentation. As far as I understand, otherkeywords handles characters considered to be of type "other" according to the listings classification.
This year, both gardens were merged, so the street in front of the church doesn't exist anymore. :)
@egreg We have two nearby. :) The one from the decoration is the "Morro do Cuscuzeiro". We also have another one called "Morro do Camelo". Cuscuzeiro is named after the "cuscuz" plate (they usually have that shape!). :) The other one is called Camelo (camel) because it reminds of a camel. :)
For the following piece of LaTeX code,
{\hat \theta}
= { \argmin_{\theta \in \Theta}}
I got following error:
undefined control sequence={\argmin
How would I correct it?
Hey, just dropping a note that Stack Overflow's migration path list now includes TeX.SE; that means that those of you who patrol SO looking for questions that need to be migrated can now either vote yourself or use a standard off-topic flag which 10k users there can review.
It's the same amount of work for you and less for us poor overworked SO mods. :)
I wonder how long I can answer tikz questions just by running the MWE with \tracingall and inserting an expandafter or two and not actually knowing what any of the code does:-)
I've got something like
\documentclass{article}
\begin{document}
\tableofcontents
\section*{About this Article}
\section*{About this Author}
\section{First Step}
\section{Second Step}
\end{document}
My table of contents won't show the "About this Article" and "About this Author" sections.
...
Note: something appears to be wrong with the formatting engine. Please bear with me until I get it sorted on meta.
Here's an outline answer using tabularx and tikz.
I apologise for (a) Not filling in all the text and (b) not tuning the horizontal fit and spacing.
\documentclass[10pt]{article...
In my package I intend to write in expl3 syntax, how can I get access to the list of options passed to it on the document level via \usepackage[<option list>]{my-l3-pkg}?
I know more or less how to define and set keys using the functions provided by the l3keys package. I don't know yet, wh...
I run the following simple example using MikTeX 2.9 (complete installation) that is regularly updated (this is one of the first examples in TikZ manual):
\documentclass{article}
\usepackage{tikz}
\usetikzlibrary{arrows,calc,intersections}
\begin{document}
\begin{tikzpicture}
\path [name path=on...
For the following piece of LaTeX code,
{\hat \theta}
= { \argmin_{\theta \in \Theta}}
I got following error:
undefined control sequence={\argmin
How would I correct it?
