[dev-context] palatino at 10.5pt bold not found when using project structure w/ MkIV
schuster.wolfgang at gmail.com
Sun Jul 7 22:38:50 CEST 2013
Am 06.07.2013 um 12:33 schrieb Sanjoy Mahajan <sanjoy at olin.edu>:
> Thank you for all your solutions!
>> 2. You can omit the \usetypescript line.
> Good to know. Does the "palatino" keyword in \setupbodyfont
> automatically do that now (in Mark IV)?
> Should I wikify that bit of information (as MkIV-only)? (Since I don't
> really understand how the fonts work, I am hesitant to wikify much about
> it and put up incorrect information.)
The normal way to load a new font from a external typescript is
In MkII you don’t need \usetypescriptfile to load the default fonts (times,
palatino etc.) because context loads them when it generates the format
but MkIV loads them the fonts are used to save memory.
Because in many cases the name of the file is the same (with a “type-” prefix)
as the font context tries to load the file itself when you enable the font with
\setupbodyfont, even the \usetypescript call (the second argument isn’t needed
because we aren’t restricted to 256 anymore with LuaTeX) isn’t necessary
because this is also done by \setupbodyfont.
>> 3. Move the \setupbodyfont setting *before* \startcomponent.
> Right, I found that by experiment. But how should you do that with
> projects? The \setupbodyfont is usually part of an environment file,
> which is loaded by the project file. Should the "\project project_file"
> line be placed before the "\startcomponent"? Like this:
> \project project_file
> \startcomponent component_name
> If that's the recommended way, I can update
You can do this. It’s always better to make the setup of the document before
\starttext, startcomponent etc. because some values are set/reset with \starttext.
>> 4. Add \definebodyfontenvironment[10.5pt] to your document.
> Thanks, that fixes everything. On the theory of teaching a man to fish,
> how did you learn so much about making ConTeXt do just the right thing?
>> 1. Use the normal and not the developer list for such a question.
> I thought it was a bug (and it might be, though your
> definebodyfontenvironment solution makes me wonder if it is just my not
> knowing enough). In general, should bug reports go to the regular list?
The only things which are posted on the developer list nowadays are bug reports
with possible fixes or extensions to the context programing language.
More information about the dev-context