Re: [NTG-context] typescripts again (was to keep you busy ...)
At 11:21 AM 2/8/2003 -0800, Bruce D'Arcus wrote:
On Sat, 08 Feb 2003 17:22:03 +0100, "Hans Hagen"
said: At 06:59 AM 2/7/2003 -0800, you wrote:
On Fri, 07 Feb 2003 09:13:03 +0100, "Hans Hagen"
said: this means that it cannot find it on th elocal path but the file is
found
elsewhere (there are some 5 strategies for locating files in context)
can you send me the file + test file?
Which "file"? I'll assume the typescriptfile, etc...
your problem is related to a naming inconsistency:
you map serif's in a typescript called
[minionpro]
but in defining the typeface use:
[minionpro-osf]
so, either name the typescript -pro as well, or call it up using:
[minionpro,minionpro-osf]
Seems that halefway defining you lost the -osf -)
Well, this is just the start of the typescript. What I want in the end is to have typescripts to call four different fonts: Minion, Minion-SC, Minion-OSF, and Minion-SCOSF. So how do I deal with *that*? As you can see, I don't quite understand some piece of this puzzle, though I'm not really sure which!
in that case, say things like [minionpro,minionpro-osf] and another typeface [minionpro,minionpro-whow]
Also, I just changed the name of the first typescript to add the -osf, ran the file, adn got this error:
! Font \*maintext5ptrmbs*:=MinionPro-BoldIt-OSF-8y at 5.0pt not loaded: Not eno
this can be solved by enlarging the mem settings in texmf.cnf and regenerating the format 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 Saturday, February 8, 2003, at 02:38 PM, Hans Hagen wrote:
Also, I just changed the name of the first typescript to add the -osf, ran the file, and got this error:
! Font \*maintext5ptrmbs*:=MinionPro-BoldIt-OSF-8y at 5.0pt not loaded: Not enough room left.
this can be solved by enlarging the mem settings in texmf.cnf and regenerating the format
With Hans' help, am making progress on the typescript, but am now getting a memory error. Regarding suggestion to change the settings in texmf.cnf, here is what I currently have: % Max number of characters in all strings, including all error messages, % help texts, font names, control sequences. These values apply to TeX and MP. pool_size.context = 750000 pool_size = 500000 % Minimum pool space after TeX/MP's own strings; must be at least % 25000 less than pool_size, but doesn't need to be nearly that large. string_vacancies.context = 45000 string_vacancies = 25000 % Maximum number of strings. max_strings.context = 55000 max_strings = 35000 % min pool space left after loading .fmt pool_free.context = 47500 pool_free = 25000 What should I change, and to what recommended value? Bruce
At 10:47 AM 2/9/2003 -0500, Bruce D'Arcus wrote:
On Saturday, February 8, 2003, at 02:38 PM, Hans Hagen wrote:
Also, I just changed the name of the first typescript to add the -osf, ran the file, and got this error:
! Font \*maintext5ptrmbs*:=MinionPro-BoldIt-OSF-8y at 5.0pt not loaded: Not enough room left.
this can be solved by enlarging the mem settings in texmf.cnf and regenerating the format
With Hans' help, am making progress on the typescript, but am now getting a memory error. Regarding suggestion to change the settings in texmf.cnf, here is what I currently have:
the tex live values are normally ok, here i have:
% Max number of characters in all strings, including all error messages, % help texts, font names, control sequences. These values apply to TeX and MP. pool_size.context = 750000 pool_size = 500000 % Minimum pool space after TeX/MP's own strings; must be at least % 25000 less than pool_size, but doesn't need to be nearly that large. string_vacancies.context = 45000 string_vacancies = 25000 % Maximum number of strings. max_strings.context = 55000 max_strings = 35000 % min pool space left after loading .fmt pool_free.context = 47500 pool_free = 25000
buf_size.context = 200000 % needed for omega bug extra_mem_bot.context = 2000000 extra_mem_top.context = 2000000 font_max.context = 2000 font_mem_size.context = 1000000 hash_extra.context = 50000 main_memory.context = 1500000 max_strings.context = 100000 nest_size.context = 500 obj_tab_size.context = 300000 dest_names_size = 300000 param_size.context = 5000 pool_free.context = 47500 pool_size.context = 1250000 save_size.context = 50000 stack_size.context = 5000 string_vacancies.context = 90000 main_memory.mpost = 2000000 pool_size.mpost = 200000 ------------------------------------------------------------------------- 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 for the help with this font stuff people! It now works. Beyond needing to change the memory settings, I was incorrectly specifying the osf font. This works though: \usetypescriptfile[type-otp.tex] \definetypeface [maintext] [rm] [serif] [minionpro,minionpro-osf][default] [encoding=texnansi] \definetypeface [maintext] [ss] [sans] [gillsans] [default] [encoding=texnansi] \setupbodyfont[maintext,rm,10pt] Now, to go back to the auto-size-switching thing, here's a variation on the suggestion by Hans: \definefontsynonym [AutoSerif] [\fontrange {MinionPro-Capt <10pt MinionPro-Regular <12pt MinionPro-Subh <15pt MinionPro-Display ??? }] (am not sure how to specify the last) So exactly where do I put this in the typescriptfile, and how do I integrate it? What I want to do is to be able to put, for example, MinionPro-BoldCapt-OSF-8y, into the "minionpro,minionpro-osf" typescript below, and each respective optical font into its respective typescript. I'm not really understanding the logic of how this would work. \starttypescript [serif] [minionpro] [name] \definefontsynonym [Serif] [MinionPro-Regular] \definefontsynonym [SerifCaps] [MinionPro-Caps] \definefontsynonym [SerifSlanted] [MinionPro-RegularItalic] \definefontsynonym [SerifItalic] [MinionPro-RegularItalic] \definefontsynonym [SerifBold] [MinionPro-Bold] \definefontsynonym [SerifBoldSlanted] [MinionPro-BoldItalic] \definefontsynonym [SerifBoldItalic] [MinionPro-BoldItalic] \stoptypescript \starttypescript [serif] [minionpro,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 Bruce
Goodevening all, Suddenly this turns up, texexec-ing files that did ok until now, and when I continue I get a row of several : on top. The strange thing is: there is no : in line 4 Does anybody now the answer to this little enigma? ? ) (./Factuur1.tuo ! Undefined control sequence. l.4 \thisissectionseparator {:}
At 09:05 PM 2/9/2003 +0100, you wrote:
Goodevening all,
Suddenly this turns up, texexec-ing files that did ok until now, and when I continue I get a row of several : on top. The strange thing is: there is no : in line 4 Does anybody now the answer to this little enigma?
? ) (./Factuur1.tuo ! Undefined control sequence. l.4 \thisissectionseparator
looks like an old context running a newer tuo file; this directive was added when french active :'s were added (and as a result dynamic separators) so (1) check what context you run (maybe no new dutch/english format generated) (2) remove the tuo 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 -------------------------------------------------------------------------
Op zo 09-02-2003, om 21:37 schreef Hans Hagen:
At 09:05 PM 2/9/2003 +0100, you wrote:
Goodevening all,
Suddenly this turns up, texexec-ing files that did ok until now, and when I continue I get a row of several : on top. The strange thing is: there is no : in line 4 Does anybody now the answer to this little enigma?
? ) (./Factuur1.tuo ! Undefined control sequence. l.4 \thisissectionseparator
looks like an old context running a newer tuo file;
This indeed was the answer, thanks again
this directive was added when french active :'s were added (and as a result dynamic separators)
so
(1) check what context you run (maybe no new dutch/english format generated) (2) remove the tuo
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 -------------------------------------------------------------------------
_______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
At 02:45 PM 2/9/2003 -0500, Bruce D'Arcus wrote:
Thanks for the help with this font stuff people! It now works. Beyond needing to change the memory settings, I was incorrectly specifying the osf font. This works though:
\usetypescriptfile[type-otp.tex]
\definetypeface [maintext] [rm] [serif] [minionpro,minionpro-osf][default] [encoding=texnansi] \definetypeface [maintext] [ss] [sans] [gillsans] [default] [encoding=texnansi]
\setupbodyfont[maintext,rm,10pt]
Now, to go back to the auto-size-switching thing, here's a variation on the suggestion by Hans:
\definefontsynonym [AutoSerif] [\fontrange {MinionPro-Capt <10pt MinionPro-Regular <12pt MinionPro-Subh <15pt MinionPro-Display ??? }]
(am not sure how to specify the last)
no specification, just a name, it's the auto-fall back
So exactly where do I put this in the typescriptfile, and how do I integrate it? What I want to do is to be able to put, for example, MinionPro-BoldCapt-OSF-8y, into the "minionpro,minionpro-osf" typescript below, and each respective optical font into its respective typescript. I'm not really understanding the logic of how this would work.
\starttypescript [serif] [minionpro] [name]
\definefontsynonym [Serif] [MinionPro-Regular] \definefontsynonym [SerifCaps] [MinionPro-Caps] \definefontsynonym [SerifSlanted] [MinionPro-RegularItalic] \definefontsynonym [SerifItalic] [MinionPro-RegularItalic] \definefontsynonym [SerifBold] [MinionPro-Bold] \definefontsynonym [SerifBoldSlanted] [MinionPro-BoldItalic] \definefontsynonym [SerifBoldItalic] [MinionPro-BoldItalic]
\stoptypescript
something \starttypescript [serif] [minionpro-auto] [name] \definefontsynonym [Serif] [\fontrange{.....}] .... \stoptypescript 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 Sunday, February 9, 2003, at 05:06 PM, Hans Hagen wrote:
Now, to go back to the auto-size-switching thing, here's a variation on the suggestion by Hans:
\definefontsynonym [AutoSerif] [\fontrange {MinionPro-Capt <10pt MinionPro-Regular <12pt MinionPro-Subh <15pt MinionPro-Display ??? }]
(am not sure how to specify the last)
no specification, just a name, it's the auto-fall back
But something like "<10pt" is saying, "if font size is less than 10pt, use MinionPro-Capt"; right? So how do I deal with the Display size, which is for fonts greater than or equal to 15pt?
So exactly where do I put this in the typescriptfile, and how do I integrate it? What I want to do is to be able to put, for example, MinionPro-BoldCapt-OSF-8y, into the "minionpro,minionpro-osf" typescript below, and each respective optical font into its respective typescript. I'm not really understanding the logic of how this would work.
something
\starttypescript [serif] [minionpro-auto] [name]
\definefontsynonym [Serif] [\fontrange{.....}] ....
\stoptypescript
So in the example above, does that mean I need to have four separate lines for "Serif"? Or to put differently, what is the {.....} in the [\fontrange{.....}] thing above? \starttypescript [serif] [minionpro-auto] [name] \definefontsynonym [Serif] [\fontrange{MinionPro-Capt}] \definefontsynonym [Serif] [\fontrange{MinionPro-Regular}] \definefontsynonym [Serif] [\fontrange{MinionPro-Subh}] \definefontsynonym [Serif] [\fontrange{MinionPro-Display}] etc., etc. \stoptypescript And then in each other variant I specify (like "minionpro-osf"), I need? \starttypescript [serif] [minionpro-auto,minionpro-auto-osf] [name] \definefontsynonym [\fontrange{MinionPro-Capt}] [MinionPro-Capt-OSF-8y] \definefontsynonym [\fontrange{MinionPro-Regular}] [MinionPro-Regular-OSF-8y] \definefontsynonym [\fontrange{MinionPro-Subh}] [MinionPro-Subh-OSF-8y] \definefontsynonym [\fontrange{MinionPro-Display}] [MinionPro-Display-OSF-8y] etc., etc. \stoptypescript
At 06:09 PM 2/9/2003 -0500, Bruce D'Arcus wrote:
On Sunday, February 9, 2003, at 05:06 PM, Hans Hagen wrote:
Now, to go back to the auto-size-switching thing, here's a variation on the suggestion by Hans:
\definefontsynonym [AutoSerif] [\fontrange {MinionPro-Capt <10pt MinionPro-Regular <12pt MinionPro-Subh <15pt MinionPro-Display ??? }]
(am not sure how to specify the last)
no specification, just a name, it's the auto-fall back
But something like "<10pt" is saying, "if font size is less than 10pt, use MinionPro-Capt"; right? So how do I deal with the Display size, which is for fonts greater than or equal to 15pt?
that will happen because that is the default (i.e. when no match is found) 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 -------------------------------------------------------------------------
participants (3)
-
Bruce D'Arcus
-
Hans Hagen
-
Roef Ragas