|
From: sfeam <sf...@us...> - 2013-10-10 15:36:26
|
On Thursday, October 10, 2013 02:19:12 PM Mojca Miklavec wrote:
> On Wed, Oct 9, 2013 at 7:36 PM, Ethan A Merritt wrote:
> > On Wednesday, 09 October, 2013 15:26:29 Mojca Miklavec wrote:
> > "set format '%H'" is sufficient. You don't need to set it separately for
> > x and y.
> It's not just about simplicity, but also about configurability. Let's
> say that a user would want
> 3×10<sup>6</sup>
> rather than
> 3x10<sup>6</sup>
> even if UTF-8 isn't recognized.
Huh? How can you select a UTF-8 character if UTF-8 isn't recognized?
> > A related question:
> >
> > At the moment the new code checks for TERM_IS_LATEX and if so
> > replaces the default format "%h" with "$%h$". I.e. it uses the same
> > format but wraps it in $...$ so that LaTeX uses numerical mode.
> > Would it be a good idea to _always_ do this? Or maybe always do
> > it if the format does not already contain $ signs?
>
> What exactly do you mean with "always"? If I use "set title 'some
> text'" I don't want it to be enclosed in dollar signs for example.
Only for "set format"
> Which cases exactly fall under "alway wrap it in $...$"?
>
> In my old scripts I was often using something like (please excuse me
> if I used the wrong format specifiers here):
> set format y "\\m{%t}{%T}"
> where the master document defined
> \def\m#1#2{$#1\cdot10^{#2}$}
That example is way over my head.
I don't recognize the syntax at all.
> I guess this would fail then?
Yes it would. So maybe it it wasn't a good idea.
I can revert it to only wrap the default format, not user-defined formats.
Ethan
|