TLatex * l1 = new TLatex(0.2,0.5,"|c_{2}{8}|");
TLatex * l2 = new TLatex(0.2,0.4,"#left| c_{2}{8} #right|");
TLatex * l3 = new TLatex(0.2,0.3,"#left| c_{2}#left{8#right} #right|");
l1->Draw();
l2->Draw();
l3->Draw();
c1->SaveAs("latex.pdf");
I am testing on 5.34/18.
latex.pdf (12.5 KB)
In l1, the || are so tiny, so I have the l2.
But why it shows as|} instead of }|?
Why l3 is so ugly?
Can you, please, be more precise?
a) what’s your ROOT version?
b) what’s your platform?
It’s very possible we have a bug, but … WE ARE NOT PHYCHICS and your description is not really usefull.
Mac OSX, 5.34/18, and 5.32/00 on lxplus.
[quote=“tpochep”]Can you, please, be more precise?
a) what’s your ROOT version?
b) what’s your platform?
It’s very possible we have a bug, but … WE ARE NOT PHYCHICS and your description is not really usefull.[/quote]
Anyway, I found walk around using #scale.
[quote=“betterwang”]Mac OSX, 5.34/18, and 5.32/00 on lxplus.
[quote=“tpochep”]Can you, please, be more precise?
a) what’s your ROOT version?
b) what’s your platform?
It’s very possible we have a bug, but … WE ARE NOT PHYCHICS and your description is not really usefull.[/quote][/quote]
the fact that you found a workaround is not really helpful ( though I’m personally really happy you did). if we have a bug, we have to fix it. So, again, try to be more precise. 5.34/18 on Mac == a new graphics back-end == potentially a different behavior/output. This has to be fixed/adjusted. But your statement about 5.32 on lxplus in the same post is quite misleading/useless.
Any ideas, what did you really mean?
I use X11 for 5.34/18 on Mac OSX.
Also, lxplus is linux and the bug is still there back in 5.32/00.
It is in pdf also, so, it is not a display issue.
I assume that #left| #right| are handled as #||{something}.
When “something” contains “}”, it then breaks.
[quote=“tpochep”][quote=“betterwang”]Mac OSX, 5.34/18, and 5.32/00 on lxplus.
[quote=“tpochep”]Can you, please, be more precise?
a) what’s your ROOT version?
b) what’s your platform?
It’s very possible we have a bug, but … WE ARE NOT PHYCHICS and your description is not really usefull.[/quote][/quote]
the fact that you found a workaround is not really helpful ( though I’m personally really happy you did). if we have a bug, we have to fix it. So, again, try to be more precise. 5.34/18 on Mac == a new graphics back-end == potentially a different behavior/output. This has to be fixed/adjusted. But your statement about 5.32 on lxplus in the same post is quite misleading/useless.
Any ideas, what did you really mean?[/quote]
ookay, thanks a lot for this additional information, we’ll investigate and fix asap.