Is there a short, simple guide somewhere that shows how to use TTF and OTF fonts in Context? I downloaded the new Fonts chapter but it goes deep into the weeds on typescripts etc. I am looking for a method that allows me to do in Context what I can already do in most other DTP programs: simply designate for use a font or font family that exists in /usr/share/fonts without typescripts, complex and confusing aliasing schemes or tfm files. -- John Culleton Create Book Covers with Scribus: http://www.booklocker.com/p/books/4055.html Typesetting and indexing http://wexfordpress.com book sales http://wexfordpress.net Free barcode: http://www.tux.org/~milgram/bookland/
John Culleton
Is there a short, simple guide somewhere that shows how to use TTF and OTF fonts in Context? I downloaded the new Fonts chapter but it goes deep into the weeds on typescripts etc. I am looking for a method that allows me to do in Context what I can already do in most other DTP programs: simply designate for use a font or font family that exists in /usr/share/fonts without typescripts, complex and confusing aliasing schemes or tfm files.
John Culleton
writes: Is there a short, simple guide somewhere that shows how to use TTF and OTF fonts in Context? I downloaded the new Fonts chapter but it goes deep into the weeds on typescripts etc. I am looking for a method that allows me to do in Context what I can already do in most other DTP programs: simply designate for use a font or font family that exists in /usr/share/fonts without typescripts, complex and confusing aliasing schemes or tfm files.
http://wiki.contextgarden.net/Fonts_in_LuaTex OK I used this guide and have access to one of the fonts in /usr/share/fonts/Type1 but not the rest. Courier is in the database. AGaramond is not. The wiki paper seems to state that Type1 fonts should be available via the database and \simplefonts. AGaramond is in
On Friday 28 January 2011 16:52:57 Marco Pessotto wrote: the /usr/share/fonts/Type1 directory and is listed in the /usr/share/fonts/Type1/fonts.dir file. It does not show up in the mtxrun generated data base. set shows the following entry: OSFONTDIR='/usr/share/fonts;/home/safe/.fonts' Now if Type1 isn't included the font data base yet I can be cool with that. But in that case the wiki needs to be corrected. -- John Culleton Create Book Covers with Scribus: http://www.booklocker.com/p/books/4055.html Typesetting and indexing http://wexfordpress.com book sales http://wexfordpress.net Free barcode: http://www.tux.org/~milgram/bookland/
On Friday 28 January 2011 16:52:57 Marco Pessotto wrote:
John Culleton
writes: Is there a short, simple guide somewhere that shows how to use TTF and OTF fonts in Context? I downloaded the new Fonts chapter but it goes deep into the weeds on typescripts etc. I am looking for a method that allows me to do in Context what I can already do in most other DTP programs: simply designate for use a font or font family that exists in /usr/share/fonts without typescripts, complex and confusing aliasing schemes or tfm files.
OK I used this guide and have access to one of the fonts in /usr/share/fonts/Type1 but not the rest. Courier is in the database. AGaramond is not. The wiki paper seems to state that Type1 fonts should be available via the database and \simplefonts. AGaramond is in the /usr/share/fonts/Type1 directory and is listed in the /usr/share/fonts/Type1/fonts.dir file. It does not show up in the mtxrun generated data base.
set shows the following entry: OSFONTDIR='/usr/share/fonts;/home/safe/.fonts'
Now if Type1 isn't included the font data base yet I can be cool with that. But in that case the wiki needs to be corrected. I have tried various fonts, including charterbt, calibri (ttf) and so on. I get the called-for font but the sequences for curly double quotes, in use since Ramses II, give me either two back ticks followed by two forward ticks, (calibri) or two back ticks followed by an inch symbol (charterbt). So this defect is not limited to one font. My
On Saturday 29 January 2011 11:53:20 John Culleton wrote: main file is as follows: \input macros.tex \usemodule [simplefonts] \setmainfont [calibri] \starttext \input body.tex \stoptext and macros.tex looks like this: \setupoutput[pdftex] \definepapersize[bok][width=7.0in,height=10.0in] %\setuppapersize[bok][letter] \setuppapersize[bok][bok] \setuplayout[location=middle,marking=on]% \setupwhitespace[line] \setuptyping[style=small] Anyone else have this problem? -- John Culleton Create Book Covers with Scribus: http://www.booklocker.com/p/books/4055.html Typesetting and indexing http://wexfordpress.com book sales http://wexfordpress.net Free barcode: http://www.tux.org/~milgram/bookland/
Am 30.01.2011 um 16:34 schrieb John Culleton:
I have tried various fonts, including charterbt, calibri (ttf) and so on. I get the called-for font but the sequences for curly double quotes, in use since Ramses II, give me either two back ticks followed by two forward ticks, (calibri) or two back ticks followed by an inch symbol (charterbt). So this defect is not limited to one font. My main file is as follows:
\input macros.tex
\environment macros
\usemodule [simplefonts] \setmainfont [calibri] \starttext \input body.tex \stoptext
and macros.tex looks like this:
\startenvironment macros
\setupoutput[pdftex] \definepapersize[bok][width=7.0in,height=10.0in] %\setuppapersize[bok][letter] \setuppapersize[bok][bok] \setuplayout[location=middle,marking=on]% \setupwhitespace[line] \setuptyping[style=small]
\stopenvironment
Anyone else have this problem?
Learn to make a minimal *working* example, this works: \usemodule[simplefonts] \setmainfont[Calibri] \starttext “quoted text” \stoptext Wolfgang
On Sunday 30 January 2011 10:52:10 Wolfgang Schuster wrote:
Am 30.01.2011 um 16:34 schrieb John Culleton:
I have tried various fonts, including charterbt, calibri (ttf) and so on. I get the called-for font but the sequences for curly double quotes, in use since Ramses II, give me either two back ticks followed by two forward ticks, (calibri) or two back ticks followed by an inch symbol (charterbt). So this defect is not limited to one font. My main file is as follows:
\input macros.tex
\environment macros
\usemodule [simplefonts] \setmainfont [calibri] \starttext \input body.tex \stoptext
and macros.tex looks like this:
\startenvironment macros
\setupoutput[pdftex] \definepapersize[bok][width=7.0in,height=10.0in] %\setuppapersize[bok][letter] \setuppapersize[bok][bok] \setuplayout[location=middle,marking=on]% \setupwhitespace[line] \setuptyping[style=small]
\stopenvironment
Anyone else have this problem?
Learn to make a minimal *working* example, this works:
\usemodule[simplefonts] \setmainfont[Calibri] \starttext “quoted text” \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 ___________________________________________________________________ ________________
Thanks for your reply. Are you telling me that \input foo no longer works the way it used to? Let me simplify the example: ----------------------------------------------------------- \setupoutput[pdftex] \definepapersize[bok][width=7.0in,height=10.0in] \setuppapersize[bok][bok] \usemodule [simplefonts] \setmainfont [georgia] \starttext Here is ``foo''. \stoptext --------------------------------- I still get the same wrong results. In a ttf font like georgia the close quote looks OK but the open quote are two left tick marks. In Bitstream Charter the close quote is the inch sign and the open quote is again two left tick marks. So my original question remains: Why do the double quote codes not work as they have since the days of plain tex? -- John Culleton Create Book Covers with Scribus: http://www.booklocker.com/p/books/4055.html Typesetting and indexing http://wexfordpress.com book sales http://wexfordpress.net Free barcode: http://www.tux.org/~milgram/bookland/
Am 30.01.2011 um 17:29 schrieb John Culleton:
Thanks for your reply. Are you telling me that \input foo no longer works the way it used to?
\input works but \environment is the “ConTeXt Way” to load your personal settings for a document, environment prevents also multiple loading of the file when you use context’s document structure.
Let me simplify the example: ----------------------------------------------------------- \setupoutput[pdftex]
simplefonts is mkiv only, so remove this or don’t use simplefonts
\definepapersize[bok][width=7.0in,height=10.0in] \setuppapersize[bok][bok] \usemodule [simplefonts] \setmainfont [georgia] \starttext Here is ``foo''. \stoptext --------------------------------- I still get the same wrong results. In a ttf font like georgia the close quote looks OK but the open quote are two left tick marks. In Bitstream Charter the close quote is the inch sign and the open quote is again two left tick marks. So my original question remains: Why do the double quote codes not work as they have since the days of plain tex?
Use “…” or \quotation{…}, we have 2011 and Unicode is available since years. Wolfgang
On Sunday 30 January 2011 16:52:55 Wolfgang Schuster wrote:
Am 30.01.2011 um 17:29 schrieb John Culleton:
Thanks for your reply. Are you telling me that \input foo no longer works the way it used to?
\input works but \environment is the “ConTeXt Way” to load your personal settings for a document, environment prevents also multiple loading of the file when you use context’s document structure.
Let me simplify the example: ----------------------------------------------------------- \setupoutput[pdftex]
simplefonts is mkiv only, so remove this or don’t use simplefonts
\definepapersize[bok][width=7.0in,height=10.0in] \setuppapersize[bok][bok] \usemodule [simplefonts] \setmainfont [georgia] \starttext Here is ``foo''. \stoptext --------------------------------- I still get the same wrong results. In a ttf font like georgia the close quote looks OK but the open quote are two left tick marks. In Bitstream Charter the close quote is the inch sign and the open quote is again two left tick marks. So my original question remains: Why do the double quote codes not work as they have since the days of plain tex?
Use “…” or \quotation{…}, we have 2011 and Unicode is available since years.
Wolfgang
___________________________________________________________________ ________________
\quotation{} works, but nothing else does. It is not clear how one sets the main font size. Is this correct? \setmainfont[charterbt][size=11pt] ? -- John Culleton Create Book Covers with Scribus: http://www.booklocker.com/p/books/4055.html Typesetting and indexing http://wexfordpress.com book sales http://wexfordpress.net Free barcode: http://www.tux.org/~milgram/bookland/
Am 31.01.2011 um 21:45 schrieb John Culleton:
\quotation{} works, but nothing else does.
just write the quotes: '“' and '”'
It is not clear how one sets the main font size. Is this correct? \setmainfont[charterbt][size=11pt]
\setupsimplefonts[size=11pt] or \setupbodyfont[11pt] Wolfgang
On Sun, Jan 30, 2011 at 17:29, John Culleton wrote:
Here is ``foo''.
See Wolfgang's answer, I just wanted to add a note. This syntax has deliberately been disabled. In MKII it was a hack implemented in fonts. In XeLaTeX you need mapping=tex-text to get that behaviour (which adds some non-existant features to the font), but that way you won't be able to get "breve" or "plain backtick" in your final document, so it had to be disabled. Mojca
* John Culleton
Is there a short, simple guide somewhere that shows how to use TTF and OTF fonts in Context? I downloaded the new Fonts chapter but it goes deep into the weeds on typescripts etc. I am looking for a method that allows me to do in Context what I can already do in most other DTP programs: simply designate for use a font or font family that exists in /usr/share/fonts without typescripts, complex and confusing aliasing schemes or tfm files.
The Simplefont module by Wolfgang Schuster is very good for my (not highly demanding) purposes. Certainly it is intended to do just what you describe. -- David
Am 29.01.2011 um 06:42 schrieb David Rogers:
* John Culleton
[2011-01-28 16:39]: Is there a short, simple guide somewhere that shows how to use TTF and OTF fonts in Context? I downloaded the new Fonts chapter but it goes deep into the weeds on typescripts etc. I am looking for a method that allows me to do in Context what I can already do in most other DTP programs: simply designate for use a font or font family that exists in /usr/share/fonts without typescripts, complex and confusing aliasing schemes or tfm files.
The Simplefont module by Wolfgang Schuster is very good for my (not highly demanding) purposes. Certainly it is intended to do just what you describe.
Or you use \definetypeface and specserif, specsans and specmono, e.g. \definetypeface[mainface][rm][specserif][Times New Roman][default] \definetypeface[mainface][ss][specsans] [Arial] [default] \definetypeface[mainface][tt][specmono] [Courier] [default] \definetypeface[mainface][mm][math] [times] [default] \setupbodyfont[mainface] \starttext … \stoptext Wolfgang
On Sat, Jan 29, 2011 at 9:55 AM, Wolfgang Schuster < schuster.wolfgang@googlemail.com> wrote:
Am 29.01.2011 um 06:42 schrieb David Rogers:
* John Culleton
[2011-01-28 16:39]: Is there a short, simple guide somewhere that shows how to use TTF and OTF fonts in Context? I downloaded the new Fonts chapter but it goes deep into the weeds on typescripts etc. I am looking for a method that allows me to do in Context what I can already do in most other DTP programs: simply designate for use a font or font family that exists in /usr/share/fonts without typescripts, complex and confusing aliasing schemes or tfm files.
The Simplefont module by Wolfgang Schuster is very good for my (not highly demanding) purposes. Certainly it is intended to do just what you describe.
Or you use \definetypeface and specserif, specsans and specmono, e.g.
\definetypeface[mainface][rm][specserif][Times New Roman][default] \definetypeface[mainface][ss][specsans] [Arial] [default] \definetypeface[mainface][tt][specmono] [Courier] [default] \definetypeface[mainface][mm][math] [times] [default]
\setupbodyfont[mainface]
\starttext … \stoptext
I've added this to the wiki page on using Fonts in LuaTeX, but since I don't know anything about these spec settings it for now just consists of our example Wolfgang. If you send back some explanations then I will add them to the wiki as well. Are these basically the same settings as used in simplefonts?
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
___________________________________________________________________________________
On 29-1-2011 10:17, John Haltiwanger wrote:
Are these basically the same settings as used in simplefonts?
Although the spec: interface (in addition to file: and name:) has fallback heuristics, simplefonts is more clever and does more extensive testing, But as with all heuristics, you can never be 100% sure what you get so in critical long term projects you can best use names or filename (and keep the files someplace backed up). It all depends on the situation. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Am 29.01.2011 um 10:17 schrieb John Haltiwanger:
I've added this to the wiki page on using Fonts in LuaTeX, but since I don't know anything about these spec settings it for now just consists of our example Wolfgang. If you send back some explanations then I will add them to the wiki as well.
The third argument use instead of serif specserif, etc. and the fourth argument is the familyname of a font.
Are these basically the same settings as used in simplefonts?
No, specserif etc. use the “spec:…” mechanism to load a font (the other two are file:… and name:…) while simplefonts use the name:… mechanism to look for a font. Wolfgang
participants (7)
-
David Rogers
-
Hans Hagen
-
John Culleton
-
John Haltiwanger
-
Marco Pessotto
-
Mojca Miklavec
-
Wolfgang Schuster