| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 9 months |
| seen | 22 hours ago | |
| stats | profile views | 82 |
|
May 22 |
accepted | Tiny gaps in large parentheses in PDF |
|
May 22 |
comment |
Tiny gaps in large parentheses in PDF Thanks for the suggestion, I edited the title accordingly. |
|
May 22 |
revised |
Tiny gaps in large parentheses in PDF edited title |
|
May 22 |
comment |
Tiny gaps in large parentheses in PDF I just filed a bug report: bugs.freedesktop.org/show_bug.cgi?id=64855 |
|
May 22 |
comment |
Tiny gaps in large parentheses in PDF @JohnWickerson, ok, this is a viewer problem. As you have been the first to comment and added external ressources, would you mind posting an answer, so that I can accept it? |
|
May 22 |
comment |
pgfplots scale legend position when below xlabel I do not really know, what you want to achieve, but I guess that the chapter "Evaluating Mathematical Expressions" in the pgf manual could be of help. You can do the conversion of units manually, too, by multiplying or dividing by 2.54 (or whatever the exact factor is). Btw. avoiding non-SI units is a good thing. matlab2tikz can be used accordingly. |
|
May 21 |
comment |
Speeding up LaTeX compilation Note, that adding more RAM will normally not increase TeX's speed. I just tested a not-too-small document with many packages and had a 49 MB RAM usage of the pdflatex process (peak value) plus 47 MB file cache usage after the compilation process (I dropped the caches before the measurements). So 100 MB of free memory when the OS and all the other applications are loaded seems to be enough for most cases. The only thing that does matter is the single-core (integer) cpu speed. |
|
May 20 |
comment |
Tiny gaps in large parentheses in PDF I just tested mupdf, and I cannot reproduce the problem in that viewer. So it might be related to the poppler library. Can anyone else see the described problem? |
|
May 20 |
comment |
Tiny gaps in large parentheses in PDF @JohnWickerson, I tested xpdf's options -aa and -aaVector (antialiasing) and both do not solve the problem (in any combination). Of course, I do not know, if this is the same option as in Adobe's Reader in the given link. |
|
May 20 |
comment |
Tiny gaps in large parentheses in PDF @JohnWickerson, Thanks for the link. Unfortunately, I cannot reproduce that, as I do not have Adobe's reader and its installation failed just yet. So there are basically two possibilities: 1.) The reader does not do exact calculations. 2.) LaTeX does not do exact calcuations. |
|
May 20 |
comment |
Tiny gaps in large parentheses in PDF @HendrikVogt Do you have any links to bug reports or any pointers to additional information? Is the hinting also applied when printing (much higher resolution)? This might be information for an answer … |
|
May 20 |
comment |
Tiny gaps in large parentheses in PDF @JohnWickerson Interesting test, but no, they do not get larger. Depending on the viewer they might even get smaller when zooming-in (also depending on the exact zoom level). Although I guess that all my viewers user poppler, so this might not be an independent test set. |
|
May 20 |
asked | Tiny gaps in large parentheses in PDF |
|
Apr 25 |
comment |
Remove macro from list like LOF Thanks a lot! Would you mind to shortly explain how \vanishprotect works? |
|
Apr 25 |
accepted | Remove macro from list like LOF |
|
Apr 25 |
asked | Remove macro from list like LOF |
|
Apr 25 |
awarded | Necromancer |
|
Feb 21 |
awarded | Nice Question |
|
Jan 22 |
comment |
Compile error with MWE using pgfkeys, beamer, xparse and \includegraphics Is there any way how to detect this different scanning mechanism or to see that a robust command is redefined? I think about interpreting \meaning\includegraphics or something like that. Reading beamer's source could also be an option, but if possible I'd like to avoid that. |
|
Jan 22 |
accepted | Compile error with MWE using pgfkeys, beamer, xparse and \includegraphics |