Am sending this to the list Hans, because I have some bizarre bug in my mail app or system that doesn't allow me to send message to you directly. I have no idea what is going on , but you're literally the only person this happens to! On Monday, February 3, 2003, at 06:21 PM, Hans Hagen wrote:
this is not fixed, finished, just for you to play with
Thanks! But...now what? Let's take my earlier LaTeX example: \DeclareFontShape{T1}{minion}{m}{n}{ <-6> MinionPro-SemiboldCapt-8t <6-9> MinionPro-Capt-8t <9-12> MinionPro-Regular-8t <12-15> MinionPro-Subh-8t <15-> MinionPro-Disp-8t}{\romanprotruding} And the typescript as it currently stands: \starttypescript [serif] [minionpro] [texnansi] \definefontsynonym[MinionPro-Bold] [MinionPro-Bold-8y] [encoding=texnansi] \definefontsynonym[MinionPro-BoldItalic] [MinionPro-BoldIt-8y][encoding=texnansi] \definefontsynonym[MinionPro-BoldSlanted] [MinionPro-BoldIt-8y][encoding=texnansi] \definefontsynonym[MinionPro-Caps] [MinionPro-Regular-SC-8y] [encoding=texnansi] \definefontsynonym[MinionPro-BoldCaps] [MinionPro-Bold-SC-8y] [encoding=texnansi] \definefontsynonym[MinionPro-Regular] [MinionPro-Regular-8y] [encoding=texnansi] \definefontsynonym[MinionPro-RegularItalic] [MinionPro-It-8y][encoding=texnansi] \definefontsynonym[MinionPro-RegularSlanted] [MinionPro-It-8y][encoding=texnansi] \stoptypescript So what do I add to the above so that, for example, MinionPro-Capt-8y is used as the roman default at font sizes between 6 and 9 pt, MinionPro-Regular-8y between 9 and 12, etc.? Remember: I'm not a programmer, and I still get confused by the font mechanism that is already there ;-) Bruce
At 07:28 PM 2/3/2003 -0500, Bruce D'Arcus wrote: Thanks! But...now what?
Let's take my earlier LaTeX example:
\DeclareFontShape{T1}{minion}{m}{n}{ <-6> MinionPro-SemiboldCapt-8t <6-9> MinionPro-Capt-8t <9-12> MinionPro-Regular-8t <12-15> MinionPro-Subh-8t <15-> MinionPro-Disp-8t}{\romanprotruding}
And the typescript as it currently stands:
\starttypescript [serif] [minionpro] [texnansi]
\definefontsynonym[MinionPro-Bold] [MinionPro-Bold-8y] [encoding=texnansi] \definefontsynonym[MinionPro-BoldItalic] [MinionPro-BoldIt-8y][encoding=texnansi] \definefontsynonym[MinionPro-BoldSlanted] [MinionPro-BoldIt-8y][encoding=texnansi] \definefontsynonym[MinionPro-Caps] [MinionPro-Regular-SC-8y] [encoding=texnansi] \definefontsynonym[MinionPro-BoldCaps] [MinionPro-Bold-SC-8y] [encoding=texnansi] \definefontsynonym[MinionPro-Regular] [MinionPro-Regular-8y] [encoding=texnansi] \definefontsynonym[MinionPro-RegularItalic] [MinionPro-It-8y][encoding=texnansi] \definefontsynonym[MinionPro-RegularSlanted] [MinionPro-It-8y][encoding=texnansi]
\stoptypescript
So what do I add to the above so that, for example, MinionPro-Capt-8y is used as the roman default at font sizes between 6 and 9 pt, MinionPro-Regular-8y between 9 and 12, etc.?
\definefontsynonym [AutoSerif] [\fontrange {MinionPro-Caps <10pt MinionPro-Regular <12pt MinionPro-Disp <15pt MinionPro-Something}] and then \definefontsynonym[MinionPro-Caps][MinionPro-regular-SC-8y][encoding=texnansi] with for instance \definefont[BigTitleFont][AutoSerif sa 2] and alike; it all depends on how you want to use it
Remember: I'm not a programmer, and I still get confused by the font mechanism that is already there ;-)
i'm no programmer either (educational technology, long ago -) Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------
Thanks! See below... On Tuesday, February 4, 2003, at 07:35 AM, Hans Hagen wrote:
\definefontsynonym [AutoSerif] [\fontrange {MinionPro-Caps <10pt MinionPro-Regular <12pt MinionPro-Disp <15pt MinionPro-Something}]
and then
\definefontsynonym[MinionPro-Caps][MinionPro-regular-SC- 8y][encoding=texnansi]
with for instance
\definefont[BigTitleFont][AutoSerif sa 2]
and alike; it all depends on how you want to use it
Let's just say I only want to specify a single command that says "use minionpro-osf." This command would then automatically apply the regular font to the body text, the caption to the footnotes, and the display (which you've given the synonym BigTitleFont) for, well, the title. That'll work here? Just want to make sure, as I sometimes get really lost when I start trying to do this kind of thing with ConTeXt :-) Bruce
At 10:08 AM 2/4/2003 -0500, you wrote: Let's just say I only want to specify a single command that says "use
minionpro-osf." This command would then automatically apply the regular font to the body text, the caption to the footnotes, and the display (which you've given the synonym BigTitleFont) for, well, the title.
That'll work here? Just want to make sure, as I sometimes get really lost when I start trying to do this kind of thing with ConTeXt :-)
that depends on how you've set up footnotes and alike; as long as bodyfontswitches are used, it should work since this method looks at the current bodyfontsize Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------
Before I deal with the auto-sizing thing, I need to just get this font to work, and no matter what I do I can't seem to do that! Note: there is no problem on the TeX end, as this font works fine with LaTeX. Any help greatly appreciated. I have put everything in a single file for now, so that I don't have to worry about problems elsewhere (say with loading an environment or typescript file). Bruce ============ \starttypescript [serif] [minionpro] [name] \definefontsynonym [Serif] [MinionPro-Regular] \definefontsynonym [SerifCaps] [MinionPro-Caps] \definefontsynonym [SerifCaps] [MinionPro-BoldCaps] \definefontsynonym [SerifSlanted] [MinionPro-RegularItalic] \definefontsynonym [SerifItalic] [MinionPro-RegularItalic] \definefontsynonym [SerifBold] [MinionPro-Bold] \definefontsynonym [SerifBoldSlanted] [MinionPro-BoldItalic] \definefontsynonym [SerifBoldItalic] [MinionPro-BoldItalic] \stoptypescript \starttypescript [serif] [minionpro-osf] [texnansi] \definefontsynonym[MinionPro-Bold] [MinionPro-Bold-OSF-8y] [encoding=texnansi] \definefontsynonym[MinionPro-BoldItalic] [MinionPro-BoldIt-OSF-8y][encoding=texnansi] \definefontsynonym[MinionPro-BoldSlanted] [MinionPro-BoldIt-OSF-8y][encoding=texnansi] \definefontsynonym[MinionPro-Caps] [MinionPro-Regular-OSFSC-8y] [encoding=texnansi] \definefontsynonym[MinionPro-BoldCaps] [MinionPro-Bold-OSFSC-8y] [encoding=texnansi] \definefontsynonym[MinionPro-Regular] [MinionPro-Regular-OSF-8y] [encoding=texnansi] \definefontsynonym[MinionPro-RegularItalic] [MinionPro-It-OSF-8y][encoding=texnansi] \definefontsynonym[MinionPro-RegularSlanted] [MinionPro-It-OSF-8y][encoding=texnansi] \stoptypescript \definetypeface [maintext] [rm] [serif] [minionpro-osf] [default] [encoding=texnansi] \definetypeface [maintext] [ss] [sans] [gillsans] [default] [encoding=texnansi] \definetypeface [maintext] [tt] [mono] [computer-modern] [default] [encoding=default,rscale=1.1] \definetypeface [maintext] [mm] [math] [times] [default] [encoding=default,rscale=1.1] \setupbodyfont[maintext,rm,10pt] \starttext \title{A Title} \section{A Section Heading} Here is some text, 1234567890... {\sc Small Caps} \stoptext
On Wed, 5 Feb 2003 13:12:35 -0500
"Bruce D'Arcus"
Before I deal with the auto-sizing thing, I need to just get this font to work, and no matter what I do I can't seem to do that!
Note: there is no problem on the TeX end, as this font works fine with LaTeX. Any help greatly appreciated. I have put everything in a single file for now, so that I don't have to worry about problems elsewhere (say with loading an environment or typescript file).
If i read my log-files correctly then each \definetypeface queries all typescripts completely for matching entries. Therefore, afaik, the typescripts have be in their own file. \usetypescriptfile makes this file known to ConTeXt. Jens
On Wednesday, February 5, 2003, at 04:00 PM, Jens-Uwe Morawski wrote:
If i read my log-files correctly then each \definetypeface queries all typescripts completely for matching entries. Therefore, afaik, the typescripts have be in their own file. \usetypescriptfile makes this file known to ConTeXt.
Hmm...which puts me back where I started: with a separate typescript file that doesn't work. I haven't the least clue why this isn't working, as a few people (including you) gave feedback on the earlier files I sent, and I corrected the minor problems. Still no luck. Bruce
On Wed, 5 Feb 2003 16:13:23 -0500
"Bruce D'Arcus"
On Wednesday, February 5, 2003, at 04:00 PM, Jens-Uwe Morawski wrote:
If i read my log-files correctly then each \definetypeface queries all typescripts completely for matching entries. Therefore, afaik, the typescripts have be in their own file. \usetypescriptfile makes this file known to ConTeXt.
Hmm...which puts me back where I started: with a separate typescript file that doesn't work.
What means "doesn't work"? Can you run the example from your previous mail (with a seperate type-script file) and send the log here Jens
On Wednesday, February 5, 2003, at 08:55 PM, Jens-Uwe Morawski wrote:
Can you run the example from your previous mail (with a seperate type-script file) and send the log here
Here it is. Thanks in advance!
====================================
TeXExec 3.1 - ConTeXt / PRAGMA ADE 1997-2002
executable : pdfetex
format : cont-en
inputfile : cMP
output : pdftex
interface : en
current mode : none
TeX run : 1
This is pdfeTeX, Version 3.14159-1.00b-pretest-20020211-2.1 (Web2C
7.3.7x)
entering extended mode
(./cMP.tex{/usr/local/teTeX/share/texmf.local/pdftex/config/pdftex.cfg}
ConTeXt ver: 2003.1.10 fmt: 2003.1.12 int: english mes: english
language : language en is active
On Wed, 5 Feb 2003 21:40:18 -0500
"Bruce D'Arcus"
On Wednesday, February 5, 2003, at 08:55 PM, Jens-Uwe Morawski wrote:
Can you run the example from your previous mail (with a seperate type-script file) and send the log here
typescript : [serif] [minionpro-osf] [name,default,texnansi,special] (/Users/bdarcus/Library/texmf/tex/context/base/type-syn.tex) (/Users/bdarcus/Library/texmf/tex/context/base/type-enc.tex) (/Users/bdarcus/Library/texmf/tex/context/base/type-siz.tex) (/Users/bdarcus/Library/texmf/tex/context/base/type-map.tex) (/Users/bdarcus/Library/texmf/tex/context/base/type-spe.tex) (/Users/bdarcus/Library/texmf/tex/context/base/type-exa.tex)
Here your type-script is not loaded. For example, if you have your type-script (i assume its name is type-minion.tex) located in /Users/bdarcus/Library/texmf-local/tex/context/user/type-minion.tex then should be here (and for each other typescript-message) an log entry like: (/Users/bdarcus/Library/texmf-local/tex/context/user/type-minion.tex) Thus, check if your type-script can be found; run kpsewhich <your-typescript-file-name> in your document-directory for example: kpsewhich type-minion.tex and check for misspellings, since ConTeXt gives no error message if you declare a typescript-file via \usetypescriptfile[type-minionn] but its name is type-minion.tex BTW, Hans, can you add a log-warning for unknown typescript files.
typescript : [serif] [default] [size] (/Users/bdarcus/Library/texmf/tex/context/base/type-syn.tex) [...]
Best, Jens
Thanks Jens. I still don't see anything obvious though (see below).... On Thursday, February 6, 2003, at 07:58 AM, Jens-Uwe Morawski wrote:
Thus, check if your type-script can be found; run kpsewhich <your-typescript-file-name> in your document-directory for example: kpsewhich type-minion.tex
and check for misspellings, since ConTeXt gives no error message if you declare a typescript-file via \usetypescriptfile[type-minionn] but its name is type-minion.tex
Here's what I get: bdarcus% kpsewhich type-OpenTypePro.tex /Users/bdarcus/Library/texmf/tex/context/user/type-OpenTypePro.tex And this is copied from my environment file: \usetypescriptfile[type-OpenTypePro] No typos, soo...??? Here's the document source, BTW: \environment minionpro-osf.tex \starttext \title{A Title} \section{A Section Heading} Here is some text, 1234567890... \stoptext Bruce
Wanna bet that context is looking for type-Ope.tex ? On Thu, 6 Feb 2003 09:53:13 -0500, Bruce wrote:
Thanks Jens. I still don't see anything obvious though (see below)....
On Thursday, February 6, 2003, at 07:58 AM, Jens-Uwe Morawski wrote:
Thus, check if your type-script can be found; run kpsewhich <your-typescript-file-name> in your document-directory for example: kpsewhich type-minion.tex
and check for misspellings, since ConTeXt gives no error message if you declare a typescript-file via \usetypescriptfile[type-minionn] but its name is type-minion.tex
Here's what I get:
bdarcus% kpsewhich type-OpenTypePro.tex /Users/bdarcus/Library/texmf/tex/context/user/type-OpenTypePro.tex
And this is copied from my environment file:
\usetypescriptfile[type-OpenTypePro]
No typos, soo...???
Here's the document source, BTW:
\environment minionpro-osf.tex
\starttext
\title{A Title}
\section{A Section Heading}
Here is some text, 1234567890...
\stoptext
Bruce
_______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
-- groeten, Taco
On Thursday, February 6, 2003, at 09:58 AM, Taco Hoekwater wrote:
Wanna bet that context is looking for type-Ope.tex ?
I hadn't thought about that one! But changing the typescriptfile name to type-OTP.tex also has no effect. Bruce
At 09:53 AM 2/6/2003 -0500, you wrote:
Thanks Jens. I still don't see anything obvious though (see below)....
On Thursday, February 6, 2003, at 07:58 AM, Jens-Uwe Morawski wrote:
Thus, check if your type-script can be found; run kpsewhich <your-typescript-file-name> in your document-directory for example: kpsewhich type-minion.tex
and check for misspellings, since ConTeXt gives no error message if you declare a typescript-file via \usetypescriptfile[type-minionn] but its name is type-minion.tex
Here's what I get:
bdarcus% kpsewhich type-OpenTypePro.tex /Users/bdarcus/Library/texmf/tex/context/user/type-OpenTypePro.tex
And this is copied from my environment file:
\usetypescriptfile[type-OpenTypePro]
No typos, soo...???
is this a case sensitive problem? i'm upgrading the file search mechsnism (faster, optional tracing), so some day soon it will be easier to track this down Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------
On Thu, 6 Feb 2003 09:53:13 -0500
"Bruce D'Arcus"
Thanks Jens. I still don't see anything obvious though (see below)....
On Thursday, February 6, 2003, at 07:58 AM, Jens-Uwe Morawski wrote:
Thus, check if your type-script can be found; run kpsewhich <your-typescript-file-name> in your document-directory for example: kpsewhich type-minion.tex
and check for misspellings, since ConTeXt gives no error message if you declare a typescript-file via \usetypescriptfile[type-minionn] but its name is type-minion.tex
Here's what I get:
bdarcus% kpsewhich type-OpenTypePro.tex /Users/bdarcus/Library/texmf/tex/context/user/type-OpenTypePro.tex
And this is copied from my environment file:
\usetypescriptfile[type-OpenTypePro]
No typos, soo...???
Here's the document source, BTW:
\environment minionpro-osf.tex
Please, step by step! Thus, try it first without an environment-file. In your TeX-file load the typescript using \usetypescriptfile, make your \definetypeface definitions there (the definition for rm/serif should be enough), setup your body-font and let us see what happens. Jens
On Thursday, February 6, 2003, at 11:53 AM, Jens-Uwe Morawski wrote:
Thus, try it first without an environment-file. In your TeX-file load the typescript using \usetypescriptfile, make your \definetypeface definitions there (the definition for rm/serif should be enough), setup your body-font and let us see what happens.
Here's the file, which doesn't work either: \usetypescriptfile[type-OTP] \definetypeface [maintext] [rm] [serif] [minionpro-osf][default] [encoding=texnansi] \definetypeface [maintext] [ss] [sans] [gillsans] [default] [encoding=texnansi] \setupbodyfont[maintext,rm,serif,10pt] \starttext \title{A Title} \section{A Section Heading} Here is some text, 1234567890... {\sc Q Small Caps} \stoptext
On Thu, 6 Feb 2003 12:25:05 -0500
"Bruce D'Arcus"
On Thursday, February 6, 2003, at 11:53 AM, Jens-Uwe Morawski wrote:
Thus, try it first without an environment-file. In your TeX-file load the typescript using \usetypescriptfile, make your \definetypeface definitions there (the definition for rm/serif should be enough), setup your body-font and let us see what happens.
Here's the file, which doesn't work either:
i'm puzzled. AFAIK, MacOS X (it seems that you work with this system) has internally a not case-sensitive file-system. Maybe, this confuses the kpathsee library.
\usetypescriptfile[type-OTP]
\definetypeface [maintext] [rm] [serif] [minionpro-osf][default] [encoding=texnansi] \definetypeface [maintext] [ss] [sans] [gillsans] [default] [encoding=texnansi]
\setupbodyfont[maintext,rm,serif,10pt]
\setupbodyfont[maintext,rm,10pt] should be enough Jens
The fight towards understanding the font mechanism continues... On Wed, 5 Feb 2003, Bruce D'Arcus wrote:
==================================== <clipclip> pdftex : needs map file: original-context-symbol.map pdftex : needs map file: pl0-ams-cmr.map pdftex : needs map file: original-vogel-symbol.map <clipclip>
WHAT in the compilation system says that these are to be loaded? Since I turned on (i.e. uncommented) the /autoloadmapfilestrue setting in my cont-sys.tex to make the fonts work, it seems that the three above mentioned map files are loaded twice, first here in the very beginning and then somewhere a bit later, so I get all these annoying warnings about "Warning: pdfetex.exe (file c:/TeXLive/texmf/pdftex/config/context/pl0-ams-cmr.map): entry for `pltt9' already exists, duplicates ignored" While this is less of a problem than not having the fonts at all, I'd like to get rid of it, if possible... Mari
mari.voipio@iki.fi said this at Fri, 7 Feb 2003 13:46:46 +0200:
"Warning: pdfetex.exe (file c:/TeXLive/texmf/pdftex/config/context/pl0-ams-cmr.map): entry for `pltt9' already exists, duplicates ignored"
While this is less of a problem than not having the fonts at all, I'd like to get rid of it, if possible...
Very much agreed... these warning messages are what make my system (in a certain configuration) slow down to a crawl. adam -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay atl@comp.lancs.ac.uk Computing Dept, Lancaster University +44(0)1524/594.537 Lancaster, LA1 4YR, UK Fax:+44(0)1524/593.608 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
At 01:46 PM 2/7/2003 +0200, you wrote:
The fight towards understanding the font mechanism continues...
On Wed, 5 Feb 2003, Bruce D'Arcus wrote:
==================================== <clipclip> pdftex : needs map file: original-context-symbol.map pdftex : needs map file: pl0-ams-cmr.map pdftex : needs map file: original-vogel-symbol.map <clipclip>
WHAT in the compilation system says that these are to be loaded? Since I turned on (i.e. uncommented) the /autoloadmapfilestrue setting in my cont-sys.tex to make the fonts work, it seems that the three above mentioned map files are loaded twice, first here in the very beginning and then somewhere a bit later, so I get all theseannoyingwarningsaboutWarningpdfetex.zl9filecTeXLivetexmfpdftexconfigcontextpl0-ams-cmr.mapentryfor`pltt9'alreadyexists,duplicatesignoredWhilethisislessofaproblemthannothavingthefontsatall,I'dliketogetridofit,if possible...
i cannot peek into your system -) you can of course turn off map loading and do it manually in the pdftex.cfg file (here i don't load anything in pdftex.cfg) it's on thanh's todo list to let map files be loaded after the first page as well as let map file entries be overloaded (which would remove the warnings) Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------
At 01:12 PM 2/5/2003 -0500, Bruce D'Arcus wrote:
Before I deal with the auto-sizing thing, I need to just get this font to work, and no matter what I do I can't seem to do that!
Note: there is no problem on the TeX end, as this font works fine with LaTeX. Any help greatly appreciated. I have put everything in a single file for now, so that I don't have to worry about problems elsewhere (say with loading an environment or typescript file).
Bruce
============
\starttypescript [serif] [minionpro] [name]
\starttypescript [serif] [minionpro-osf] [texnansi]
\definetypeface [maintext] [rm] [serif] [minionpro-osf] [default] [encoding=texnansi]
i think that the first typescript should be minionpro-osf I'll send you a version of type-ini with tracing (\tracetypescriptstrue) (no fun on your slow terminal) Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------
On Fri, 07 Feb 2003 10:28:08 +0100, "Hans Hagen"
i think that the first typescript should be minionpro-osf
I'll send you a version of type-ini with tracing (\tracetypescriptstrue) (no fun on your slow terminal)
I've attached the log file. Nothing seems wrong to me... Bruce -- http://fastmail.fm - Choose from over 50 domains or use your own
participants (6)
-
Adam Lindsay -
Bruce D'Arcus -
Hans Hagen -
Jens-Uwe Morawski -
mari.voipio＠iki.fi -
Taco Hoekwater