19,396 reputation
143100
bio website
location
age
visits member for 3 years, 11 months
seen 9 hours ago

Jan
20
comment TeXShop doesn't remember file encoding
@cfr: For kate I have provided some more details in tex.stackexchange.com/questions/89859/… If you google for the example, you will easily find more.
Jan
19
awarded  Announcer
Jan
18
answered Beamer overlays with tikz nodes break verbatim whitespace handling
Jan
13
comment How can you create a vertical timeline?
+1 for handcrafted solution :-)
Dec
23
awarded  Nice Question
Dec
22
comment TikZ/TeX: Minimum line width/maximum resolution
@egreg: With pdftex the resulting PDF contains a visible line that, according to Adobe Illustrator, is 0 pt thick :-)
Dec
22
revised TikZ/TeX: Minimum line width/maximum resolution
incorporated pauls answer
Dec
21
comment TikZ/TeX: Minimum line width/maximum resolution
Alright, I found the culprit: I did all my tests with LaTeXit, which is kind of nice for small tests. However, if one saves the PDF, LaTeXit apparently pipes it through the MacOS Quartz engine, which caused the effect. If I compile with pdflatex directly, it works: 0.1004pt (or simpler: 0.01bp) gives the right thickness.
Dec
21
comment TikZ/TeX: Minimum line width/maximum resolution
Hm... that yields 0.18 pt in Adobe Illustrator (which makes sense, if the previous result was 0.179). Something strange is going on...
Dec
21
comment TikZ/TeX: Minimum line width/maximum resolution
Aaarg! I know that TeX points are not points. How could I forget that...
Dec
21
comment TikZ/TeX: Minimum line width/maximum resolution
This yields lines with 0.0179, 0.0161, ..., 0.0107, ..., 0,0018 pt. The 0.0107 comes pretty close, have to try if that works.
Dec
21
comment TikZ/TeX: Minimum line width/maximum resolution
@Kpym: I have tried it, result the same: 0.0179 pt
Dec
21
asked TikZ/TeX: Minimum line width/maximum resolution
Dec
20
comment Why do people still use Postscript?
@AlexG: Good comparison! However, as a matter of fact fewer and fewer tools are able to generate PS out of the box, so what publishers actually get is PS that has been converted from PDF. To stay into you picture this would be C code generated by a disassembler/decompiler out of the binary. I doubt that this is more editable than the PDF directly.
Dec
19
comment Calling macro fails with error \inaccessible
@jlinkels: I strongly feel with you! Well, you should admit yourself that the error message was not exactly helpful to find the culprit.
Dec
19
comment LaTeX vs Word; improvements of LaTeX over the years
@barbarabeeton: Thanks for mentioning snapshot! For some years I have been maintaining a project-specific texmf tree for every project that uses "critical" packages (especially biblatex...). However, "criticality" was purely subjective here – I added a package if something did not work with some colleagues TeX installation. snapshot seems to be the missing link to systematically maintain version dependencies!
Dec
19
comment LaTeX vs Word; improvements of LaTeX over the years
@CarlWitthoft: Just for curiosity I did: No problems at all to open it in a current version of Word.
Dec
18
comment LaTeX vs Word; improvements of LaTeX over the years
Hm... might work today with a plain document from 2000, but I am not so sure about it in 2030 with a LaTeX document from today. I have experienced too many problems reusing documents less than three years old if they employed modern packages or classes, such as biblatex, libertine, tikz, moderncv. Unfortunately, issues with back-compatibility are no longer a privilege of Word and Co.
Dec
16
revised merge many pdfs
typos
Dec
16
answered merge many pdfs