Re: [NTG-context] Creating SVG: using MetaFun, exporting proper units, conversion to DXF

[Jan Tosovsky]

On 2016-06-29 Mojca Miklavec wrote:
> 
> I want to play with CNC and don't yet have any experience with CAD
> software (nor the licence for the expensive ones) other than perhaps
> some Blender, so I decided to try to use the super ugly route with
> metapost -> svg -> dxf -> g-code for the first time.

For simple shapes I'd choose Inkscape SVG editor, which can export to DXF 
directly. In settings you can customize the coords precision to reduce those 
fractions.

For more sophisticated designing I'd skip simple 2D CADs and use parametric 
tools instead (allowing to use equations instead of fixed values which 
simplifies future refactoring).

I'd recommend Autodesk Fusion, which is even free for enthusiasts:
https://knowledge.autodesk.com/support/fusion-360/troubleshooting/caas/sfdcarticles/sfdcarticles/How-to-activate-start-up-or-educational-licensing-for-Fusion-360.html

https://www.youtube.com/watch?v=VzqXo0d0W8s

Jan

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Creating SVG: using MetaFun, exporting proper units, conversion to DXF

[Mojca Miklavec]

On 29 June 2016 at 14:12, Hans Hagen wrote:
> On 6/29/2016 12:31 PM, Mojca Miklavec wrote:
>>
>> Hi,
>>
>> I want to play with CNC and don't yet have any experience with CAD
>> software (nor the licence for the expensive ones) other than perhaps
>> some Blender, so I decided to try to use the super ugly route with
>> metapost -> svg -> dxf -> g-code
>> for the first time.
>>
>> I have a few questions.
>>
>> (1) I love Hans' shortcuts in metafun, but I seem to remember that things
>> like
>> input metafun;
>> or perhaps
>> input mp-tool;
>> used to work, so that I don't have to remember to use
>> mpost -mem=metafun my-drawings.mp
>> when compiling the graphics.
>>
>> Did the method with "input" ever work (or is it supposed to work)? Now
>> I'm getting a bunch of weird errors.
>> I would love to specify everything in the source file and then just
>> call mpost. If that doesn't work, that's fine, I can still add
>> "-mem=metafun", but ...
>
>
> input metafun.mpiv ;

How should one properly compile that file then to get the SVG?

Using just "mpost something.mp" doesn't work that way.

>> (2) I guess that using "raw metapost" is the only sane way to generate
>> SVG. If I use metapost inside ConTeXt that's probably not going to
>> work, right?
>>
>> (3) Is there any way to convince the SVG output mode to generate something
>> like
>> 
>> rather than
>> 
>> because the program I use to convert SVG to DXF has troubles
>> interpreting "points" properly. I read somewhere that they assume 90
>> points per inch because that's Inkskape's default.
>
> why not just
>
> \startMPpage
>   whatever you want
> \stopMPpage
>
> and then use mudraw (mutools) to go from pdf to svg (that's what i do when i
> need svg)

Given that metapost supports SVG natively I imagined that it would
produce a simpler/cleaner output. Thanks a lot for the suggestion,
I'll test it.

It turned out that the (opensource) tools I used for converting SVG
into DXF gives very weird result, so I have to change the other parts
of the "toolchain" as well.

Nevertheless, the question about whether one could convince MP to
output true units in cm/mm/in.

Mojca
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Italic in margins and footntes

[Pablo Rodriguez]

On 06/29/2016 06:06 PM, Jean-Pierre Delange wrote:
> 
> Dear ConTeXt wizards,
> 
> I am currently writing a course. I need some notes in the left
> margin. I have written this in the preamble :
> 
> \setuppapersize[A4]
> \setuplanguage[fr]
> \setuplayout [backspace=40mm]
> \setuppagenumbering[location={header,inright}]
> \setupmargindata[inmargin][location=left]
> \setupmargindata[inmargin][style={\switchtobodyfont[ss,10pt]}]
> \setupbodyfontenvironment[default][em=italic]
> \definefallbackfamily [mainface] [serif] [New Athena Unicode] 
> [preset=range:greek]% for some words in greek
> \definefontfamily [mainface] [serif] [GFS Didot]
> \setupbodyfont[mainface]
> \setupindenting[1.5em]
> \setupindenting[yes]
> \setupframedtexts[][left,10pt]
> \starttext
> 
> A problem occurs : while some words are well printed in italics in
> the body text (and in footnotes), this is not the case in the left margin
> with this code : \inmargin[][align=middle]{Cf. Platon, {\em Timée}, 29b.}

Hi Jean-Pierre,

you have to define a sans font after the serif font, such as in:

  \definefontfamily [mainface] [sans] [GFS Neohellenic]

BTW, latest beta versions require force=yes in \definefallbackfamily.

Just out of curiosity, do you plan to post the resulting PDF file online?

I hope it helps,


Pablo
-- 
http://www.ousia.tk
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

[NTG-context] Italic in margins and footntes

[Jean-Pierre Delange]

Dear ConTeXt wizards,

I am currently writing a course. I need some notes in the left margin. I have 
written this in the preamble :

\setuppapersize[A4]
\setuplanguage[fr]
\setuplayout [backspace=40mm]
\setuppagenumbering[location={header,inright}]
\setupmargindata[inmargin][location=left]
\setupmargindata[inmargin][style={\switchtobodyfont[ss,10pt]}]
\setupbodyfontenvironment[default][em=italic]
\definefallbackfamily [mainface] [serif] [New Athena Unicode] 
[preset=range:greek]% for some words in greek
\definefontfamily [mainface] [serif] [GFS Didot]
\setupbodyfont[mainface]
\setupindenting[1.5em]
\setupindenting[yes]
\setupframedtexts[][left,10pt]
\starttext

 A problem occurs : while some words are well printed in italics in the body 
text (and in footnotes), this is not the case in the left margin with this code 
:
\inmargin[][align=middle]{Cf. Platon, {\em Timée}, 29b.}

Thanks for your help !
JP

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] crop marks

[Thomas Fehige]

Thanks Wolfgang and Thomas, that was it.

Now, what if I want crop marks only outside the printed area? As it is 
now, they appear also where the cutting lines cross each other between 
the single "pages". That way they'll end up on either the one or the 
other of the adjacent pages, maybe half a line on both, depending on how 
more or less precise printer and cutting alignments work.


Thanks -- Thomas

Am 29.06.2016 um 12:37 schrieb Thomas A. Schmitz:



On 29 Jun 2016, at 12:14, Thomas Fehige  wrote:

\definepapersize[Labelpaper][width=95mm,height=90mm]
\setuppapersize[Labelpaper][A4,portrait]

\setuplayout[
backspace=3mm,
margin=0mm,
topspace=3mm,
header=0mm,
footer=0mm,
width=89mm,
height=84mm,
nx=2,
ny=3,
location=middle,
marking=on   % according to the wiki,
 % this should show the crop marks
]

\showframe% not for the final printing of course

\starttext
~ % Dummy text, I'll work with background layers.
\stoptext


Either put a comma after your last assignment marking=on, or move the closing 
bracket right after this assignment.

Thomas
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] crop marks

[Thomas Fehige]

Thanks Wolfgang and Thomas, that was it.

Now, what if I want crop marks only outside the printed area? As it is 
now, they appear also where the cutting lines cross each other between 
the single "pages". That way they'll end up on either the one or the 
other of the adjacent pages, maybe half a line on both, depending on how 
more or less precise printer and cutting alignments work.


Thanks -- Thomas

Am 29.06.2016 um 12:37 schrieb Thomas A. Schmitz:



On 29 Jun 2016, at 12:14, Thomas Fehige  wrote:

\definepapersize[Labelpaper][width=95mm,height=90mm]
\setuppapersize[Labelpaper][A4,portrait]

\setuplayout[
backspace=3mm,
margin=0mm,
topspace=3mm,
header=0mm,
footer=0mm,
width=89mm,
height=84mm,
nx=2,
ny=3,
location=middle,
marking=on   % according to the wiki,
 % this should show the crop marks
]

\showframe% not for the final printing of course

\starttext
~ % Dummy text, I'll work with background layers.
\stoptext


Either put a comma after your last assignment marking=on, or move the closing 
bracket right after this assignment.

Thomas
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Creating SVG: using MetaFun, exporting proper units, conversion to DXF

[Hans Hagen]

On 6/29/2016 12:31 PM, Mojca Miklavec wrote:

Hi,

I want to play with CNC and don't yet have any experience with CAD
software (nor the licence for the expensive ones) other than perhaps
some Blender, so I decided to try to use the super ugly route with
metapost -> svg -> dxf -> g-code
for the first time.

I have a few questions.

(1) I love Hans' shortcuts in metafun, but I seem to remember that things like
input metafun;
or perhaps
input mp-tool;
used to work, so that I don't have to remember to use
mpost -mem=metafun my-drawings.mp
when compiling the graphics.

Did the method with "input" ever work (or is it supposed to work)? Now
I'm getting a bunch of weird errors.
I would love to specify everything in the source file and then just
call mpost. If that doesn't work, that's fine, I can still add
"-mem=metafun", but ...


input metafun.mpiv ;


(2) I guess that using "raw metapost" is the only sane way to generate
SVG. If I use metapost inside ConTeXt that's probably not going to
work, right?

(3) Is there any way to convince the SVG output mode to generate something like

rather than

because the program I use to convert SVG to DXF has troubles
interpreting "points" properly. I read somewhere that they assume 90
points per inch because that's Inkskape's default.


why not just

\startMPpage
  whatever you want
\stopMPpage

and then use mudraw (mutools) to go from pdf to svg (that's what i do 
when i need svg)



(4) Does anyone have a better proposal for conversion into DXF (or
G-code)? I'm currently playing with FreeCAD and I've seen some
tutorials showing that AutoCAD can open PDF directly, but I don't want
to buy AudoCAD just for the sake of converting files.

(Not to mention that FreeCAD's SVG importer crashes when reading
output from MetaPost unless I manually remove parts of the SVG, but
that's an unrelated problem that I'm somehow able to overcome.)

Thank you,
Mojca
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___




--

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] smallcaps

[Wolfgang Schuster]

Meer, Hans van der 
29. Juni 2016 um 11:26
Thanks.

For those who are curious as to how I became confused about the 
uppercase-lowercase for smallcaps: look at session "803 Typography and 
Fonts" in Apple's WWDC2016 conference, just after 23 minutes and you 
will understand.
The following two tables contain the content of the relevant slides 
where he explains the effects from smcp (create small caps from 
lowercase letters) and c2sc (create small caps from uppercase letters).


\definefontfeature[f:smcp][smcp=yes]
\definefontfeature[f:c2sc][c2sc=yes]

\setupbodyfont[pagella]

\starttext

\subject{Small Caps from Uppercase}

\starttabulate[|l|lf{\feature[+][f:c2sc]}|]
\NC SAN FRANCISCO \NC SAN FRANCISCO \NC\NR
\NC San Francisco \NC San Francisco \NC\NR
\NC san francisco \NC san francisco \NC\NR
\stoptabulate

\subject{Small Caps from Lowercase}

\starttabulate[|l|lf{\feature[+][f:smcp]}|]
\NC SAN FRANCISCO \NC SAN FRANCISCO \NC\NR
\NC San Francisco \NC San Francisco \NC\NR
\NC san francisco \NC san francisco \NC\NR
\stoptabulate

\stoptext

Wolfgang
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] smallcaps

[Alan Bowen]

Hans—

Try “ABC {\sc abc}”.

Alan

On Wed, Jun 29, 2016 at 4:05 AM, dr. Hans van der Meer 
wrote:

> I do not understand the behaviour of the \sc macro. I thought smallcaps
> would turn out to be smaller than capitals. But I see no difference between
> them except a subtle difference in letterspacing. Am I doing something
> wrong here?
>
> Hans van der Meer
>
> Minimal example and output:
>
> \setuppapersize[A5][A5]
> \starttext
> \setupbodyfont[lmodern]
> lmodern: uppercase  smallcaps\blank
> \setupbodyfont[cambria]
> cambria: uppercase  smallcaps\blank
> \LuaTeX-version=0.\the\luatexversion\crlf
> \ConTeXt-version=\contextversion\crlf
> \stoptext
>
>
>
>
>
>
>
>
> ___
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
>
> ___
>
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] smallcaps

[Wolfgang Schuster]

dr. Hans van der Meer 
29. Juni 2016 um 12:39

The above issue being solved, I guess there is something else in my 
setup not being as it should be.

Because the code:

\starttext
\setupbodyfont[lucidaot]
{\sc abc}
\stoptext

Does give me abc in smallcaps, but placing the \setupbodyfont before 
the \starttext surprisingly does not.


\setupbodyfont[lucidaot]
\starttext
{\sc abc}
\stoptext

Changing the lucidaot call for cambria or lmodern gives the expected 
coorect behaviour.
So I guess there is something amiss with how I did setup the lucida 
font in my system.
I bought the lucida opentype font and installed my TeX trees as 
follows. The split between the ConTeXt directory and the one for my 
local files facilitates downloading new beta versions.


~home\TeX\texmf\
fonts
opentype
bh
lucidaot
LucidaBlackletterOT.otf .. LucidaSansTypewriterOT.otf
tex
context
user (my own modules)

~home\Applications\TeX-programs\
context
tex
link to the above texmf
further as downloaded from the beta

Strange thing furthermore is that changing the name of the 
lucidaot-directory in the texmf-tree does not seem to make any 
difference, not in any case when I execute "mtxrun --script font 
--reload --force" and afterwards "mtxrun --script context --make".


So I guess there are some things I did not right. Can that be spotted 
from the information given here?
The typescript for Lucida Bright OT doesn’t set a font (or applies the 
smallcaps feature) to the \sc font switch.


To get small capitals you can now activate the "smcp" or "c2sc" features 
or you create your own typeface (the \definefontfamily command always 
sets a font for the \sc switch).


\definefontfamily[lucidaopentype][rm][Lucida Bright OT]
\definefontfamily[lucidaopentype][ss][Lucida Sans OT]
\definefontfamily[lucidaopentype][tt][Lucida Sans Typewriter OT]
\definefontfamily[lucidaopentype][mm][Lucida Bright Math OT]

\setupbodyfont[lucidaopentype]

\starttext

{\rm\tf Upright, \it Italic, \bf Bold, \bi BoldItalic and \sc SmallCaps}

{\ss\tf Upright, \it Italic, \bf Bold, \bi BoldItalic and \sc SmallCaps}

{\tt\tf Upright, \it Italic, \bf Bold, \bi BoldItalic and \sc SmallCaps}

\stoptext

Wolfgang
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] smallcaps

[dr. Hans van der Meer]

> On 29 Jun 2016, at 10:05, dr. Hans van der Meer  wrote:
> 
> I do not understand the behaviour of the \sc macro. I thought smallcaps would 
> turn out to be smaller than capitals. But I see no difference between them 
> except a subtle difference in letterspacing. Am I doing something wrong here?
> 
> Hans van der Meer
> 

The above issue being solved, I guess there is something else in my setup not 
being as it should be.
Because the code:

\starttext
\setupbodyfont[lucidaot]
{\sc abc}
\stoptext

Does give me abc in smallcaps, but placing the \setupbodyfont before the 
\starttext surprisingly does not.

\setupbodyfont[lucidaot]
\starttext
{\sc abc}
\stoptext

Changing the lucidaot call for cambria or lmodern gives the expected coorect 
behaviour.
So I guess there is something amiss with how I did setup the lucida font in my 
system.
I bought the lucida opentype font and installed my TeX trees as follows. The 
split between the ConTeXt directory and the one for my local files facilitates 
downloading new beta versions.

~home\TeX\texmf\
  fonts
opentype
  bh
lucidaot
  LucidaBlackletterOT.otf .. LucidaSansTypewriterOT.otf
  tex
context
  user (my own modules)

~home\Applications\TeX-programs\
context
  tex
link to the above texmf
further as downloaded from the beta

Strange thing furthermore is that changing the name of the lucidaot-directory 
in the texmf-tree does not seem to make any difference, not in any case when I 
execute "mtxrun --script font --reload --force" and afterwards "mtxrun --script 
context --make".

So I guess there are some things I did not right. Can that be spotted from the 
information given here?

Hans van der Meer


 

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] crop marks

[Thomas A. Schmitz]

> On 29 Jun 2016, at 12:14, Thomas Fehige  wrote:
> 
> \definepapersize[Labelpaper][width=95mm,height=90mm]
> \setuppapersize[Labelpaper][A4,portrait]
> 
> \setuplayout[
>   backspace=3mm,
>   margin=0mm,
>   topspace=3mm,
>   header=0mm,
>   footer=0mm,
>   width=89mm,
>   height=84mm,
>   nx=2,
>   ny=3,
>   location=middle,
>   marking=on   % according to the wiki,
> % this should show the crop marks
> ]
> 
> \showframe% not for the final printing of course
> 
> \starttext
> ~ % Dummy text, I'll work with background layers.
> \stoptext

Either put a comma after your last assignment marking=on, or move the closing 
bracket right after this assignment. 

Thomas
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] crop marks

[Wolfgang Schuster]

Thomas Fehige 
29. Juni 2016 um 12:14
I wonder how I can get crop marks to work. This is what I have, but 
they don't show:


%=== MWE =

\definepapersize[Labelpaper][width=95mm,height=90mm]
\setuppapersize[Labelpaper][A4,portrait]

\setuplayout[
backspace=3mm,
margin=0mm,
topspace=3mm,
header=0mm,
footer=0mm,
width=89mm,
height=84mm,
nx=2,
ny=3,
location=middle,
marking=on   % according to the wiki,
You need a "," after "on", otherwise context uses the following spaces 
as part of the value and it sees "on ".


Wolfgang
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

[NTG-context] Creating SVG: using MetaFun, exporting proper units, conversion to DXF

[Mojca Miklavec]

Hi,

I want to play with CNC and don't yet have any experience with CAD
software (nor the licence for the expensive ones) other than perhaps
some Blender, so I decided to try to use the super ugly route with
metapost -> svg -> dxf -> g-code
for the first time.

I have a few questions.

(1) I love Hans' shortcuts in metafun, but I seem to remember that things like
input metafun;
or perhaps
input mp-tool;
used to work, so that I don't have to remember to use
mpost -mem=metafun my-drawings.mp
when compiling the graphics.

Did the method with "input" ever work (or is it supposed to work)? Now
I'm getting a bunch of weird errors.
I would love to specify everything in the source file and then just
call mpost. If that doesn't work, that's fine, I can still add
"-mem=metafun", but ...

(2) I guess that using "raw metapost" is the only sane way to generate
SVG. If I use metapost inside ConTeXt that's probably not going to
work, right?

(3) Is there any way to convince the SVG output mode to generate something like

rather than

because the program I use to convert SVG to DXF has troubles
interpreting "points" properly. I read somewhere that they assume 90
points per inch because that's Inkskape's default.

(4) Does anyone have a better proposal for conversion into DXF (or
G-code)? I'm currently playing with FreeCAD and I've seen some
tutorials showing that AutoCAD can open PDF directly, but I don't want
to buy AudoCAD just for the sake of converting files.

(Not to mention that FreeCAD's SVG importer crashes when reading
output from MetaPost unless I manually remove parts of the SVG, but
that's an unrelated problem that I'm somehow able to overcome.)

Thank you,
Mojca
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

[NTG-context] crop marks

[Thomas Fehige]

I wonder how I can get crop marks to work. This is what I have, but they 
don't show:


%=== MWE =

\definepapersize[Labelpaper][width=95mm,height=90mm]
\setuppapersize[Labelpaper][A4,portrait]

\setuplayout[
backspace=3mm,
margin=0mm,
topspace=3mm,
header=0mm,
footer=0mm,
width=89mm,
height=84mm,
nx=2,
ny=3,
location=middle,
marking=on   % according to the wiki,
 % this should show the crop marks
]

\showframe% not for the final printing of course

\starttext
~ % Dummy text, I'll work with background layers.
\stoptext

%==
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] smallcaps

[Meer, Hans van der]

Thanks.

For those who are curious as to how I became confused about the 
uppercase-lowercase for smallcaps: look at session "803 Typography and Fonts" 
in Apple's WWDC2016 conference, just after 23 minutes and you will understand.

Hans van der Meer




On 29 Jun 2016, at 11:00, Wolfgang Schuster 
> wrote:

dr. Hans van der Meer

29. Juni 2016 um 10:05
I do not understand the behaviour of the \sc macro. I thought smallcaps would 
turn out to be smaller than capitals. But I see no difference between them 
except a subtle difference in letterspacing. Am I doing something wrong here?

Hans van der Meer

Minimal example and output:

\setuppapersize[A5][A5]
\starttext
\setupbodyfont[lmodern]
lmodern: uppercase  smallcaps\blank
\setupbodyfont[cambria]
cambria: uppercase  smallcaps\blank
\LuaTeX-version=0.\the\luatexversion\crlf
\ConTeXt-version=\contextversion\crlf
\stoptext
Smallcaps changes only the layout of lowercase letters but some fonts let you 
also change uppercase letters.

In the example below you can see how you can change uppercase and lowercase 
letter with the smcp and c2sc features.

\definefontfeature[f:smcp][smcp=yes]
\definefontfeature[f:c2sc][c2sc=yes]

\setupbodyfont[pagella]

\starttext

An easy and breezy Sunday morning.

{\feature[+][f:smcp]An easy and breezy Sunday morning.}

{\feature[+][f:c2sc]An easy and breezy Sunday morning.}

{\feature[+][f:c2sc,f:smcp]An easy and breezy Sunday morning.}

\stoptext

Wolfgang
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] smallcaps

[Wolfgang Schuster]

dr. Hans van der Meer 
29. Juni 2016 um 10:05
I do not understand the behaviour of the \sc macro. I thought 
smallcaps would turn out to be smaller than capitals. But I see no 
difference between them except a subtle difference in letterspacing. 
Am I doing something wrong here?


Hans van der Meer

Minimal example and output:

\setuppapersize[A5][A5]
\starttext
\setupbodyfont[lmodern]
lmodern: uppercase  smallcaps\blank
\setupbodyfont[cambria]
cambria: uppercase  smallcaps\blank
\LuaTeX-version=0.\the\luatexversion\crlf
\ConTeXt-version=\contextversion\crlf
\stoptext
Smallcaps changes only the layout of lowercase letters but some fonts 
let you also change uppercase letters.


In the example below you can see how you can change uppercase and 
lowercase letter with the smcp and c2sc features.


\definefontfeature[f:smcp][smcp=yes]
\definefontfeature[f:c2sc][c2sc=yes]

\setupbodyfont[pagella]

\starttext

An easy and breezy Sunday morning.

{\feature[+][f:smcp]An easy and breezy Sunday morning.}

{\feature[+][f:c2sc]An easy and breezy Sunday morning.}

{\feature[+][f:c2sc,f:smcp]An easy and breezy Sunday morning.}

\stoptext

Wolfgang
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] ConTeXt and LilyPond problem

[Robert Blackstone]

On 28 Jun 2016, at 14:16 , Mojca Miklavec  wrote
>> 
>> On 27 June 2016 at 16:11, Robert Blackstone wrote:
>>> Dear All,
>>> 
>>> I am trying to get the combination of ConTeXt and LilyPond working.
>>> I copied the example that I found on http://wiki.contextgarden.net/LilyPond
>>> , changing the setups a little (I don't have the font  Adobe Jenson Pro).
>>> 
>>> Processing it with mkiv from april this year and earlier produces a pdf with
>>> both zapf texts and in between the text: [[output file missing.
>>> 
>> 
>> You first need to get lilypond working from Terminal, otherwise asking
>> any other question on the ConTeXt mailing list won't really help much.
>> 
>> 
>> Mojca
> 
> Thanks Mojca,
> 
> I have tried to get lilypond working from Terminal but without success. No 
> idea why. Whatever I do Terminal replies with : cannot execute binary file.

Dear all, and in particular Mojca Miklavec and Jean-Pierre Delange, who reacted 
to my first call for help, 

I think I have solved my problem.
Somehow I managed to get Lilypond working from Terminal.  Then I placed the 
ConTeXt-example with the LilyPond filter that I tried to compile in the same 
directory als the lilypond binary. Compiling it, as usual, from TeXShop it 
still did not start LilyPond and the .pdf still had: "[[output file missing"  
where the musical example should have been.
However, compiling the file from Terminal did work.

Best regards,
Robert Blackstone







___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] smallcaps

[Mikael P. Sundqvist]

On Wed, Jun 29, 2016 at 10:05 AM, dr. Hans van der Meer
 wrote:
> I do not understand the behaviour of the \sc macro. I thought smallcaps would 
> turn out to be smaller than capitals. But I see no difference between them 
> except a subtle difference in letterspacing. Am I doing something wrong here?
>
> Hans van der Meer
>
> Minimal example and output:
>
> \setuppapersize[A5][A5]
> \starttext
> \setupbodyfont[lmodern]
> lmodern: uppercase  smallcaps\blank
> \setupbodyfont[cambria]
> cambria: uppercase  smallcaps\blank
> \LuaTeX-version=0.\the\luatexversion\crlf
> \ConTeXt-version=\contextversion\crlf
> \stoptext
>
>
>
>
>
>
>
> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___

Hi!

I think \sc ABC should give ABC in full size as it does.

Try

\sc ABCabc

/Mikael
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

[NTG-context] smallcaps

[dr. Hans van der Meer]

I do not understand the behaviour of the \sc macro. I thought smallcaps would 
turn out to be smaller than capitals. But I see no difference between them 
except a subtle difference in letterspacing. Am I doing something wrong here?

Hans van der Meer

Minimal example and output:

\setuppapersize[A5][A5]
\starttext
\setupbodyfont[lmodern]
lmodern: uppercase  smallcaps\blank
\setupbodyfont[cambria]
cambria: uppercase  smallcaps\blank
\LuaTeX-version=0.\the\luatexversion\crlf
\ConTeXt-version=\contextversion\crlf
\stoptext




smallcaps.pdf
Description: Adobe PDF document



___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___