Klaus

I can reproduce the same behavior as described in the original post with version 5.2.8 on Windows 10. Here ist the output of the script above for font scaling 100 % and 125 %, respectively. Edit: I also attached scaling 150 % and 175 %, because of the comment from Tatsuro MATSUOKA on 2015-05-26. But the phenomenon also occurs in these cases.

I can reproduce the same behavior as described in the original post with version 5.2.8 on Windows 10 . Here ist the output of the script above for font scaling 100 % and 125 %, respectively.

Thanks for the explanation, the work-around with the linebreak is very helpful.

x2label y-offset

"Would anyone ever want to set the t axis to log scale?" Is your application a case where the answer is "yes"? I would agree: The proposed case is an application where a logscale of the t axis makes sense. Without this option, one has to define an additional log-scaling function as a workaround. Meanwhile, the logscale of the t axis is not necessarily related to the logscale of another axis (like x1). Therefore, I would plead for - set log t as an allowed command - not correlate the log t with logscale...

Dear Ethan, thank you for the proposed workaround, it worked well. However, the behavior of parametric mode and trange is somewhat unexpected, and seems not be be consistent within the versions 5.0 and 5.2. As you pointed out that for this specific task, parametric mode is not the only way to do that: I reduced my plotting script to what I thought was a minimal example (although Karl Ratzsch improved that, thanks!), so it was not clear what I was trying to do. In order to clarify the background of...

parametric, trange, logscale causes problems

parametric, trange, logscale causes problems