Tag Info

22

You need to use baseline on the tikzpicture, not on the nodes. As Tom Bombadil mentioned in the comments you can use current bounding box.center to put the center of the TikZ picture on the baseline. I would also add an yshift to center it around the middle of the = sign. -.5ex seems to do it. \documentclass{article} \usepackage{tikz} \begin{document} ...

20

As mentioned in the comments, \tikz[baseline=(X.base)]{% works for this \documentclass{article} \usepackage{pgf,tikz} \makeatletter \begin{document} \gdef\drawfontframe#1{% \tikz[baseline=(X.base)]{% \node[rectangle,draw,inner sep=0pt,outer sep=0pt] (X){#1}; \draw[red, line width=0.4pt] (X.text) circle(0.4pt)[fill=red] -- (X.base east);}% ...

15


4

This uses a pdftex \pdfliteral but you could use a special for xetex Here I've used two minipages side by side so that you can tell by the end that the baselines have returned to normal. On the left the region between the !! is raised by 2bp \documentclass{article} \begin{document} \centering \begin{minipage}[t]{.43\linewidth} One two three four one two ...

4

One way is to use the baseline key in the tikzpicture options to specify that each picture should be aligned to the baseline by a particular node name (here I used (A)): \documentclass{article} \usepackage{tikz} \usetikzlibrary{automata} \usetikzlibrary{positioning} \begin{document} \tikzstyle{negative} = [circle, minimum width=8pt, fill, inner sep=0pt] ...

3

this is the expected behavior. you have wrapped the text in a group without ending the paragraph, so the baselines applied are those for the surrounding environment. one double blackslash has no effect on this setting, but when the text is broken this way multiple times, all but the last force resolution of the baseline of the previous segment. in this ...

3

Is this what you want? \begin{tikzpicture} [mainbullet/.style={rectangle, minimum size=0.3cm, draw=orange!100, fill=orange!100, thick}, maintitle/.style={rectangle, opacity=0.5}] \node[mainbullet] (experiencebullet) at (0, -23) {}; \node[maintitle] (experiencetitle) [right=10mm of experiencebullet.south east, anchor=base west] {Experience}; ...

3

Without changing anything in your tree-syntax, the tikz-qtree package allows you to get the right result: \documentclass{scrreprt} \usepackage{tikz-qtree} \begin{document} \Tree[.table [.thead [.tr [.th [.\textit{Vorname} ] ] [.th [.\textit{Nachname} ] ] ] ] ...

3

Too long for a comment. The base line of the last text line on the second page is correctly aligned with the bottom of the text area. According to \maxdepth, TeX allows the descenders to stick outside the text area to get a proper alignment of the base lines of the last text lines on the pages. The last text line of the first page does not reach the ...

3

The height of the \tikz in the definition of \circled is responsible for the added line spacing. One can treat the height of an object as zero with the \smash{} macro. So here, I \smash{\tikz[...]{...}}. Of course, this now makes overlap a possibility. In an effort to combat this, I reduced the minimum size of the circle to 1.4em. % !TEX encoding = ...

3

In this case, you will have to tell TikZ where you want your baseline to be. Here you want it to be for example on your (a) node. Here is a code to provide it : \documentclass{report} \usepackage[english]{babel} \usepackage{tikz} \tikzset{x=1pt, y=1pt, z=1pt} \begin{document} \newcommand{\mypicture}{\begin{tikzpicture}[baseline=(a.base)] ...

3

Your problem is that by using \begin{tikzpicture} \begin{tikzfadingfrompicture} \end{tikzfadingfrompicture} \end{tikzpicture} you do nothing else than nesting two tikzpicture environments, which is known to be a source of trouble. However, it is not necessary to do this, since you name the tikzfadingfrompicture to reuse it. When putting both ...

3

The example is not minimal. I've minimised it a bit further just by removing all the hyperref stuff. (I checked that this all has no relevance.) The basic problem involves the use of nested tikzpictures which are known to cause problems. Although not guaranteed to fail, failure is to be expected. Nesting should therefore (very nearly almost) always be ...

Only top voted, non community-wiki answers of a minimum length are eligible