Re: [NTG-context] context minimal problem on windows
Yes it is OK now. Both MKII and MKIV works fine. Thanks. On 3/13/2010 11:42 PM, Mojca Miklavec wrote: On Sat, Mar 13, 2010 at 11:10, Mehdi Omidali wrote: Hi, I have faced a problem during upgrade to the latest minimal. I have attached a picture that explain the problem. Is it better now? (I need to fix some hardcoded commands, but I keep postponing that for way too long.) The problem is not with binaries, but with wrong libraries that we recombine on the garden (my fault). 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 ___ ___ 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] simplefonts
On Mar 13, 2010, at 5:09 PM, Michael Saunders wrote: > > I don't understand the syntax of \starttypescript. It doesn't appear > in the manual. > It occurs twice in the "typography" document. In both cases the first > argument > appears to be the name of the typescript. In one example, there is only one > argument, and in the other example, the second argument appears to be a list > of encodings. Since everything is now utf-8, I guess that could be forgotten. > So, in your example here, I take "serif" to be the name of both typsecripts, > but > I don't know what [garamondprem] is doing. We're talking about mkiv here, so we don't need to worry about encodings (which is a confusing topic - utf8 is not a font encoding, but an input encoding; these two are not identical). A typescript file can contain a series of typeface definitions, e.g., one for serif, one for sans, one for mono, one for math, etc. hence the syntax \starttypescript [] [] > It's never spelled out, but from looking at examples of > \definefontsynonym [1][2] in the > docs, I think it means something like "what we used to call 2 we can > now call 1", i.e., > telling the machine to replace instances of "1" with "2". If this is > the case, your third > arguments above just seem to apply your features to the fonts referred > to, which makes sense. > I don't see, though, why this has to be done twice, and with an extra > layer of misdirection. > E.g., instead of: > \definefontsynonym [Garamond-Roman] [name:garamondpremierpro] > [features=myroman] > \definefontsynonym [Serif] [Garamond-Roman] [features=myroman] > why not just: > \definefontsynonym [Serif] [name:garamondpremierpro] > [features=myroman]? > > I think the purpose of the above step is to connect identifiers like > "Serif" to a qualified font file. > You could indeed write typescripts without the extra layer of abstraction. It just may make it easier if you want to mix different fonts etc. >> Finally, define your first typeface: >> >> \starttypescript [GaramondPrem] >> \definetypeface [GaramondPrem] [rm] [serif] [garamondprem] [default] >> \stoptypescript > > I think this is a typescript called GaramondPrem that contains a > typeface called GaramondPrem. It seems a little redundant that they > have the same name. You can use two different names, if you prefer. > I know that the typescripts are referred to by > \usetypescript, but I don't know where typefaces are referred to, so > maybe it's just a dummy argument. In the \usebodyfont or \switchtobodyfont commands. > The "[rm]" seems to be what links > this to the font switching command, and the "[garamondprem]" obviously > refers to both the typescripts you defined above. I don't understand > what the "[serif]" is doing. In the typography manual, Hans says, > "The third and fourth > arguments to \definetypeface are pointers to already declared font > sets; these are defined elsewhere." I think by "font set" he must > mean a typescript like garamondprem, but I don't know where the font > set (typescript?) "serif" As I said: there's at least serif, sans, mono, math > is or why two font sets need to be pointed > to. ??? > The same typography document goes on to explain the fifth > argument: > "The fifth argument to \definetypeface specifies specific font size > setups (if any), these will be covered in section ?? in the next > chapter." > This is getting scary, but I'm hoping putting "[optical]" there will > solve everything. > I don't follow. > >> Next step: defining a typeface with superior numbers for footnote references >> etc.: > >> \starttypescript [serif] [garamondpremupper] >> \definefontsynonym [GaramondPremUpper-Roman] [name:agaramondproregular] >> [features=mysup] >> \stoptypescript > >> \starttypescript [serif] [garamondpremupper] >> \definefontsynonym [Serif] [GaramondPremUpper-Roman] >> [features=mysup] >> \definefontsynonym [SerifItalic] [Serif] >> \definefontsynonym [SerifBold] [Serif] >> \definefontsynonym [SerifBoldItalic] [Serif] >> \definefontsynonym [SerifCaps] [Serif] >> \stoptypescript > > I think I follow you, up to the line: > \definefontsynonym [SerifItalic] [Serif]. > These last lines seem to say that if you're in bold or italic, that > you should still use > regular superior figures, but the font has its own bold and italic > superiors. I think > that's true of all the weight/shape/design size variations in the set. > It depends what you want to achieve. I map everything onto Serif because I do not want the superior numbers to be bold or italic, even in an italic environment. Of course, you can define something for all these variants. >> \starttypescript [GaramondPremUpper] >> \definetypeface [GaramondPremUpper] [rm] [serif] [garamondpremupper] >> [default] >> \stoptypescript > > I'm confused about how [GaramondPremUpper] and [garamondpremupper] > seem to be getting associated with [rm] and
Re: [NTG-context] context minimal problem on windows
On Sat, Mar 13, 2010 at 11:10, Mehdi Omidali wrote: > Hi, > I have faced a problem during upgrade to the latest minimal. I have attached > a picture that explain the problem. Is it better now? (I need to fix some hardcoded commands, but I keep postponing that for way too long.) The problem is not with binaries, but with wrong libraries that we recombine on the garden (my fault). 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] colored column
Am 13.03.10 18:51, schrieb Wolfgang Werners-Lucchini: So, how can I do the job? Natural tables? \setupTABLE[offset=0pt,loffset=0.25ex,roffset=0.25ex] % l|roffset requires MKIV \setupTABLE[frame=off,leftframe=on,rightframe=on] \starttext \startTABLE[color=red] \NC red \NC\NR \stopTABLE \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] Including lua files
On 2010-03-13 <17:24:27>, Wolfgang Schuster wrote: > Am 13.03.10 15:54, schrieb Philipp Gesang: > >Dear Lua Gurus, > > > >what's the preferred way of including files in Lua? > > > >When trying my module on a different machine I noticed that it fails > >because Lua's dofile() does not extend to files in the texmf tree. Thus > >I attempted to include the file with context.ctxlualoadfile() but it > >doesn't work either. > environment.loadluafile(...)? What a relief, finally I managed it: could somebody with access to the context source please add a note luat-env.lua, that filenames passed to environment.loadluafile() must have their .lua suffix stripped? This might save somebody a minor headache someday. Thanks for the help, Philipp > > 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 > ___ -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments signature.asc Description: Digital signature ___ 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] not printable pdf
On Sat, Mar 13, 2010 at 6:22 PM, R. Bastian wrote: > Hello, > > I join a minimal example (ex0.tex) > > texexec (version 6.2.1) and context (2009.10.02) > compile and the PDf is visible (xpdf and kpdf) > but it is not printable (lpr -P HP-5MP ...) printable here with my HP LaserJEt 1020 #>cupsdoprint -P HP_LaserJet_1020 -o InputSlot=Auto -o Resolution=1200x600dpi -o PageSize=A4 $1 > The same text in his Latex-form is printed (after pdflatex), so I think that > there is a bug in the PDF produced by context | texexec. I don't see anything wrong in it. -- luigi ___ 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] not printable pdf
On Sat, 13 Mar 2010 18:36:23 +0100 Wolfgang Schuster scribit: > Am 13.03.10 18:22, schrieb R. Bastian: > > Hello, > > > > I join a minimal example (ex0.tex) > > > > > > \parindent 3mm > > > \setupindenting[yes,3mm] > > \parskip 6mm > > > \setupwhitespace[6mm] > > \language[fr] > > > \language is for the local change of the language *in* the document, the > global language of the document is set with > > \mainlanguage[fr] > > \setupinterlinespace[small] > > > useless > > Wolfgang > Thanks [je vais amender l'ensemble de mes sources/ich werde alle Quelttexte korrigieren] The new PDF is compiled and is visible but it is not printed. -- René Bastian www.pythoneon.org www.musiques-rb.org http://www.soundsurvey.org.uk/ ___ 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] Dezimalkomma
> > Hallo, > > > > I must do something wrong. It is not working for me: > > > > \setupmathematics[autopunctuation=yes] > > \starttext > > $0,1$ > > \stoptext > > maybe an too old version > As I wrote, I tested on the garden. This version is current enough I thinck. 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] colored column
Hallo, can someone explain how to write a table column in color, please? The following example worked in 2006 but is not working anymore: \starttext \starttable[o1|\{C{red}|] \VL red \VL\SR \stoptable \stoptext Wolfgang Schuster posted last year the following example: \NewFormatKey W#1% {\ReadFormatKeys b{\localstartcolor[#1]\{} a{\}\localstopcolor}} \starttable[o1|W{red}c|] \VL red \VL\SR \stoptable But this results in printing '{red}' in red, not 'red'! And this variant paints the following vertical line in red too: \NewFormatKey W#1% {\ReadFormatKeys b{\localstartcolor[#1]} a{\localstopcolor}} \starttable[o1|W{red}c|] \VL red \VL\SR \stoptable So, how can I do the job? 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] not printable pdf
Am 13.03.10 18:22, schrieb R. Bastian: Hello, I join a minimal example (ex0.tex) \parindent 3mm \setupindenting[yes,3mm] \parskip 6mm \setupwhitespace[6mm] \language[fr] \language is for the local change of the language *in* the document, the global language of the document is set with \mainlanguage[fr] \setupinterlinespace[small] useless 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] simplefonts
Am 13.03.10 17:59, schrieb Andreas Harder: I've played with it, but with \TestLookup{familyname=minionpro,designsize=11pt} no fonts are found. Values are passed from to to Lua as string and the size is a number, what i do is to ask for the font only and loop where i check the size of the font. \dorecurse {\dolookupnoffound} {\dolookupgetkeyofindex{designsize}{\recurselevel}} % minsize, maxsize Fonts use a different system for the size a value of 100 stands for 10pt, 120 for 12pt etc. You should be also know that fonts are not perfect and in *many* cases fonts without optical size use '0' as value for the size. By the way, is luaTeX able to use ttc-fonts? Yes but a few fonts in snow leopard have problems. 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] not printable pdf
Hello, I join a minimal example (ex0.tex) texexec (version 6.2.1) and context (2009.10.02) compile and the PDf is visible (xpdf and kpdf) but it is not printable (lpr -P HP-5MP ...) The same text in his Latex-form is printed (after pdflatex), so I think that there is a bug in the PDF produced by context | texexec. Can you help me? -- René Bastian www.pythoneon.org www.musiques-rb.org http://www.soundsurvey.org.uk/ \enableregime[utf] \parindent 3mm \parskip 6mm \setupbodyfont[sansserif, 12pt] \definepapersize[monpapier][width=170mm,height=235mm] \setuppapersize[monpapier][monpapier] \setuplayout[textwidth=140mm, textheight=195mm, topspace=5mm, leftmargin=5mm, rightmargin=5mm, leftmargindistance=3mm] \setupheadertexts[chapter] \setuppagenumbering[alternative=doublesided,location={footer,inleft}, command=\inframed] \language[fr] \setuphead[chapter][textstyle=cap, numberstyle=bold, after={\blank\hrule\blank}] \setuphead[title][after={\blank\hrule\blank}] \def\auteur{\hfill Claude G.\blank\blank} \setupinterlinespace[small] \starttext Le gazon est un sympathique paillason doux et sec, sur ... les livres \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] simplefonts
Am 13.03.2010 um 17:17 schrieb Wolfgang Schuster: > Am 13.03.10 14:27, schrieb Andreas Harder: >> would you provide an example of how to use this information? >> > font-ini.mkiv > > %D some low level helpers > %D > %D \starttyping > %D \def\TestLookup#1% > %D {\dolookupfontbyspec{#1} > %D pattern: #1, found: \dolookupnoffound > %D\blank > %D\dorecurse {\dolookupnoffound} {% > %D \recurselevel:~\dolookupgetkeyofindex{fontname}{\recurselevel}\quad > %D}% > %D\blank} > %D > %D \TestLookup{familyname=helveticaneue} > %D \TestLookup{familyname=helveticaneue,weight=bold} > %D \TestLookup{familyname=helveticaneue,weight=bold,style=italic} > %D \stoptyping > > You can ask ConTeXt to look for a font in it's database with the keys > > - familyname (e.g. TeX Gyre Pagella or Latin Modern Roman) > - weight (normal, bold, light, medium etc.) > - style (normal, italic) > - variant (normal, smallcaps) > - fontname (e.g. texgyrepagellaregular) > - … Thank you Wolfgang! I've played with it, but with \TestLookup{familyname=minionpro,designsize=11pt} no fonts are found. By the way, is luaTeX able to use ttc-fonts? Andreas ___ 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] simplefonts
Am 13.03.10 17:09, schrieb Michael Saunders: 2. What keys and values are available for the third, and what they mean. Thank you, but by "the first two arguments", I mean 1 and 2 of: \definefontfeature [1][2][3]. For example, in \definefontfeature[smallcaps][smallcaps][script=latn] I don't know what "[smallcaps][smallcaps]" is doing. Let's start with the normal version \definefontfeature[default][liga=yes,kern=yes,tlig=yes,trep=yes] creates a list with the name 'default' (predefined by context and used by default for all fonts if not specified otherwise) with the opentype features liga (ligature), kern (kerning) and the pseudo tex features tlig (-- -> –, --- -> —) and trep (' -> ’). This feature is now applied to font in a typescript (ConTeXt system map font files to commands, e.g. when you write \bf in your document your get Times New Roman Bold). In the extended version with three arguments you copy the list from the second argument to the new list which name is given in the first argument and you can add new opentype features to the list, e.g. \definefontfeature[mine][default][onum=yes] creates the new list mine which inherits all features from default and adds onum to the list, when the name in the first and second arguments are equal you extend a already created list with additional features. 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] Including lua files
Am 13.03.10 15:54, schrieb Philipp Gesang: Dear Lua Gurus, what's the preferred way of including files in Lua? When trying my module on a different machine I noticed that it fails because Lua's dofile() does not extend to files in the texmf tree. Thus I attempted to include the file with context.ctxlualoadfile() but it doesn't work either. environment.loadluafile(...)? 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] simplefonts
Am 13.03.10 14:27, schrieb Andreas Harder: would you provide an example of how to use this information? font-ini.mkiv %D some low level helpers %D %D \starttyping %D \def\TestLookup#1% %D {\dolookupfontbyspec{#1} %D pattern: #1, found: \dolookupnoffound %D\blank %D\dorecurse {\dolookupnoffound} {% %D \recurselevel:~\dolookupgetkeyofindex{fontname}{\recurselevel}\quad %D}% %D\blank} %D %D \TestLookup{familyname=helveticaneue} %D \TestLookup{familyname=helveticaneue,weight=bold} %D \TestLookup{familyname=helveticaneue,weight=bold,style=italic} %D \stoptyping You can ask ConTeXt to look for a font in it's database with the keys - familyname (e.g. TeX Gyre Pagella or Latin Modern Roman) - weight (normal, bold, light, medium etc.) - style (normal, italic) - variant (normal, smallcaps) - fontname (e.g. texgyrepagellaregular) - ... The information in the database are not always perfect (because fonts are a mess) but I'll try to improve this in the next time. 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] simplefonts
Aditya Mahajan: > Have you read the chapter on typography in the new manual > http://context.aanhet.net/svn/contextman/context-reference/en/co-typography.pdf Yes. Several times. And I took notes. -- Hans Hagen: > > 1. What the first two arguments do. > the mode=base|node determines if we use traditional tex mechanisms > (base) or let mkiv do all work itself (node) > 2. What keys and values are available for the third, and what they mean. Thank you, but by "the first two arguments", I mean 1 and 2 of: \definefontfeature [1][2][3]. For example, in \definefontfeature[smallcaps][smallcaps][script=latn] I don't know what "[smallcaps][smallcaps]" is doing. > > 3. Once I have composed a \definefontfeature command, how do I use it > > in the text. > not in the text, only when defining fonts; although you can enable and > disable features in the running text (dynamicly) .. from the source: > % \startbuffer > % \definefontfeature[smallcaps][smallcaps][script=latn] > % \definefontfeature[oldstyle] [oldstyle] [script=latn] > % > % \definedfont[name:cambria at 15pt] > % > % Hello there {\setff{smallcaps}capped 123 \setff{oldstyle}123!}\blank > % Hello there {\addff{smallcaps}capped 123 \addff{oldstyle}123!}\blank > % Hello there {\addff{smallcaps}capped \subff{smallcaps}normal} \blank > % \stopbuffer > % > % \typebuffer \getbuffer Naturally, I don't know what any of this code means (which is why I seek a human language explanation), but I'm guessing that in \definefontfeature[oldstyle] [oldstyle] [script=latn] the first "[oldstyle]" creates a command or variable called "oldstyle", the second "[oldstyle]" relates this to something else (another command or variable, maybe a font file) which is also called "oldstyle", and the key-value pair "[script=latn]"qualifies this, selecting the only the Latin part of the second "[oldstyle]". (And, by the way, my font has Greek and Cyrillic as well---why disable oldstyle in them?) I think that leaves me with a command or variable or something called "oldstyle", which I could include in the text. My first guess would have been that it's "\oldstyle", but, later in your code snippet, I see "\setff{smallcaps}" and "\addff{smallcaps}". There's no telling what the difference is. So, I'm left guessing that \definefontfeature[oldstyle] [oldstyle] [script=latn] creates a possible argument for \setff{} and \addff{}, whatever they are. They might be the commands for font switching in the text. Since the code snippet isn't a human explanation, however, I can't tell--- I can only make wild guesses. > > 4. For example, I gathered that I needed a [default] [default] > > [...onum=yes...] to get oldstyle numerals by default, but what if I > > want to use some lining numerals here and there? > > \definefontfeature [lining] [lining] [...onum=no...] > > {\lining 123} > > doesn't do it. > lnum=yes I tried this, and \definefontfeature [lining] [lining] [lnum=yes] {\lining 123} still gives me "undefined control sequence" on \lining. I also tried {\switchtobodyfont [lining] 123}, which had no effect. > > 5. How I could use the superior and inferior shapes in my font---like > > for the footnotemarks, for example? > hm, with sups=yes,subs=yes i guess but better use \high{..} and \low{..} > as often such font features are rather limited and depend on the font I'll have to try that out (since I know which fonts have them), but: \definefontfeature [?] [?] [sups=yes,subs=yes] ? -- Thomas A. Schmitz: > This is not to disparage Wolfgang's great simplefonts module, but I learnt > setting up fonts the old-fashioned way (with typescripts), > so I will give a few explanations about this approach. Most of what you want > can be achieved easily. I have Garamond Premier myself, and this is how I set > it up: Thank you, this is very encouraging. I used to do this with otftotfm and .fd files, so it's not totally alien to me. I just need to grasp the syntax of the Context commands. I've been pouring over your example. There are a few points I still don't understand. ... > Next step: we set up the "normal" and smallcaps font: > \starttypescript [serif] [garamondprem] > \definefontsynonym [Garamond-Roman] [name:garamondpremierpro] > [features=myroman] > \definefontsynonym [Garamond-Bold] [name:garamondpremierprobold] > [features=myroman] > \definefontsynonym [Garamond-Italic] [name:garamondpremierproitalic] > [features=myroman] > \definefontsynonym [Garamond-Bold-Italic] > [name:garamondpremierprobolditalicc] [features=myroman] > \definefontsynonym [Garamond-SmallCaps] [name:garamondpremierpro] > [features=mysmcp] > \stoptypescript > > \starttypescript [serif] [garamondprem] > \definefontsynonym [Serif] [Garamond-Roman] [features=myroman] > \definefontsynonym [SerifItalic] [Garamond-Italic] [features=myroman] > \definefontsynonym [SerifBo
[NTG-context] Including lua files
Dear Lua Gurus, what's the preferred way of including files in Lua? When trying my module on a different machine I noticed that it fails because Lua's dofile() does not extend to files in the texmf tree. Thus I attempted to include the file with context.ctxlualoadfile() but it doesn't work either. Have a relaxed weekend, Philipp -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments signature.asc Description: Digital signature ___ 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] simplefonts
Am 13.03.2010 um 13:26 schrieb Wolfgang Schuster: > Am 13.03.10 13:16, schrieb Hans Hagen: >>> Fontloader already expose the size info if present, we wrote some code >>> for LaTeX that loads the best optical size automatically based on the >>> requested font size, it isn't that hard. >> sure, it's no big deal to support it, but as said .. i don't have such fonts >> (and i don't want illegal copies on my machine) so i haven't looked into it; >> also, for the few cases that are there, typescripts can cover it (if it >> concerns different font files) .. if it crosses out paths wolfgang and i can >> add it to the mkiv heuristics handler > ConTeXt already has the relevant information (designsize, minsize and maxsize > in the font database) and i have a few test files which use them. Hello Wolfgang, would you provide an example of how to use this information? Thank you in advance Andreas ___ 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 minimal problem on windows
Yes they are the same problem. I replaced luatex.dll with of the latest version (.51) with the previous one (.50) and the problem disappeared, though the problem still exists for pdftex.dll. It seems that something is wrong with compilation of luatex and pdftex on windows. MO On 3/13/2010 4:06 PM, Helmut Schwertner wrote: Am 13.03.2010 11:10, schrieb Mehdi Omidali: Hi, I have faced a problem during upgrade to the latest minimal. I have attached a picture that explain the problem. MO Hello, it seems to be the same problem how on my windows (win7 64 bit and winxp 32 bit). On Wed, Mar 10, 2010 at 17:00, Helmut Schwertner wrote: > > Hello, > > I'm using contextminimals with win7 64bit. Since a few days i get the > > following two messages when I try to update or to do a new install of > > contextminimals. > > The message (error report) for two times is: > > > > pdftex.exe – Einsprungpunkt nicht gefunden > > > > Der Prozedureinsprungpunkt „sfseek64“ wurde in der DLL „kpathsearch510.dll“ > > nicht gefunden. > > > > Context (mkiv) is working ; texexec (mkii) is broken. > > > > What can I do? > >I need to ask Akira - I suspect that there are two incompatible > >versions of the library with the same name. > > Mojca Thanks, Helmut eMail: helmut.schwert...@gmx.de ___ 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] context minimal problem on windows
Am 13.03.2010 11:10, schrieb Mehdi Omidali: Hi, I have faced a problem during upgrade to the latest minimal. I have attached a picture that explain the problem. MO Hello, it seems to be the same problem how on my windows (win7 64 bit and winxp 32 bit). On Wed, Mar 10, 2010 at 17:00, Helmut Schwertner wrote: > > Hello, > > I'm using contextminimals with win7 64bit. Since a few days i get the > > following two messages when I try to update or to do a new install of > > contextminimals. > > The message (error report) for two times is: > > > > pdftex.exe – Einsprungpunkt nicht gefunden > > > > Der Prozedureinsprungpunkt „sfseek64“ wurde in der DLL „kpathsearch510.dll“ > > nicht gefunden. > > > > Context (mkiv) is working ; texexec (mkii) is broken. > > > > What can I do? > >I need to ask Akira - I suspect that there are two incompatible > >versions of the library with the same name. > > Mojca Thanks, Helmut eMail: helmut.schwert...@gmx.de ___ 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] simplefonts
On 13-3-2010 13:26, Wolfgang Schuster wrote: Am 13.03.10 13:16, schrieb Hans Hagen: Fontloader already expose the size info if present, we wrote some code for LaTeX that loads the best optical size automatically based on the requested font size, it isn't that hard. sure, it's no big deal to support it, but as said .. i don't have such fonts (and i don't want illegal copies on my machine) so i haven't looked into it; also, for the few cases that are there, typescripts can cover it (if it concerns different font files) .. if it crosses out paths wolfgang and i can add it to the mkiv heuristics handler ConTeXt already has the relevant information (designsize, minsize and maxsize in the font database) and i have a few test files which use them. ok, so we take care of it already (sort of) 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 - ___ 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] simplefonts
Am 13.03.10 13:16, schrieb Hans Hagen: Fontloader already expose the size info if present, we wrote some code for LaTeX that loads the best optical size automatically based on the requested font size, it isn't that hard. sure, it's no big deal to support it, but as said .. i don't have such fonts (and i don't want illegal copies on my machine) so i haven't looked into it; also, for the few cases that are there, typescripts can cover it (if it concerns different font files) .. if it crosses out paths wolfgang and i can add it to the mkiv heuristics handler ConTeXt already has the relevant information (designsize, minsize and maxsize in the font database) and i have a few test files which use them. 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] streams
On 12-3-2010 23:43, Philipp Gesang wrote: Good evening, Hans! On 2010-03-11<19:37:48>, Hans Hagen wrote: On 11-3-2010 11:47, Philipp Gesang wrote: Hello all, the streams module could help typesetting my current work but all the examples fail in mkiv. (The output from mkii is impressive, though.) The snippets I tried are from the comments of http://source.contextgarden.net/tex/context/base/m-streams.tex and another one from the wiki http://wiki.contextgarden.net/Columns#Streams Here are the ConTeXt error messages, seems that \FlushLeftAndRight is the culprit but I don't really know where to start looking because the command sequences are not legible in this truncated form. (Is there some switch that prevents ConTeXt from shortening the names at least in the log file?) i've fixed that bug but streams wll be redone inb mkiv from scratch anyway Are you sure this worked for you? I get another error with today's beta: you need to remove the \endinput which i added as i'm playing with a new implementation and don't want conflicting code 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 - ___ 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] simplefonts
On 13-3-2010 7:19, Khaled Hosny wrote: On Sat, Mar 13, 2010 at 06:35:30AM +0100, Wolfgang Schuster wrote: Am 12.03.10 23:29, schrieb Hans Hagen: ok, i was thinking of embedded optical sized (i.e. one font file that has several sizes) Is there anything besides different sizes in opentype math fonts and the ruby feature in cjk fonts? OpenType fonts can set a size feature, setting the optical size of the font and the size range in which it is used, so different font files in the same family with different optical sizes can be set (like LM). http://www.microsoft.com/typography/otspec/features_pt.htm#size But I don't think there is support for a single font file with different optical sizes. ah Fontloader already expose the size info if present, we wrote some code for LaTeX that loads the best optical size automatically based on the requested font size, it isn't that hard. sure, it's no big deal to support it, but as said .. i don't have such fonts (and i don't want illegal copies on my machine) so i haven't looked into it; also, for the few cases that are there, typescripts can cover it (if it concerns different font files) .. if it crosses out paths wolfgang and i can add it to the mkiv heuristics handler 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 - ___ 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] context minimal problem on windows
Hi, I have faced a problem during upgrade to the latest minimal. I have attached a picture that explain the problem. MO <>___ 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 ___