937 reputation
1519
bio website
location
age
visits member for 3 years, 10 months
seen 2 days ago

I'm not incredibly TeX savvy, but I know the basics plus a trick or two. For this reason, there aren't too many questions can provide an answer to, but I'll answer what I can when I see it. I'm also contributing to the (La)TeX community by helping friends and students with their problems, and showing beginners how to get started.



Welcome to TeX.SX!

Have a look at our [starter page](http://meta.tex.stackexchange.com/questions/1436/welcome-to-tex-sx) for a quick intro if you wish to familiarize yourself with our format. 

Please help us help you by including a [minimal working example (MWE)](http://meta.tex.stackexchange.com/questions/228/ive-just-been-asked-to-write-a-minimal-example-what-is-that) in your question. An MWE begins with `\documentclass{...}` and the required `\usepackage{...}` lines, and ends with `\end{document}`. If your code sample can be compiled without any changes, it is much easier for us to provide help.

A tip: If you indent lines by 4 spaces, they'll be [marked as a code sample](http://meta.tex.stackexchange.com/questions/1192/how-do-i-mark-code-blocks). You can also highlight the code and click the button marked with a `{}` symbol.

Nov
7
comment Tikz pattern areas become black when printing
I believe this problem is largely dependent on your setup. Have you tried printing the document on different printers? Is the result the same? When I print that pattern, the pattern is very dense, but not completely filled. One workaround could be to define your own pattern with more space between the pattern lines.
Oct
10
awarded  Popular Question
Oct
1
comment usepackage{pdfpages} error
The error says you're missing the \begin{document} line. Could you post a minimal working example (MWE) so we can have a look? Or, if you're wondering about the error, could you post a minimal document which reproduces that error?
Sep
30
awarded  Explainer
Sep
30
awarded  Popular Question
Sep
24
awarded  Autobiographer
Sep
20
accepted Clipping plots to other plots in pgfplots
Sep
20
comment Clipping plots to other plots in pgfplots
I don't know what the issue was, and I have trouble accepting that this was within my control. When I found that the \path command didn't work for the scaling coefficient I wanted, I plotted the frame with the \addplot command instead. I copied the expressions from the \path command and only changed \x to x. I'm looking at that file now, and the expressions are exactly the same as in your updated example. Nevertheless, your updated example plots everything very nicely. I guess I'll never know what caused this second issue. Thanks for looking into my problem and for a neat solution.
Sep
20
comment Clipping plots to other plots in pgfplots
When the last terms in the fractions are squared, a different scaling coefficient is needed to get the same visual impression. I first squared all the appropriate terms without changing the scaling coefficient, and everything was plotted as expected. However, when I changed the scaling coefficients, the paths were no longer drawn. I plotted the functions elsewhere to double-check that there was, indeed, nothing weird about them. When I changed the scaling coefficient back, the paths were plotted again. The \addplot command didn't have this problem.
Sep
19
comment Clipping plots to other plots in pgfplots
Sorry for being so absent-minded, but I forgot to actually square the last term in the functions in my example. The correct functions don't seem to work with your solution, presumably because tikz can't handle the mathematical computations. Please excuse my silliness. Your solution is otherwise a great one. I have corrected the question.
Sep
19
revised Clipping plots to other plots in pgfplots
added 358 characters in body
Sep
19
asked Clipping plots to other plots in pgfplots
Sep
18
comment Defining consistent rules for the use of small caps
And please don't get me wrong: I don't mean to argue for the sake of arguing. Before I asked this question I wasn't sure whether it would be considered off topic. However, when I found that related question and also discovered that there was a dedicated typography tag, I was convinced that this question was, in fact, on topic. The tag descriptions even read: "Typography is the art and technique of arranging type, type design, and modifying type glyphs." and: "Questions tagged typography deal with [...] questions about what constitutes good typography in the first place."
Sep
18
comment Defining consistent rules for the use of small caps
@T.Verron: I find that quite contradictory. If anything which isn't TeX is off topic, then typography per se is indeed off topic. And no matter how you look at it, if every question should have something to do with some TeX feature, the typography tag is vague and misleading. Instead of having the typography tag, those questions, which apparently are not about typography per se, should rather have a more specific tag about the feature they're actually asking about.
Sep
18
comment Defining consistent rules for the use of small caps
@T.Verron: If there is a dedicated typography tag on TeX.SX and questions like the one I linked are not specifically marked as off topic, there really isn't much to suggest that questions like my own are off topic. Besides, typography and TeX are very closely related, and my personal opinion is that one should be careful writing off all typography questions as off topic.
Sep
18
comment Defining consistent rules for the use of small caps
@T.Verron: It's mostly a general typography question, but the same is the case for one of the related questions. There's also a typography tag here on TeX.SX. I could, perhaps, ask both places.
Sep
18
revised Defining consistent rules for the use of small caps
Updated example to include oldstylenums
Sep
18
asked Defining consistent rules for the use of small caps
Sep
17
accepted Persistent draw color when using \def
Sep
17
comment Persistent draw color when using \def
Thanks for this great answer. Although you seem to have found the source of the problem, I'd say the code looks a little neater with the workaround. I assume this bug will be fixed in a future version.