77,000 reputation
14193415
bio website loopspace.mathforge.org
location Trondheim, Norway
age 38
visits member for 4 years
seen yesterday

Jun
10
awarded  Nice Answer
Jun
7
awarded  Nice Answer
Jun
4
comment How to get and process bitmap graphics at a pixel level on-the-fly?
Take a look at the pullquote package, see tex.stackexchange.com/a/70169/86, as I think that does something like that.
Jun
4
comment How to get intersection point(s) of two glyphs?
I use the CVS version of TikZ and I know that the name path global has had issues in the past, so it may well come down to that.
Jun
4
comment How to get intersection point(s) of two glyphs?
Regarding conversion of fonts, there's the script x2svg.pe which uses FontForge to convert an arbitrary font to SVG type. Then the program svgtopgf.pl converts the resulting SVG to PGF paths. That program was written specifically for font files so I wouldn't expect it to work on an arbitrary SVG.
Jun
4
comment How to get intersection point(s) of two glyphs?
What version of TikZ/PGF are you using? I get a different list of numbers of intersection points. I haven't checked them all, but the ones I have checked look right. My list is 4, 6, 14, 14, 10, 8, 8, 6, 4, 4, 6, 10, 8, 14, 10, 12, 10, 4.
Jun
4
comment Rescale a character to fill a complete A4 page
@strpeter I think it could handle a multi-page document with one letter per page. I haven't experimented, though. The point is to allow the PDF viewer to do the scaling, not TeX.
Jun
4
comment How to get intersection point(s) of two glyphs?
Oh, and if you have any specific questions about the bits and pieces of my code that you've used, just ask.
Jun
4
comment How to get intersection point(s) of two glyphs?
Yay! That looks awesome. I think that there are some bugs with name path global, but I'm not sure if they've been fixed or not (see the PGF bug list).
Jun
4
comment Rescale a character to fill a complete A4 page
My strategy for this is to print it out normal size on an empty page using standalone to crop the PDF to the size of the letter(s). Then in my PDF viewer I print it out scaling it up to fit.
May
29
comment Parameterized anchors in pgf/tikz
I did this with the original version of the TQFT package (that used nodes, the latest version uses pics). I based it on the code for the polygon shape that comes with TikZ.
May
28
comment Trouble defining new environment with embedded gather
@Werner That looks like the one I was thinking of.
May
28
comment TikZ: extend a line along a path
Or maybe not. To be on the line from the focal point, we're treating the lens as a single object rather than as a composite of two edges and only interested in the path of the ray as it comes out of the lens. So I agree with your picture.
May
28
comment TikZ: extend a line along a path
I think that the bend should be at the point where the incoming ray hits the edge of the lens, not at the (vertical) centre of the lens.
May
28
comment Trouble defining new environment with embedded gather
You're using amsmath, the other answer used mathtools. There was a question here about using align within a custom environment with amsmath, but I can't find it right now. I think that the solution was to use the environ package.
May
28
comment TikZ: extend a line along a path
Plus the calc library to draw the extension since you can draw from the intersection in the direction of F for -1cm, or however long you want.
May
28
comment TikZ: extend a line along a path
If you want a single path then the intersections library is the way to go.
May
28
comment TikZ: extend a line along a path
Would you accept a clip to the lens path? If not, the best I can think of would be to use intersections to compute the starting points of the rays.
May
28
comment How can I break a macro / how to realize a switch or array-structure
@DavidCarlisle I applaud your sense of morality.
May
28
comment How can I break a macro / how to realize a switch or array-structure
@DavidCarlisle You misunderstand where I want to put the \long. Since you define \foo using \newcommand* then I think you should also define \setfoo using \newcommand* as the arguments are used in the same way. Whether or not you want to allow \foo and \setfoo to eat a \par is, as both you and egreg point out, simply a matter of choosing your error message. But whatever you choose, you should be consistent about your choice.