On 11/16/2017 06:11 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
> What do we need to do to get a raised footnote symbol in the main text
> (line 6 of the pdf)? Thanks in advance.
BTW, I mixed the number which had to be raised.
By default, the textcommand option has a value of
On 11/16/2017 06:11 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
> Der gang,
>
> For the following \definefont scenario, the footnote symbol in the main
> text is not raised:
>
> ===
> \setuppapersize[letter][letter]
Dear Idris,
which is the difference betwe
Der gang,
For the following \definefont scenario, the footnote symbol in the main
text is not raised:
===
\setuppapersize[letter][letter]
% \setupbodyfont[schola,12pt]
\definefont[PagellaRegular] [texgyrepagella-regular.otf at 14pt]
\definefont[PagellaRegularSmall][texgyrepagella
s)
mkiv lua stats > loaded patterns: en::2, load time: 0.000
mkiv lua stats > result saved in file: ntg70.pdf, compresslevel 3, objectcompresslevel 3
mkiv lua stats > loaded fonts: 4 files: latinmodern-math.otf, lmmono12-regular.otf, lmroman12-bold.otf, lmroman12-regular.otf
mkiv lua sta
/mtx-update.lua:127: unexpected symbol near '.'
When you want to use context, you need to initialize the tree by typing:
. /opt/ConTeXt/tex/setuptex
in your shell or add
"/opt/ConTeXt/tex/texmf-linux-64/bin"
to PATH variable if you want to set it permanently.
This can usual
017.09.25 19:19 MKIV beta fmt: 2017.9.27"
>
> Do you have a diff file ?
Diff attached. It also includes a translations from Dutch into English.
Pablo
--
http://www.ousia.tk
--- grph-inc.mkiv 2017-09-27 18:48:45.157818507 +0200
+++ mkiv/grph-inc.mkiv 2017-09-25 19:23:53.0 +0
> flushing realpage 2, userpage 2
> pages > flushing realpage 3, userpage 3
> close source> level 2, order 4, name '/Users/vm/Desktop/error.tex'
> close source> level 1, order 4, name '/Applications/ConTeXt/tex/
> texmf-context/tex/context/base/mkiv/
loaded tex modules: 1 requested, all found (*-simplefonts)
mkiv lua stats > loaded patterns: en::2, load time: 0.000
mkiv lua stats > result saved in file: error.pdf, compresslevel 3,
objectcompresslevel 3
mkiv lua stats > loaded fonts: 1 files: latinmodern-math.otf
mkiv lua stats > font
#1}}
>> \startsymbolset [Dangerous Bends]
>> \definesymbol [dbend] [\GetSym{127}]
>> \definesymbol [lhdbend] [\GetSym{126}]
>> \stopsymbolset
>> \setupsymbolset [Dangerous Bends]
>> \setupbodyfont[manfnt]
>> \starttext
>>
Bends]
\setupbodyfont[manfnt]
\starttext
\symbol{dbend}
\blank[big]
\symbol{lhdbend}
\stoptext
%%% end dangerous-bend.tex
Thanks in advance: OK
\definefontsynonym [bends] [file:manfnt.afm]
\startsymbolset [Dangerous Bends]
\definesymbol [dbend] [\resolvedglyphdirect{bends}{n:char_7e
\symbol{dbend}
\blank[big]
\symbol{lhdbend}
\stoptext
%%% end dangerous-bend.tex
Thanks in advance: OK
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context
Hi Hans,
Regarding what you have added on line 1327 of math-stc.mkvi, that line should be
\definemathover[\v!symbol][interiorset]["2218]
(instead of "2217).
I added also a wiki page for mathstackers:
http://wiki.contextgarden.net/mathstackers
Best regards: OK
&
to ask how is it possible to get the
>> command act entirely in math mode, that is respecting the distances and the
>> math fonts. Please see the attached output.
>> %%% begin interior-of-a-set.tex
>> \definemathstackers[symbol][voffset=-.30\mathexheight,hoffset=\zeropoint]
>> \d
. Please see the attached output.
%%% begin interior-of-a-set.tex
\definemathstackers[symbol][voffset=-.30\mathexheight,hoffset=\zeropoint]
\definemathover[symbol][interiorset]["2218]
\starttext
Here is the new command \type{\interiorset{K}}: $\mathring{K} \neq
\interiorset{K}$
\stoptext
%%
interior-of-a-set.tex
\definemathstackers[symbol][voffset=-.30\mathexheight,hoffset=\zeropoint]
\definemathover[symbol][interiorset]["2218]
\starttext
Here is the new command \type{\interiorset{K}}: $\mathring{K} \neq
\interiorset{K}$
\stoptext
%%% end interior-of-a-set.tex
Best regard
\definemathstackers[symbol][voffset=-.30\mathexheight,hoffset=\zeropoint,color=red]
\definemathover[symbol][interiorset]["2217]
\startformula
\mathover [symbol]{"2217} {A}
\mathover [symbol]{"2218} {A}
\mathover [symbol]{"2219} {A}
\mathunder [
auto-resolving ~= to the proper symbol (as we do with := and such)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477
Am 2017-07-24 um 15:24 schrieb Hans Hagen <pra...@wxs.nl>:
> On 7/24/2017 1:54 PM, Rik wrote:
>> On 2017-07-24 05:51, Hans Hagen wrote:
>>> On 7/24/2017 3:51 AM, Rik Kabel wrote:
>>>> Aditya came across this in 2011 ([NTG-context] export kills hyphen symbol
&g
On 7/24/2017 1:54 PM, Rik wrote:
On 2017-07-24 05:51, Hans Hagen wrote:
On 7/24/2017 3:51 AM, Rik Kabel wrote:
Aditya came across this in 2011 ([NTG-context] export kills hyphen
symbol
<https://www.mail-archive.com/ntg-context@ntg.nl/msg58460.html>)[1]
with the Fontin font. It
On 2017-07-24 05:51, Hans Hagen wrote:
On 7/24/2017 3:51 AM, Rik Kabel wrote:
Aditya came across this in 2011 ([NTG-context] export kills hyphen
symbol
<https://www.mail-archive.com/ntg-context@ntg.nl/msg58460.html>)[1]
with the Fontin font. It wasn’t answered then. It is back if i
On 7/24/2017 3:51 AM, Rik Kabel wrote:
Aditya came across this in 2011 ([NTG-context] export kills hyphen
symbol
<https://www.mail-archive.com/ntg-context@ntg.nl/msg58460.html>)[1] with
the Fontin font. It wasn’t answered then. It is back if it ever left.
Here is an e
Aditya came across this in 2011 ([NTG-context] export kills hyphen
symbol
<https://www.mail-archive.com/ntg-context@ntg.nl/msg58460.html>)[1] with
the Fontin font. It wasn’t answered then. It is back if it ever left.
Here is an example:
\definefontfamily
[TestFont]
\usemodule[vim]
\definevimtyping[python][syntax=python, escape=on,
highlightcommand=\texthighlight]
\starttext
\startpython[highlight=3]
for x in 1:n
print(x)
# Returns \m{\sum_{i=1}^{n}i \in F \int_i f}
for x in 1:n
print(x)
\stoppython
\stoptext
Thank you, this works much b
ound mechanism:
>
> \definetextbackground[texthighlight]
> [
>background=color,
>backgroundcolor=gray,
>frame=off,
> ]
>
> \define[1]\texthighlight{\starttexthighlight#1\stoptexthighlight}
>
> \usemodule[vim]
> \definevim
ext-mirror/blob/beta/tex/context/base/mkiv/math-stc.mkvi
https://github.com/contextgarden/context-mirror/blob/beta/tex/context/base/mkiv/math-fen.mkiv
Otherwise I just look up the symbol in this file
http://texdoc.net/texmf-dist/doc/latex/unicode-math/unim
ll?) delimiters are defined in these files.
https://github.com/contextgarden/context-mirror/blob/beta/tex/context/base/mkiv/math-stc.mkvi
https://github.com/contextgarden/context-mirror/blob/beta/tex/context/base/mkiv/math-fen.mkiv
Otherwise I just look up the symbol in this file
http://texdoc.net
fine with latest beta.
>>>
>>> I found a strange bug with the \tt command: when copying from the
>>> PDF, the spaces disappear. With your header above, I get (the
>>> comments is the text copy from the PDF):
>>> [...]
>>> That is, when adding a single
>> PDF, the spaces disappear. With your header above, I get (the
>> comments is the text copy from the PDF):
>> [...]
>> That is, when adding a single symbol, above "α", but it does not
>> seem to matter which, the spaces disappear.
>
> I get right s
>> PDF, the spaces disappear. With your header above, I get (the
>> comments is the text copy from the PDF):
>> [...]
>> That is, when adding a single symbol, above "α", but it does not
>> seem to matter which, the spaces disappear.
>
> I get right
copy from the PDF):
> [...]
> That is, when adding a single symbol, above "α", but it does not
> seem to matter which, the spaces disappear.
I get right spaces with latest beta from:
\definefallbackfamily[mainface][tt][TeX Gyre Cursor]
[range={basiclatin, digitslatin}, force
changed in a non-trivial manner since TL2017. You
> have to go with beta.
Yes, it works in latest beta. There is a TeX Live updating utility, at least on
the MacOS distribution, that allows for server synchronizations between the
yearly updates.
I found a strange bug with the \tt command, wher
t beta
> from the ConTeXt Suite.
Yes, that is the problem. It works fine with latest beta.
I found a strange bug with the \tt command: when copying from the PDF, the
spaces disappear. With your header above, I get (the comments is the text copy
from the PDF):
{\tt axiom A1. 푨 ⇒ 푩.}
%
become proper unicode symbols too
>>
>> - fonts have one, two or three sizes, often inconsistent and with funny
>> dimensions, onlyt the text size can be trusted
>>
>> - we cannot use prime as nuclues as it can be combined with a subscript
>>
>> - but
y one prime but also with double, tripple and
> quadruple ones and they need to become proper unicode symbols too
>
> - fonts have one, two or three sizes, often inconsistent and with funny
> dimensions, onlyt the text size can be trusted
>
> - we cannot use prime as nuclues
- but it isn't designed as a script symbol and is already raised (somewhat)
- so we have to deal with a good old tex / fonts / plain inheritance,
unicode but also want to avoid active character and parsing mess etc.
I tried several approaches and it's hard to come up with a general
solution
a spurious horizontal whitespace after the item
>> symbol when the item is of type “\sym{}”.
>> I also noticed that the problem goes away if I use “inner=” instead of
>> “command=”.
>
> command is applied to the text, try command=\WORD and after \sym is a space
> so
On 5/24/2017 6:28 PM, Thomas Floeren wrote:
Hi,
I used to use the “command=” parameter when setting up itemize. Now I noticed
that it introduces a spurious horizontal whitespace after the item symbol when
the item is of type “\sym{}”.
I also noticed that the problem goes away if I use
Hi,
I used to use the “command=” parameter when setting up itemize. Now I noticed
that it introduces a spurious horizontal whitespace after the item symbol when
the item is of type “\sym{}”.
I also noticed that the problem goes away if I use “inner=” instead of
“command=”.
Example
;>> such as the ones in the example code below, but this should be avoided in
>>>>> my
>>>>> opinion.
>>>>
>>>> well, it depends on how one sees this '' mess
>>>>
>>>> the problem with primes is that in macro packag
ent the behaviour of the latest beta release of mkiv by using tricks
>>>> such as the ones in the example code below, but this should be avoided in
>>>> my
>>>> opinion.
>>>
>>> well, it depends on how one sees this '' mess
>>>
>>
gt;
>> well, it depends on how one sees this '' mess
>>
>> the problem with primes is that in macro packages they are messy entities
>> that should collapse or not (active char mess) and the more clever a macro
>> packages becomes the harder it becomes to makes it robust and
ecomes to makes it robust and/or to fight
against such heuristics
>
> add to that the fact that the symbol itself is a funny positioned
something already raised in a font or not i.e. sometimes in need of
superscript and sometimes explicitly not
>
> for unicode we need to turn two '' into a doubl
e avoided in my opinion.
>
> well, it depends on how one sees this '' mess
>
> the problem with primes is that in macro packages they are messy entities
> that should collapse or not (active char mess) and the more clever a macro
> packages becomes the harder it becomes to makes it robus
that the symbol itself is a funny positioned
something already raised in a font or not i.e. sometimes in need of
superscript and sometimes explicitly not
for unicode we need to turn two '' into a double and ''' into a and
triple such
that said, in context these thingies are at some point
ed there. So at present the
>> bug occurs that ConTeXt uses the smallest optical size for every symbol
>> (independent of the size). This results in strange looking mathematics.
>> Maybe you can fix this, Han
, Hans, even if
this seems to have caused some trouble) support for optical sizes in fallbacks
and I suppose the bug has been introduced there. So at present the bug occurs
that ConTeXt uses the smallest optical size for every symbol (independent of
the size). This results in strange looking
ber...@telia.com>:
>
> > On 15 Sep 2016, at 20:19, Wolfgang Schuster <schuster.wolfg...@gmail.com>
> wrote:
>
> > Another input method is shown in the following video [1] where each
> symbol get its own command, e.g. \mbfitx is equal to {\bi x}. The source
> ta
d that,
> too. Hans did recently add (due to my suggestion, so thanks again, Hans, even
> if this seems to have caused some trouble) support for optical sizes in
> fallbacks and I suppose the bug has been introduced there. So at present the
> bug occurs that ConTeXt uses the sm
d some trouble) support for optical sizes in fallbacks
and I suppose the bug has been introduced there. So at present the bug occurs
that ConTeXt uses the smallest optical size for every symbol (independent of
the size). This results in strange looking mathematics. Maybe you can fix this,
rators, might be nice to have, but U2205 looks
strange, as the empty set symbol comes from a Danish ø, so deselecting just
that one might be of interest.
one more reason for not using stix
the default is the AMS calligraphic style.
On most other features, the STIX2 default seems to what I think of as
traditional.
The feature 'ss07', smaller operators, might be nice to have, but U2205 looks
strange, as the empty set symbol comes from a Dan
onts: 2 files: latinmodern-math.otf,
lmroman12-regular.otf
mkiv lua stats > font engine: otf 3.028, afm 1.512, tfm 1.000, 4 instances,
load time 0.152 seconds
mkiv lua stats > used platform: mswin, type: windows, binary subtree:
texmf-mswin
mkiv lua stats > luatex banner: this is luat
longer.
What can be done to solve this second problem?
One last question remains: I dislike the summation symbol of CambriaMath
(because it is too large in my eyes) and this is why I want to replace it by
the version of STIX2Math again (this symbols is indeed redesigned in STIX2Math
and looks
ymbol{f024}]
>>> \definesymbol [award] [\WebdingsSymbol{f026}]
>>> \definesymbol [ribbon] [\WebdingsSymbol{f02d}]
>>> \definesymbol [plane] [\WebdingsSymbol{f0f1}]
>>> % …
>>> \stopsymbolset
>>>
>>> \usesymbols[webdings]
>>> \showsymb
No, It is not worked.
I mistakenly used a Unicode character in another test.
2017-03-31 12:13 GMT+03:00 Kostirya <kosti...@gmail.com>:
> I apologize.
> It is not hyphen symbol. It is unicode.
> Everything is working!
>
> 2017-03-31 11:46 GMT+03:00 Kostirya <kosti...@gmai
I apologize.
It is not hyphen symbol. It is unicode.
Everything is working!
2017-03-31 11:46 GMT+03:00 Kostirya <kosti...@gmail.com>:
> Hello.
> Two hyphens do not replaced on em—dash when dejavu,14pt
> :-(
>
>
>
> \starttext
> 1-2 11--22
>
> \switch
[\WebdingsSymbol{f026}]
>> \definesymbol [ribbon] [\WebdingsSymbol{f02d}]
>> \definesymbol [plane] [\WebdingsSymbol{f0f1}]
>> % …
>> \stopsymbolset
>>
>> \usesymbols[webdings]
>> \showsymbolset[webdings]
>> \symbol[webdings][spider]
>>
>> The
definesymbol [plane] [\WebdingsSymbol{f0f1}]
% …
\stopsymbolset
\usesymbols[webdings]
\showsymbolset[webdings]
\symbol[webdings][spider]
The font is included in my pdf, \showsymbolset[webdings] lists the
names, but the symbols never show up.
I also tried other fonts.
What’s wrong?
You can get the
Am 2017-03-30 um 18:49 schrieb Lutz Haseloff :
> I recently had the same problem.
> I installed fontforge and opened the fontfile. There you can see the names of
> the glyphs.
Thank you!
But does that mean that MkIV can’t access glyphs by number at all?
Greetlings,
]
\definesymbol[surf][\WebDingSymbol{surf}]
\definesymbol[motorcycle][\WebDingSymbol{motorcycle}]
\definesymbol[mountain][\WebDingSymbol{mountain}]
\definesymbol[art][\WebDingSymbol{art}]
\definesymbol[occasion][\WebDingSymbol{occasion}]
\stopsymbolset
\starttext
\tfc
\symbol[webding][surf]
\symbol
}]
\definesymbol [sunglasses][\WebdingsSymbol{f024}]
\definesymbol [award][\WebdingsSymbol{f026}]
\definesymbol [ribbon][\WebdingsSymbol{f02d}]
\definesymbol [plane][\WebdingsSymbol{f0f1}]
% …
\stopsymbolset
\usesymbols[webdings]
\showsymbolset[webdings]
\symbol[webdings
ua stats > used platform: osx-64, type: unix, binary subtree: bin
mkiv lua stats > luatex banner: this is luatex, version beta-0.80.0
(tex live 2015) (rev 5238)
mkiv lua stats > control sequences: 43101 of 6
cent.pdf, compresslevel 3,
> objectcompresslevel 3
> mkiv lua stats > loaded fonts: 2 files: latinmodern-math.otf,
> lmroman12-regular.otf
> mkiv lua stats > fonts load time: 0.180 seconds
> mkiv lua stats > used platform: osx-64, type: unix, binary subtree: bin
&
nor width=broad,distance=dimension results in the same.
>
>Some information is given here: http://www.ntg.nl/maps/36/09.pdf
>Enumerations and descriptions share a lot of settings.
Thank you. I read it. I have a question: is it possible to add some text or
command
between the head and text
garden.net/
>
> On 02/01/2017 04:43 PM, Lawrence Bell wrote:
> > I'm having some difficulties with nested itemgroups. I've produced a
> > minimal working example as follows.
> >
> > \defineitemgroup
> > [test] [symbol=n]
> >
> > \starttext
> &
inimal working example as follows.
>
> \defineitemgroup
> [test] [symbol=n]
>
> \starttext
>
> % \startitemgroup
> % \startitem
> % \startitemgroup[test]
> % \startitem
> % ...
> % \stopitem
> % \stopitemgroup
> % \
I'm having some difficulties with nested itemgroups. I've produced a
minimal working example as follows.
\defineitemgroup
[test] [symbol=n]
\starttext
% \startitemgroup
% \startitem
% \startitemgroup[test]
% \startitem
% ...
% \stopitem
% \stopitemgroup
Hello,
the solution works fine, thank you!
Best regards,
Lukas
On Tue, 31 Jan 2017 13:08:28 +0100, Otared Kavian <ota...@gmail.com> wrote:
Hi Lukas,
Maybe you can use
symbol=\lower.25em\hbox{.},
instead of what you set in your \definefiller definition is what you need?
Hi Lukas,
Maybe you can use
symbol=\lower.25em\hbox{.},
instead of what you set in your \definefiller definition is what you need?
Best regards: OK
> On 31 Jan 2017, at 12:33, Procházka Lukáš Ing. <l...@pontex.cz> wrote:
>
> Hello,
>
> the following code:
>
Hello,
the following code:
\definefiller
[DotFill]
[alternative=symbol,
symbol=.,
width=.5em,
style=\txx]
Fill here: \filler[DotFill]{}
produces filler with dots on the baseline.
Is there a way to shift the dots a bit lower, bellow the baseline, e.g. to
0.25em
ng a placeholder `\meaning' there
(never attempting to use it as a command acting on the explanatory text
for that symbol definition but only wanting a glossary.
the strange thing (for me) is that this worked just fine two years ago,
now it does produce a very strange error as described. question is why
ver
attempting to use it as a command acting on the explanatory text for that
symbol definition but only wanting a glossary.
the strange thing (for me) is that this worked just fine two years ago,
now it does produce a very strange error as described. question is why.
but replacing `\mean
Hans Hagen writes:
>
> this just works here ... so can others confirm it?
>
> \starttext
>
> \startformula
> x = \left ( 1 + 2 \right )
> \stopformula
>
> \stoptext
>
>
Here too:
resolvers | trees | analyzing 'home:texmf'
resolvers | globbing | confusing
On Tue, 24 Jan 2017 15:15:09 +0100, luigi scarso
wrote:
On Tue, Jan 24, 2017 at 3:02 PM, Hans Hagen wrote:
this just works here ... so can others confirm it?
\starttext
\startformula
x = \left ( 1 + 2 \right )
\stopformula
\stoptext
no
On Tue, Jan 24, 2017 at 3:02 PM, Hans Hagen wrote:
> this just works here ... so can others confirm it?
>
> \starttext
>
> \startformula
> x = \left ( 1 + 2 \right )
> \stopformula
>
> \stoptext
>
>
no problem here with
This is LuaTeX, Version 1.0.2 (TeX Live 2017/dev)
On 1/24/2017 2:33 PM, j. van den hoff wrote:
On Tue, 24 Jan 2017 14:15:08 +0100, Hans Hagen wrote:
thanks for the quick reply and sorry for my not being precise.
correction/addition follows:
On 1/24/2017 11:33 AM, j. van den hoff wrote:
hi everybody,
after a 2 year hiatus
On Tue, 24 Jan 2017 14:15:08 +0100, Hans Hagen wrote:
thanks for the quick reply and sorry for my not being precise.
correction/addition follows:
On 1/24/2017 11:33 AM, j. van den hoff wrote:
hi everybody,
after a 2 year hiatus I'm just giving `context' a second try (so,
On 1/24/2017 11:33 AM, j. van den hoff wrote:
hi everybody,
after a 2 year hiatus I'm just giving `context' a second try (so, really
not much experience so far).
I updated to the latest version (0.63) before proceeding.
0.63 what? luatex? then you need to check things as we're beyond 1.00
hi everybody,
after a 2 year hiatus I'm just giving `context' a second try (so, really
not much experience so far).
I updated to the latest version (0.63) before proceeding.
two observations:
1.
in a new document including assorted equations everything went fine until
I tried something
to get options to center the glyphs from which
the symbol is assembled (separate horizontal and vertical, with the
ability to offset them)?
Is there a ConTeXt way other than \definesymbol to create such
combined symbols?
MetaPost (with textext())?
Thank you for that, Alan. I hadn’t ever used MetaPost
yphs from which
> the symbol is assembled (separate horizontal and vertical, with the
> ability to offset them)?
>
> Is there a ConTeXt way other than \definesymbol to create such
> combined symbols?
MetaPost (with textext())?
_
be centered. Rather, it
leaves the work to a process of tuning the horizontal and vertical
levers (kern and raise here) to get something that is close, but rarely
perfect.
I also see some problems with the horizontal spacing around the new
symbol, but that may be a function of the underlying glyphs
agenumbering[location=]
> \setupfooter[style=small, color=colortwo]
> \setupfootertexts[][\userpagenumber/\lastuserpage]
>
> % Lists
> \startuseMPgraphic{itemize:main}
> save p; path p;
> p := fullcircle scaled 1.5ExHeight;
> fill p withcolor \MPcolor{colorfive};
> \stopu
definesymbol[itemize:main][\useMPgraphic{itemize:main}]
\definesymbol[itemize:nested][\useMPgraphic{itemize:nested}]
\setupitemize[1][symbol=itemize:main]
\setupitemize[2][symbol=itemize:nested, width=1.5ex]
\setupitemize[2][nowhite]
\setupitemize[
headstyle=\ssa,
headcolor=colorfive,
On 12/29/2016 12:12 PM, Fabrice Couvreur wrote:
Hi Hans,
Thanks for your solution. I created a macro, is it "robust" ?
Fabrice
\setupmathextensible[integral][rightoffset=-3mu,exact=yes,factor=2]
\unexpanded
\def\integ#1#2#3{\math{\autointegral{#1}{#2}{#3}\diff x}}
\starttext
Hi Hans,
Thanks for your solution. I created a macro, is it "robust" ?
Fabrice
\setupmathextensible[integral][rightoffset=-3mu,exact=yes,factor=2]
\def\integ#1#2#3{\math{\autointegral{#1}{#2}{#3}\diff x}}
\starttext
\integ{4}{1}{g(x)}
\stoptext
2016-12-28 18:40 GMT+01:00 Hans Hagen
On 12/28/2016 6:14 PM, Alan Braslau wrote:
Hi Hans, Hi list,
This is similar to what we have discussed earlier on this list and
elsewhere regarding \over vs. \frac. (I agree with Knuth that {a \over
b} is *much* more readable in running source code than \frac{a}{b} but
have resigned myself to
Hi Hans, Hi list,
This is similar to what we have discussed earlier on this list and
elsewhere regarding \over vs. \frac. (I agree with Knuth that {a \over
b} is *much* more readable in running source code than \frac{a}{b} but
have resigned myself to use \frac{}{}, as this can be made better
uvreur wrote:
> Hello,
> The integral symbol is little in inline math mode. Is it possible to have
it bigger ?
> thank you,
> Fabrice
>
> \definetypeface [mainface] [rm]
>[serif] [palatino][default] [encoding=texnansi]
>
> \define
Hi Henri,
Thank you for your suggestion.
Fabrice
2016-12-28 12:19 GMT+01:00 Henri Menke <henrime...@gmail.com>:
> On 12/28/2016 11:39 AM, Fabrice Couvreur wrote:
> > Hello,
> > The integral symbol is little in inline math mode. Is it possible to
> have it bigger ?
&g
On 12/28/2016 11:39 AM, Fabrice Couvreur wrote:
> Hello,
> The integral symbol is little in inline math mode. Is it possible to have it
> bigger ?
> thank you,
> Fabrice
>
> \definetypeface [mainface] [rm]
>[serif] [palatino][default] [encoding=texnansi]
>
Hello,
The integral symbol is little in inline math mode. Is it possible to have
it bigger ?
thank you,
Fabrice
\definetypeface [mainface] [rm]
[serif] [palatino][default] [encoding=texnansi]
\definetypeface [mainface] [ss]
[sans] [helvetica] [default] [encoding=texnansi
is this a real bug?
>
> \startxmlsetups xml:pre:code
> solution one \begingroup
> \expandUx
> \comment[symbol=Key, location=inmargin,color=yellow]{\xmlflush{#1}}
> \endgroup
> \par
> solution two
> \comment[symbol=Key, location
:*}
\xmlsetsetup{#1}{doc|p|code}{xml:*}
\xmlsetsetup{#1}{pre/code}{xml:pre:code}
\stopxmlsetups
\xmlregistersetup{xml:initialize}
\startxmlsetups xml:doc
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:pre:code
\comment[symbol=Key, location
:*}
\xmlsetsetup{#1}{pre/code}{xml:pre:code}
\stopxmlsetups
\xmlregistersetup{xml:initialize}
\startxmlsetups xml:doc
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:pre:code
\comment[symbol=Key, location=inmargin,
color=yellow
symbols are not defined. Do you know if unicode math
> fonts provide these symbols and if they are part of Unicode math
> symbol list?
>
> Aditya
I'm not sure. That said, XeTeX can render them using Latin Modern Roman
and Math so they are available.
For what its worth they can be fo
in math mode?
AFAIK, these symbols are not defined. Do you know if unicode math fonts
provide these symbols and if they are part of Unicode math symbol list?
Aditya
___
If your question is of interest to others as well
}{xml:pre:code}
\stopxmlsetups
\xmlregistersetup{xml:initialize}
\startxmlsetups xml:doc
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:pre:code
\comment[symbol=Key, location=inmargin,
color=yellow]{\xmlflush{#1}}\xmlprettyprint{#1}{tex
roup
>> %[itemize]
>> %[each]
>> %[autointro,packed]
>> %[symbol=2]
>
> Use
>
> \setupitemgroup
> [itemize]
> [each]
> [packed]
> [symbol=2]
>
>
> Herbert
>
>
>>
>> \starttext
>> \star
Am 20.11.2016 um 20:25 schrieb Willi Egger:
I have the following minimal example
% \setupitemgroup
% [itemize]
% [each]
% [autointro,packed]
% [symbol=2]
Use
\setupitemgroup
[itemize]
[each]
[packed]
[symbol=2]
Herbert
\starttext
501 - 600 of 2317 matches
Mail list logo