[NTG-context] font handling and \showfont
Hi all, I have a question regarding the use of font handling. With the trailer \setupoutput[pdftex] \useencoding[win] \setupalign[hanging] \setupfontsynonym [Serif] [handling=pure] \setupfontsynonym [Sans] [handling=pure] \setupfontsynonym [Mono] [handling=punctuation] \usetypescript [all] [latin-modern][texnansi] \setupbodyfont[reset] \setupbodyfont[cmr] I get output with expected hanging punctuation only if I type after \starttext the command \showfont[Serif]. Without the latter the protruding mechanism doesn't work. My question is: How can I get hanging punctuation without the command \showfont[Serif]? With many thanks for any hint Albrecht ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] \setuplist[...][alternative=c] doesn't work
Hi all, I've problems making a TOC. I'm using ConTeXt ver: 2004.12.06 and pdfeTeXk, Version 3.141592-1.20a-2.2 (Web2c 7.5.3). If I type e.g. \setuplist[section][alternative=c] I don't get any dots. Is this a bug, or what could be wrong? With many thanks for any hint Albrecht ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Re: \setuplist[...][alternative=c] doesn't work
Hi all, with the recent alpha version the \setuplist procedure works fine. Greetings Albrecht On Mon, 31 Jan 2005, Albrecht Kauffmann wrote: Hi all, I've problems making a TOC. I'm using ConTeXt ver: 2004.12.06 and pdfeTeXk, Version 3.141592-1.20a-2.2 (Web2c 7.5.3). If I type e.g. \setuplist[section][alternative=c] I don't get any dots. Is this a bug, or what could be wrong? With many thanks for any hint Albrecht ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] How to use and not embed the PdfBase14 fonts?
Hi all! I want to generate PDF documents that use the standard PDF fonts (Helvetica, Times-Roman, and Courier) and not to embed these fonts. With my former installation (TexLive-2003 and a ConText distribution of last autumn) this was possible by using the following lines in the praeambel: \usetypescript[adobekb][texnansi] \usetypescript[postscript][texnansi] \setupbodyfont[postscript,ss,13pt] (In addition, I had to configure pdfTeX by updmap --setoption pdftexDownloadBase14 false). After I upgraded to TexLive-2004 this does no longer work! I found that the typescript adobekb was replaced by type-akb. Yet, the encoding texnansi seems no longer to be available (Metafont complains that it can not find: texnansi-utmr8a). Changing the encoding to ec that still is available yields: \usetypescript[type-akb][ec] \usetypescript[postscript][ec] \setupbodyfont[postscript,ss,13pt] Yet, using these lines in the praeambel results in a document that uses the NimbusSanL-Regu font, that clearly has to be embedded. Does anyone know how the standard PDF fonts can be used while not being embedded? Thanks for your attention, Stefan ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] \setuplist[...][alternative=c] doesn't work
Albrecht Kauffmann wrote: Hi all, I've problems making a TOC. I'm using ConTeXt ver: 2004.12.06 and pdfeTeXk, Version 3.141592-1.20a-2.2 (Web2c 7.5.3). If I type e.g. \setuplist[section][alternative=c] I don't get any dots. Is this a bug, or what could be wrong? the list module is under partial reconstruction so you may have a buggy version; can yoi try the latest version? 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] How to use and not embed the PdfBase14 fonts?
Stefan Wachter wrote: I want to generate PDF documents that use the standard PDF fonts (Helvetica, Times-Roman, and Courier) and not to embed these fonts. With my former installation (TexLive-2003 and a ConText distribution of last autumn) this was possible by using the following lines in the praeambel: \usetypescript[adobekb][texnansi] \usetypescript[postscript][texnansi] \setupbodyfont[postscript,ss,13pt] (In addition, I had to configure pdfTeX by updmap --setoption pdftexDownloadBase14 false). After I upgraded to TexLive-2004 this does no longer work! I found that the typescript adobekb was replaced by type-akb. Yet, the encoding texnansi seems no longer to be available (Metafont complains that it can not find: texnansi-utmr8a). Changing the encoding to ec that still is available yields: texnansi tfm files are not distributed (actually, what gets distributed is some mix of encodings) so you need to generate them using texfont \usetypescript[type-akb][ec] \usetypescript[postscript][ec] \setupbodyfont[postscript,ss,13pt] Yet, using these lines in the praeambel results in a document that uses the NimbusSanL-Regu font, that clearly has to be embedded. you can make a private map file, say myfonts.map, and load that one with \loadmapfile[myfonts.map] lines with as first char an '=' will replace other map entries, so that way you can overrule defaults Does anyone know how the standard PDF fonts can be used while not being embedded? 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 - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] How to use and not embed the PdfBase14 fonts?
On Mon, 31 Jan 2005, Hans Hagen wrote: Stefan Wachter wrote: Does anyone know how the standard PDF fonts can be used while not being embedded? in principle you can do by not mentioning the fontfile names (e. g. for Times-Roman leave out the ptmr8a.pfb) in the mapfile lines (this works only for the 14 standard fonts, else an error will be flagged). But i don't know how this is done in ConTeXt. Regards, Hartmut ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Russia (cyrillic letters)
On Sun, 30 Jan 2005 22:55:51 +0100, h h extern [EMAIL PROTECTED] wrote: Mikael Persson wrote: Hm, I am entering utf8 code. I am not sure how it got converted in the email, however, when I type my .tex file I am sure that it is in utf-8. But you mean that this example should work? I attatch the testfile and the resulting pdf and logs and so on... tracing shows that the utf part is okay: \enableregime[utf] % \definetypeface [russian] % [rm] [serif] [computer-modern] [default] [encoding=t2a] % % \setupbodyfont[russian] \starttext \startbuffer % Some russian characters \stopbuffer \chardef\utfunicodetracer=0 \blank \getbuffer \blank \chardef\utfunicodetracer=2 \blank \getbuffer \blank \chardef\utfunicodetracer=7 \blank \getbuffer \blank \stoptext but i cannot test the font part, can you send me a zip with your t2a tfm files and map file and enc file? Hans Just for information (mostly to the ones reading this email list from archives). It now works using utf input and get. A minimal file: % start of test file % \enableregime[utf] \useencoding[cyr] \definetypeface [russian] [rm] [serif] [computer-modern] [default] [encoding=t2a] \setupbodyfont[russian] \starttext % Some russian characters \stoptext % stop of test file % For this to work, you have to generate the tfm-files if you do not already have them (which can be done with the afm2tfm util). Thanks Hans and Adam for the fast replies to get this working :) /Micke P ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
