Hi, I am attaching myway on using matharrow. Are there any suggestions before I release it to public? I found some surprises while making this my way. 1. Somewhere along the line of development, \xrightarrow{text} changed to placing text at the bottom of the arrow (rather than the top as in amstex). This is not a bug, just something that works differently. Should this be changed? These arrow definitions are pretty new, so I do not think that a change at this stage will effect too many users. It may not be possible to change later for compatibility reasons. 2. Something goes wrong with palatino (used by mag-01). Have a look at the \xmapsto and \xrightleftharpoons and \xleftrightharpoons in the pdf. \xmapsto can be corrected by changing its defintion to \definematharrow [xmapsto] [3599] [\mapstofill] Basically, providing a bit more cusion on the left, so that the middle \relbar not overlap the \mapstochar. Should this definition go to math-ext.tex or to something specific to palatino. I have not tested with other fonts, but what is the general strategy when definitions differ for different fonts? I could not correct leftrightharpoons. Why does this not work? \definematharrow [xleftrightharpoons] [3395,3359] [\leftharpoonupfill,\rightharpoondownfill] \starttext \math{\xleftrightharpoons} \stoptext Aditya
On 7/19/06, Aditya Mahajan wrote:
Hi,
I am attaching myway on using matharrow. Are there any suggestions before I release it to public?
I found some surprises while making this my way.
Now that you're all experts in arrows: I'm still looking for \overrightharpoonup that would: - be small enough, so that it would still look ok when placed over (dotless) i or j. - decrease with style: $\overrrightharpoonup{AB}_{\overrightharponup{CD}}$ the second arrow should be smaller.
1. Somewhere along the line of development, \xrightarrow{text} changed to placing text at the bottom of the arrow (rather than the top as in amstex). This is not a bug, just something that works differently. Should this be changed? These arrow definitions are pretty new, so I do not think that a change at this stage will effect too many users. It may not be possible to change later for compatibility reasons.
I guess that you might even be the only one who used that so far, so if you want compatibility, fix it now! (I never used that functionality in LaTeX, so I don't know how it works there).
2. Something goes wrong with palatino (used by mag-01). Have a look at the \xmapsto and \xrightleftharpoons and \xleftrightharpoons in the pdf. \xmapsto can be corrected by changing its defintion to
\definematharrow [xmapsto] [3599] [\mapstofill]
Basically, providing a bit more cusion on the left, so that the middle \relbar not overlap the \mapstochar.
Should this definition go to math-ext.tex or to something specific to palatino. I have not tested with other fonts, but what is the general strategy when definitions differ for different fonts?
Taco - now that you have enough experince with cows: do you have any suggestions about how to create nice arrows with antykwa-torunska as well? Mojca
Hi, Mojca Miklavec wrote:
Now that you're all experts in arrows: I'm still looking for \overrightharpoonup that would: - be small enough, so that it would still look ok when placed over (dotless) i or j. - decrease with style: $\overrrightharpoonup{AB}_{\overrightharponup{CD}}$ the second arrow should be smaller.
That is an accent, and therefore quite different from the current pointy stuff. Shouldnt be very hard to do though, I'll attempt something.
Taco - now that you have enough experince with cows: do you have any suggestions about how to create nice arrows with antykwa-torunska as well?
Because the arrows are not "flat", you mean? If we would have separate heads, shafts and tails, we could stretch the shafts using similar logic to cow font. But those are not in there, I assume? Taco
Aditya Mahajan wrote:
Hi,
I am attaching myway on using matharrow. Are there any suggestions before I release it to public?
I found some surprises while making this my way.
1. Somewhere along the line of development, \xrightarrow{text} changed to placing text at the bottom of the arrow (rather than the top as in amstex). This is not a bug, just something that works differently. Should this be changed? These arrow definitions are pretty new, so I do not think that a change at this stage will effect too many users. It may not be possible to change later for compatibility reasons.
In the interest of porting stuff from amstex, changing the behaviour is probably better.
2. Something goes wrong with palatino (used by mag-01). Have a look at the \xmapsto and \xrightleftharpoons and \xleftrightharpoons in the pdf. \xmapsto can be corrected by changing its defintion to
\definematharrow [xmapsto] [3599] [\mapstofill]
Basically, providing a bit more cusion on the left, so that the middle \relbar not overlap the \mapstochar.
Should this definition go to math-ext.tex or to something specific to palatino. I have not tested with other fonts, but what is the general strategy when definitions differ for different fonts?
something should be possible with mathcollections, I guess? (Hans knows this better then I do)
I could not correct leftrightharpoons. Why does this not work?
\definematharrow [xleftrightharpoons] [3395,3359] [\leftharpoonupfill,\rightharpoondownfill]
Because the current definition of dodoxmtharrow does not like it when the second arg starts with two identical digits. Changing it to this fixes the problem: \def\dodoxmtharrow[#1,#2,#3][#4,#5,#6][#7]#8#9% {\edef\tempa{#2}\ifx\tempa\empty %TH changed line \mathrel{\domthxarrsingle{#7}{#1}{#4}{#8}{#9}}% \else \mathrel{\domthxarrdouble{#7}{#1}{#2}{#4}{#5}{#8}{#9}}% \fi}
Taco Hoekwater wrote:
Aditya Mahajan wrote:
Hi,
I am attaching myway on using matharrow. Are there any suggestions before I release it to public?
I found some surprises while making this my way.
1. Somewhere along the line of development, \xrightarrow{text} changed to placing text at the bottom of the arrow (rather than the top as in amstex). This is not a bug, just something that works differently. Should this be changed? These arrow definitions are pretty new, so I do not think that a change at this stage will effect too many users. It may not be possible to change later for compatibility reasons.
In the interest of porting stuff from amstex, changing the behaviour is probably better.
\def\dodoxmtharrow[#1,#2,#3][#4,#5,#6][#7]#8#9% [3] is the optional arg {\ifx#2\empty \ifsecondargument \mathrel{\domthxarrsingle{#7}{#1}{#4}{#8}{#9}}% \else \mathrel{\domthxarrsingle{#7}{#1}{#4}{}{#8}}% \fi \else \ifsecondargument \mathrel{\domthxarrdouble{#7}{#1}{#2}{#4}{#5}{#8}{#9}}% \else \mathrel{\domthxarrdouble{#7}{#1}{#2}{#4}{#5}{}{#8}}% \fi \fi}
2. Something goes wrong with palatino (used by mag-01). Have a look at the \xmapsto and \xrightleftharpoons and \xleftrightharpoons in the pdf. \xmapsto can be corrected by changing its defintion to
\definematharrow [xmapsto] [3599] [\mapstofill]
Basically, providing a bit more cusion on the left, so that the middle \relbar not overlap the \mapstochar.
Should this definition go to math-ext.tex or to something specific to palatino. I have not tested with other fonts, but what is the general strategy when definitions differ for different fonts?
something should be possible with mathcollections, I guess? (Hans knows this better then I do)
it's font related, not collection related; the problem with these things is that in context we want to deal with mixed math font usage so we need to figure out a clever way
I could not correct leftrightharpoons. Why does this not work?
\definematharrow [xleftrightharpoons] [3395,3359] [\leftharpoonupfill,\rightharpoondownfill]
Because the current definition of dodoxmtharrow does not like it when the second arg starts with two identical digits. Changing it to this fixes the problem:
\def\dodoxmtharrow[#1,#2,#3][#4,#5,#6][#7]#8#9% {\edef\tempa{#2}\ifx\tempa\empty %TH changed line \mathrel{\domthxarrsingle{#7}{#1}{#4}{#8}{#9}}% \else \mathrel{\domthxarrdouble{#7}{#1}{#2}{#4}{#5}{#8}{#9}}% \fi}
ok, so we get \def\dodoxmtharrow[#1,#2,#3][#4,#5,#6][#7]#8#9% [3] is the optional arg {\edef\!!string{#2}% \ifx\!!stringa\empty \ifsecondargument \mathrel{\domthxarrsingle{#7}{#1}{#4}{#8}{#9}}% \else \mathrel{\domthxarrsingle{#7}{#1}{#4}{}{#8}}% \fi \else \ifsecondargument \mathrel{\domthxarrdouble{#7}{#1}{#2}{#4}{#5}{#8}{#9}}% \else \mathrel{\domthxarrdouble{#7}{#1}{#2}{#4}{#5}{}{#8}}% \fi \fi} Hans -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Aditya Mahajan wrote:
Hi,
I am attaching myway on using matharrow. Are there any suggestions before I release it to public?
I found some surprises while making this my way.
1. Somewhere along the line of development, \xrightarrow{text} changed to placing text at the bottom of the arrow (rather than the top as in amstex). This is not a bug, just something that works differently. Should this be changed? These arrow definitions are pretty new, so I do not think that a change at this stage will effect too many users. It may not be possible to change later for compatibility reasons.
2. Something goes wrong with palatino (used by mag-01). Have a look at the \xmapsto and \xrightleftharpoons and \xleftrightharpoons in the pdf. \xmapsto can be corrected by changing its defintion to
\definematharrow [xmapsto] [3599] [\mapstofill]
Basically, providing a bit more cusion on the left, so that the middle \relbar not overlap the \mapstochar.
Should this definition go to math-ext.tex or to something specific to palatino. I have not tested with other fonts, but what is the general strategy when definitions differ for different fonts?
I could not correct leftrightharpoons. Why does this not work?
\definematharrow [xleftrightharpoons] [3395,3359] [\leftharpoonupfill,\rightharpoondownfill]
\starttext \math{\xleftrightharpoons} \stoptext
ok, a dirty trick: when no third arg, then one redefines the dimensions \starttext \def\dodefinematharrow[#1][#2][#3][#4]% {\iffourthargument \executeifdefined{dodefine#2arrow} \gobblethreearguments{#1}{#3}{#4}% \else\ifthirdargument \dodefinebotharrow{#1}{#2}{#3}% \else\ifsecondargument \redefinebotharrow{#1}{#2}{#3}% \fi\fi\fi} \def\redefinebotharrow#1#2#3% {\doifdefined{#1} {\pushmacro\dotripleempty \def\dotripleempty##1[##2][##3]% {\setvalue{#1}{\dotripleempty\xmtharrow[#2][##3]}}% \getvalue{#1}% \popmacro\dotripleempty}} \def\dodefinebotharrow#1#2#3% {\setvalue{#1}{\dotripleempty\xmtharrow[#2][#3]}} \startformula \xrightarrow{stuff on top} \stopformula \definematharrow[xrightarrow][9999] \startformula \xrightarrow{stuff on top} \stopformula \definematharrow[xrightarrow][0000] \startformula \xrightarrow{stuff on top} \stopformula \stoptext ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Wed, 19 Jul 2006, Hans Hagen wrote:
Aditya Mahajan wrote:
Hi,
I am attaching myway on using matharrow. Are there any suggestions before I release it to public?
I found some surprises while making this my way.
1. Somewhere along the line of development, \xrightarrow{text} changed to placing text at the bottom of the arrow (rather than the top as in amstex). This is not a bug, just something that works differently. Should this be changed? These arrow definitions are pretty new, so I do not think that a change at this stage will effect too many users. It may not be possible to change later for compatibility reasons.
2. Something goes wrong with palatino (used by mag-01). Have a look at the \xmapsto and \xrightleftharpoons and \xleftrightharpoons in the pdf. \xmapsto can be corrected by changing its defintion to
\definematharrow [xmapsto] [3599] [\mapstofill]
Basically, providing a bit more cusion on the left, so that the middle \relbar not overlap the \mapstochar.
Should this definition go to math-ext.tex or to something specific to palatino. I have not tested with other fonts, but what is the general strategy when definitions differ for different fonts?
I could not correct leftrightharpoons. Why does this not work?
\definematharrow [xleftrightharpoons] [3395,3359] [\leftharpoonupfill,\rightharpoondownfill]
\starttext \math{\xleftrightharpoons} \stoptext
ok, a dirty trick: when no third arg, then one redefines the dimensions
Great. Now we can redefine arrows in font specific scenarios. For mapsto I think that a global redefinition in math-ext to \definematharrow [xmapsto] [3599] [\mapstofill] works fine for lm, palatino and times. For leftrightharpoons, I need more time to come up with something that is suitable for all fonts. If nothing works out, only then we would need to do font specific behaviour (I wish to avoid that, if possible.) For all this trouble, here are some bonus arrows :-) \def\hookleftfill {\mtharrowfill \leftarrow \relbar {\relbar\joinrel\rhook}} \def\hookrightfill {\mtharrowfill {\lhook\joinrel\relbar} \relbar \rightarrow} \definematharrow [xhookleftarrow] [3095] [\hookleftfill] \definematharrow [xhookrightarrow] [0395] [\hookrightfill] Aditya
On Wed, 19 Jul 2006, Taco Hoekwater wrote:
Aditya,
Aditya Mahajan wrote:
Great. Now we can redefine arrows in font specific scenarios. For mapsto I think that a global redefinition in math-ext to
Are you keeping track of all those math-ext.tex extensions today?
I am (rather I hope I am). I will send an updated math-ext.tex once I can figure something about harpoons. Aditya
Taco Hoekwater wrote:
Aditya,
Aditya Mahajan wrote:
Great. Now we can redefine arrows in font specific scenarios. For mapsto I think that a global redefinition in math-ext to
Are you keeping track of all those math-ext.tex extensions today?
i'll make an alpha release ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Wed, 19 Jul 2006, Hans Hagen wrote:
Taco Hoekwater wrote:
Aditya,
Aditya Mahajan wrote:
Great. Now we can redefine arrows in font specific scenarios. For mapsto I think that a global redefinition in math-ext to
Are you keeping track of all those math-ext.tex extensions today?
i'll make an alpha release
I think that I have finally managed to come up with the magic numbers. The following work fine for LM, times, fourier and palatino. \xmapsto also works fine with euler, but harpoons do not work with euler (missing symbols). Hans, can you change the definitions in math-ext to \definematharrow [xmapsto] [3599] [\mapstofill] \definematharrow [xleftrightharpoons] [3399,3399] [\leftharpoonupfill,\rightharpoondownfill] \definematharrow [xrightleftharpoons] [3399,3399] [\rightharpoonupfill,\leftharpoondownfill] None of the extensible arrows work with antykwa-torunska as \relbar is not of fixed width in that font. Are there any other free math fonts that I should check? Aditya
On Wed, 19 Jul 2006, Taco Hoekwater wrote:
Aditya Mahajan wrote:
None of the extensible arrows work with antykwa-torunska as \relbar is not of fixed width in that font. Are there any other free math fonts that I should check?
iwona and kurier have math nowadays, don't they?
Tested for iwona and it works fine. I do not know how to get kurier to work (I was looking at typescripts defined in type-exa and kurier is not there). Regarding the free fonts survey that Mojca sent, I do not know how to use others in Context. Can typescripts for these be included in type-exa? Aditya
Aditya Mahajan wrote:
On Wed, 19 Jul 2006, Taco Hoekwater wrote:
Aditya Mahajan wrote:
None of the extensible arrows work with antykwa-torunska as \relbar is not of fixed width in that font. Are there any other free math fonts that I should check?
iwona and kurier have math nowadays, don't they?
Tested for iwona and it works fine. I do not know how to get kurier to work (I was looking at typescripts defined in type-exa and kurier is not there).
\usetypescript[iwona] [texnansi] \usetypescript[kurier][texnansi] ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Thu, 20 Jul 2006, Hans Hagen wrote:
Aditya Mahajan wrote:
On Wed, 19 Jul 2006, Taco Hoekwater wrote:
Aditya Mahajan wrote:
None of the extensible arrows work with antykwa-torunska as \relbar is not of fixed width in that font. Are there any other free math fonts that I should check?
iwona and kurier have math nowadays, don't they?
Tested for iwona and it works fine. I do not know how to get kurier to work (I was looking at typescripts defined in type-exa and kurier is not there).
\usetypescript[iwona] [texnansi] \usetypescript[kurier][texnansi]
Kurier typeface is not defined anywhere! The following definition should be part of type-exa.tex --------------------------------------%<-------------------------------------- \starttypescript [kurier-light,kurier,kurier-medium] [texnansi,ec,8r,uc,t2a] % todo: rscale \definetypeface[\typescriptone][ss][sans] [\typescriptone] [default][encoding=\typescripttwo] \definetypeface[\typescriptone][rm][serif][modern] [default][encoding=\typescripttwo] \definetypeface[\typescriptone][tt][mono] [modern] [default][encoding=\typescripttwo] \definetypeface[\typescriptone][mm][math] [\typescriptone] [default][encoding=\typescripttwo,text=ss] \stoptypescript --------------------------------------%<-------------------------------------- Also, why not add all iwona variants to \starttypescript for iwona. --------------------------------------%<-------------------------------------- \starttypescript [iwona-light,iwona,iwona-medium,iwona-heavy,iwona-light-cond,iwona-cond,iwona-medium-cond,iwona-heavy-cond] [texansi,ec,8r,uc,t2a] --------------------------------------%<-------------------------------------- instead of \starttypescript [iwona,iwona-light,iwona-heavy,iwona-medium] [texnansi,ec,8r,uc,t2a] The arrows work fine with kurier. I will write an email to Janusz asking for a "arrow shaft" glyph for math in antkiwa. Aditya
Aditya Mahajan wrote:
The arrows work fine with kurier. I will write an email to Janusz asking for a "arrow shaft" glyph for math in antkiwa.
Ideally, we need two sets for each arrow: % a more or less normal TeX set with and extra % tail section: <arrow head with straight connecting bar> <straight bar> <arrow tail end> % a set for CM transform based macros: <arrow head totally without bar> <tapered arrow shaft> <arrow tail without shaft> and those (of course) for all eight standard arrows (four directions * double shafted) Taco
On Fri, 21 Jul 2006, Taco Hoekwater wrote:
Aditya Mahajan wrote:
The arrows work fine with kurier. I will write an email to Janusz asking for a "arrow shaft" glyph for math in antkiwa.
Ideally, we need two sets for each arrow: % a more or less normal TeX set with and extra % tail section: <arrow head with straight connecting bar> <straight bar> <arrow tail end>
% a set for CM transform based macros: <arrow head totally without bar> <tapered arrow shaft> <arrow tail without shaft>
and those (of course) for all eight standard arrows (four directions * double shafted)
So should I send a request to both Janusz and Boguslaw for these 8 glyphs in all the fonts that they maintain (LM, antkiwa, kurier, iwona)? Aditya
Aditya Mahajan wrote:
On Fri, 21 Jul 2006, Taco Hoekwater wrote:
Aditya Mahajan wrote:
The arrows work fine with kurier. I will write an email to Janusz asking for a "arrow shaft" glyph for math in antkiwa.
Ideally, we need two sets for each arrow: % a more or less normal TeX set with and extra % tail section: <arrow head with straight connecting bar> <straight bar> <arrow tail end>
% a set for CM transform based macros: <arrow head totally without bar> <tapered arrow shaft> <arrow tail without shaft>
and those (of course) for all eight standard arrows (four directions * double shafted)
So should I send a request to both Janusz and Boguslaw for these 8 glyphs in all the fonts that they maintain (LM, antkiwa, kurier, iwona)? indeed
----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 7/19/06, Aditya Mahajan wrote:
None of the extensible arrows work with antykwa-torunska as \relbar is not of fixed width in that font. Are there any other free math fonts that I should check?
http://ctan.tug.org/tex-archive/info/Free_Math_Font_Survey/survey.html To Taco: Polish guys are open to suggestions. Could you explain them what exactly is needed? I'm sure that they will add that to their font(s). An interesting approach that I saw in OpenOffice (which I use once per year): there's an arrow and an arrow extension + kerning defined between the two, so that software doesn't need to think about proper placement. If you put arrow extention and the arrow, they will be properly kerned to make a nice longer arrow. Mojca
Mojca Miklavec wrote:
On 7/19/06, Aditya Mahajan wrote:
None of the extensible arrows work with antykwa-torunska as \relbar is not of fixed width in that font. Are there any other free math fonts that I should check?
http://ctan.tug.org/tex-archive/info/Free_Math_Font_Survey/survey.html
To Taco: Polish guys are open to suggestions. Could you explain them what exactly is needed? I'm sure that they will add that to their font(s).
I am yet undecided what the best solution would be. There are basically two options: <head><leaders stem><tail> and <head><stem streched using CM><tail> The first case works always (and is the approach used by the cow font) but this looks sub-optimal for fonts like torunska, the second one only works if the CM can be adjusted but will generally look better. I would like to know how many backends cannot do the stretching. Both solutions need special characters in the font, but the first solution needs slightly different ones than the second one. Cheers, Taco
Taco Hoekwater wrote:
Mojca Miklavec wrote:
On 7/19/06, Aditya Mahajan wrote:
None of the extensible arrows work with antykwa-torunska as \relbar is not of fixed width in that font. Are there any other free math fonts that I should check?
http://ctan.tug.org/tex-archive/info/Free_Math_Font_Survey/survey.html
To Taco: Polish guys are open to suggestions. Could you explain them what exactly is needed? I'm sure that they will add that to their font(s).
I am yet undecided what the best solution would be. There are basically two options:
<head><leaders stem><tail> and <head><stem streched using CM><tail>
The first case works always (and is the approach used by the cow font) but this looks sub-optimal for fonts like torunska, the second one only works if the CM can be adjusted but will generally look better.
I would like to know how many backends cannot do the stretching.
Both solutions need special characters in the font, but the first solution needs slightly different ones than the second one.
how about supporting both methods, ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Hans Hagen wrote:
I would like to know how many backends cannot do the stretching.
Both solutions need special characters in the font, but the first solution needs slightly different ones than the second one.
how about supporting both methods,
I'll get back to this after the cows are finished Taco
On 7/20/06, Taco Hoekwater wrote:
Hans Hagen wrote:
I would like to know how many backends cannot do the stretching.
Both solutions need special characters in the font, but the first solution needs slightly different ones than the second one.
how about supporting both methods,
I'll get back to this after the cows are finished
Thanks! Do you have any slides/whatever material with cows published somewhere? Mojca
Mojca Miklavec wrote:
On 7/20/06, Taco Hoekwater wrote:
Hans Hagen wrote:
I would like to know how many backends cannot do the stretching.
Both solutions need special characters in the font, but the first solution needs slightly different ones than the second one.
how about supporting both methods,
I'll get back to this after the cows are finished
Thanks!
Do you have any slides/whatever material with cows published somewhere?
There is a cow paper in the preprints of eurotex2006, but the only published material at this point is here: http://wiki.contextgarden.net/Context_2006.07.13 :) What did you have in mind? (that paper will also appear in this autumns maps issue, and I know that Hans is working on manual but that is not finished yet). Taco
On 7/20/06, Taco Hoekwater
Mojca Miklavec wrote:
On 7/20/06, Taco Hoekwater wrote:
Hans Hagen wrote:
I would like to know how many backends cannot do the stretching.
Both solutions need special characters in the font, but the first solution needs slightly different ones than the second one.
how about supporting both methods,
I'll get back to this after the cows are finished
Thanks!
Do you have any slides/whatever material with cows published somewhere?
There is a cow paper in the preprints of eurotex2006,
Great! (Is it going to be sent to LUG members as last year or is there any other way to get it?)
but the only published material at this point is here:
A question to Patrick: the font is very blurred (or however you may call it). I remember a discussion on this issue some time ago, but this time it really seems to me that the fonts should be more sharp. What's the reason for using convert -blur 0.2 ... if this could be done by gs already by setting -r150 instead of having to additionally scale down the image?
What did you have in mind? (that paper will also appear in this autumns maps issue, and I know that Hans is working on manual but that is not finished yet).
Even "more great" ;) Mojca
Mojca Miklavec wrote:
Great! (Is it going to be sent to LUG members as last year or is there any other way to get it?)
i assume that (as last year) it will end up in the postbox of lug members btw, you've seen the colorful slides in den helder so ... Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 7/20/06, Hans Hagen wrote:
Mojca Miklavec wrote:
Great! (Is it going to be sent to LUG members as last year or is there any other way to get it?)
i assume that (as last year) it will end up in the postbox of lug members
btw, you've seen the colorful slides in den helder so ...
True, but the others didn't (it's a pitty that materials from NTG meetings "get lost"). (And I would really like to see the source of those wonderful slides. I'm impressed how well the quare root now works ;) Mojca
Mojca Miklavec wrote:
True, but the others didn't (it's a pitty that materials from NTG meetings "get lost").
(And I would really like to see the source of those wonderful slides. I'm impressed how well the quare root now works ;)
I am not so happy yet myself. $\sqrt{\frac12}$ has much too much whitespace, and $\sqrt{\frac{\frac12}{\frac34}}$ is just plain wrong :( Anyway, the slides are mostly just \externalfigures, but the paper is sort of interesting. It is here: http://matexhu.org/eurotex2006/papers/Taco2/ but please do not publish that anywhere since it is not finished yet. Taco
Quoting Taco Hoekwater
Mojca Miklavec wrote:
True, but the others didn't (it's a pitty that materials from NTG meetings "get lost").
(And I would really like to see the source of those wonderful slides. I'm impressed how well the quare root now works ;)
I am not so happy yet myself. $\sqrt{\frac12}$ has much too much whitespace, and $\sqrt{\frac{\frac12}{\frac34}}$ is just plain wrong :(
The font is nice and fresh. I am thinking of using it for title frames in presentations, but am a bit apprehensive...
Anyway, the slides are mostly just \externalfigures, but the paper is sort of interesting. It is here:
It is really intesting to know the history behind the font. However I was surprised with $$ \vbox{ \centerline{\framed{\contextlogob}} \medskip \centerline{\framed{\contextlogoa}} \medskip \centerline{\framed{\contextlogoc}} \medskip \centerline{\framed{\contextlogod}} } $$ When you have a hammer, everything looks like a nail ;) Aditya
On 7/20/06, Taco Hoekwater wrote:
Anyway, the slides are mostly just \externalfigures, but the paper is sort of interesting. It is here:
http://matexhu.org/eurotex2006/papers/Taco2/
but please do not publish that anywhere since it is not finished yet.
Thank you! Mojca
Aditya Mahajan wrote:
For all this trouble, here are some bonus arrows :-)
\def\hookleftfill {\mtharrowfill \leftarrow \relbar {\relbar\joinrel\rhook}}
\def\hookrightfill {\mtharrowfill {\lhook\joinrel\relbar} \relbar \rightarrow}
\definematharrow [xhookleftarrow] [3095] [\hookleftfill] \definematharrow [xhookrightarrow] [0395] [\hookrightfill]
added Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (4)
-
Aditya Mahajan -
Hans Hagen -
Mojca Miklavec -
Taco Hoekwater