saved string in Lua you can see that blank lines are removed
from the text.
Wolfgang
Indeed. This does build without error, but the
utilities.strings.striplong result is worse than the string.strip
result, with some additional whitespace at the end of the test string
from the earlier examp
string in Lua you can see that blank lines are removed
from the text.
Wolfgang
Indeed. This does build without error, but the
utilities.strings.striplong result is worse than the string.strip
result, with some additional whitespace at the end of the test string
On 2014-03-05 03:24, Hans Hagen wrote:
On 3/5/2014 5:45 AM, Rik Kabel wrote:
I am trying to strip all leading and trailing whitespace from a string.
I have tried two methods, neither of which is satisfactory.
The first method uses \ignorespaces and \removeunwantedspaces. This
fails to strip
On 3/5/2014 5:45 AM, Rik Kabel wrote:
I am trying to strip all leading and trailing whitespace from a string.
I have tried two methods, neither of which is satisfactory.
The first method uses \ignorespaces and \removeunwantedspaces. This
fails to strip leading and trailing newlines.
The second
I am trying to strip all leading and trailing whitespace from a string.
I have tried two methods, neither of which is satisfactory.
The first method uses \ignorespaces and \removeunwantedspaces. This
fails to strip leading and trailing newlines.
The second method uses the Lua string.strip
The second issue, however, leaves me perplexed for a solution
to avoid the issue while maintaining the desired vertical whitespace
(see (http://i.imgur.com/n46zEhf.png) between items. Any suggestions?
Hopefully these are sufficiently minimal examples.
] 8< overlapping text 8< [
I can achieve without losing any content
contains too much extraneous whitespace:
http://i.imgur.com/A3RhnjS.png
Thank you!
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist
und
for this deficiency of a standard solution?
All lines in my book have a certain (default) linespacing.
TOC entries are rendered (by default) using bigger linespacing.
I just wanted to make that TOC distance smaller a bit. Is this really the
only solution?
\definegridsnapping[crap] [fit] % wha
but here I suspect it is ignored as my chapter
> > start on a new page.
> >
>
> before={\blank[force,20mm]},
>
> whitespace at the top of a page is discarded otherwise
I was hoping there is a simple option for this (any counterpart to XSL-FO
space-before.conditionality=&q
apter{Intro}text
\startfrontmatter
\startbodymatter
\chapter{Chapter}text
\stopbodymatter
\stoptext
Any help is highly appreciated.
before={\blank[force,20mm]},
whitespace at the top of a page is discarded othe
On 9/4/2013 9:51 PM, Mikoláš Štrajt wrote:
On 2013-09-04 Hans Hagen wrote:
> first of all you need to switch to mkiv ... more change on tips and
solutions then
OK. I have switched to mkiv. What now about my head whitespace problems.
well, first provide a mkiv example ... less code than
On 2013-09-04 Hans Hagen wrote:
> first of all you need to switch to mkiv ... more change on tips and
solutions then
OK. I have switched to mkiv. What now about my head whitespace problems.
--
Mikolas Strajt___
On 9/3/2013 11:10 PM, Mikoláš Štrajt wrote:
% Hello All!
%
% In the folowing style, I need to do some whitespace tweaks. Unfortunately, I
didn't found solutions in manual, so I am asking here.
%
% I need:
%
% - make first paragraph after author name noindented, i tried to put some
\noin
% Hello All!
%
% In the folowing style, I need to do some whitespace tweaks. Unfortunately, I
didn't found solutions in manual, so I am asking here.
%
% I need:
%
% - make first paragraph after author name noindented, i tried to put some
\nointdent here, but without any effect
% - make ver
lpeg.Cs, lpeg.Ct, lpeg.Cf, lpeg.Cg, lpeg.Cp
local lpegmatch = lpeg.match
local format = string.format
local utfchar = utf.char
@@ -42,7 +42,15 @@
local whitespace = lpeg.patterns.whitespace
local optionalws = whitespace^0
-local escape = C(P("\\u") / "0x" * S("09
> \input knuth
>> \stopframed
>> \stopcontent
>> \startcaption
>> Some description
>> \stopcaption
>> \stopcombination
>>
>> \stoptext
Thanks, it helped a lot!
I've added this to control the gap (width) between text bl
? More from \loadfontgoodies[lm]? To what file does that
resolve?
The commands loads lm.lfg
The somewhat simpleminded idea of adding \ignorespaces at the end of the
\definetypeface macro and friends, will not work I am afraid.
Is there a possibilty to remove all whitesp
\loadfontgoodies[lm]? To what file does that
>> resolve?
>
> The commands loads lm.lfg
>
The somewhat simpleminded idea of adding \ignorespaces at the end of the
\definetypeface macro and friends, will not work I am afraid.
Is there a possibilty to remove all whitespace from th
Am 30.04.2013 12:00, schrieb ntg-context-requ...@ntg.nl:
When you use the grid you have to restrict yourself and use fixed values for
the interlinespace. The correction of the whitespace after the increased
linespace can be calculated and compensated by half lines in the \blank command.
Thansk
from setting arabic words into the german text, for
> arabic I have to use a bigger font, and so the problem simulated here arises.
When you use the grid you have to restrict yourself and use fixed values for
the interlinespace. The correction of the whitespace after the increased
linespace can
tead putting a
\goodbreak between entries but figured it wasn't worth the
bother. Since I call this fragment a \chapter it is listed in the
TOC. I had to put \whitespace[medium] right after the
\startbackmatter command just as I did after \startbodymatter.
for my purposes for this task si
definitely present entity an din order to make this
work:
test
\index{xxx}
test
\index will bind to the next paragraph when it's a loner
otherwise we would get
test
\index{xxx}
test
which could show up as an unwanted extra whitespace and/or page break
with dislocated index entry
this ki
this
work:
test
\index{xxx}
test
\index will bind to the next paragraph when it's a loner
otherwise we would get
test
\index{xxx}
test
which could show up as an unwanted extra whitespace and/or page break
with dislocated index entry
this kind of behaviour has always been pa
On Mon, Apr 08, 2013 at 05:49:51PM +0200, Hans Hagen wrote:
> On 4/8/2013 1:21 PM, Devendra Ghate wrote:
> >Dear all,
> >
> >I have noticed a new problem in the \startalign environment recently.
> >\startalign adds whitespace after the formula. If I remove the *\NR* fro
On 4/8/2013 1:21 PM, Devendra Ghate wrote:
Dear all,
I have noticed a new problem in the \startalign environment recently.
\startalign adds whitespace after the formula. If I remove the *\NR* from the
last equation then the white space disappears. But I need to keep it for
numbering the last
Dear all,
I have noticed a new problem in the \startalign environment recently.
\startalign adds whitespace after the formula. If I remove the *\NR* from the
last equation then the white space disappears. But I need to keep it for
numbering the last equation.
In any case, I thought that the
> This is more of a follow-up question than an answer: wouldn't
> \blank[nowhite] be better?
Quite possibly. When I read "I want to be able to adjust the vertical
white space" my mind went towards adding whitespace instead of
removing it, but that was just an assumption.
Am 16.03.2013 um 14:58 schrieb "Meer H. van der" :
> Solved. Before was \setupwhitespace[small], for this I had to surround
> everything with
> \start
> \setupwhitespace[none]
> ..
> \stop
You can also prevent the space with the following setup for the narrower
environment.
\setupnarrower
Solved. Before was \setupwhitespace[small], for this I had to surround
everything with
\start
\setupwhitespace[none]
..
\stop
Hans van der Meer
On 16 mrt. 2013, at 13:44, Wolfgang Schuster
wrote:
>
> Am 16.03.2013 um 12:45 schrieb H. van der Meer :
>
>> I find that in
>>
>> intro text
>>
Am 16.03.2013 um 12:45 schrieb H. van der Meer :
> I find that in
>
> intro text
> \startnarrower
> narrow text
> \stopnarrower
> after text
>
> blank vertical space is inserted both before and after the narrower block.
> How can I avoid that?
I can’t see a space before/after the environment.
I find that in
intro text
\startnarrower
narrow text
\stopnarrower
after text
blank vertical space is inserted both before and after the narrower block.
How can I avoid that?
Hans van der Meer
___
If your questio
On 3/11/2013 6:13 PM, Sietse Brouwer wrote:
I don't understand what they whitespace does: I tried to test it with
this code, and changing the number did nothing.
for i=0,10 do
print(string.formatters("%wsietse",i))
end
for i=9,0,-1 do
print(string.formatters(&qu
Hi,
I chucked it in here, for lack of a better place.
http://wiki.contextgarden.net/String_Manipulation#String_formatter
I don't understand what they whitespace does: I tried to test it with
this code, and changing the number did nothing.
\starttext
\startluacode
x = 999
context(&q
boolean (logic) %l boolean
BOOLEAN %L boolean
whitespace %...w
More info can be found in cld-mkiv.pdf. There I also explain how to
create specific formatters and how to extend them. In the default
formatter there are two extensions that can be used as:
string.format
x27;t know why the chapter number font style is not obeyed. If I add
*numberstyle=dfont* in
*\setuphead*, then the font size is increased but the frame size has spurious
space at top and
bottom.
When I call the macro myself, there is a single whitespace before the chapter
heading (as can be
s
t;
> I don't know why the chapter number font style is not obeyed. If I add
> *numberstyle=dfont* in
> *\setuphead*, then the font size is increased but the frame size has spurious
> space at top and
> bottom.
>
> When I call the macro myself, there is a single whitesp
\setuphead*, then the font size is increased but the frame size has
spurious space at top and
bottom.
When I call the macro myself, there is a single whitespace before the
chapter heading (as can be
seen in the attached file).
I have gone through the wiki as much as possible and I think that I
Hi Wolfgang,
Am 30.01.2013 um 21:56 schrieb Wolfgang Schuster :
>
> Am 30.01.2013 um 10:00 schrieb Keith J. Schultz :
>
>> Hi Everybody,
>>
[snip, snip]
>> Also, it took me awhile to find the setupwhitespace command, because for me
>> whitespace can be
&g
r words there is no way, that I can find to globally set "standard"
> paragraphs!!
>
> The same goes for indenting of paragraphs. Yes, Yes there are the standard
> indenting commands.
>
> I feel though one should be able to use setupparagraphs for this.
>
> Also, it
s!!
The same goes for indenting of paragraphs. Yes, Yes there
are the standard indenting commands.
I feel though one should be able to use setupparagraphs
for this.
Also, it took me awhile to find the setupwhitespace
command, because for me whitespace can be
either horizontal or vertical. I think
ble to use setupparagraphs for this.
Also, it took me awhile to find the setupwhitespace command, because for me
whitespace can be
either horizontal or vertical. I think it would be better to rename it to
setupparagraphspacing or something
like that. Or at least define a synonym for it. This would
upwhitespace command, because for me
whitespace can be
either horizontal or vertical. I think it would be better to rename it to
setupparagraphspacing or something
like that. Or at least define a synonym for it. This would make things easier
for the casual or beginning user.
Maybe I am miss
antly, that catches ^ and _,
>> but what about whitespace etc. Isn;t there a true verbatim that I can use on
>> a macro like \currentcomponent? Something along the lines of
>> \verbatimexpand{\currentcomponent}?
>
> Untested: \filename{\currentcomponent}
Works. When outs
On Sun, 20 Jan 2013, Gerben Wierda wrote:
You can add the \nonknuthmode to your document which makes _ and ^ normal
characters for text mode.
Is that limited to a {}-scope? And more importantly, that catches ^ and
_, but what about whitespace etc. Isn;t there a true verbatim that I can
use
main file->component file
>>> \setupfootertexts[pagenumber][{\jobname->\currentcomponent}]
>>> \startproduct *
>>>\input ward \page
>>>\component bar
>>> \stopproduct
>>>
>>> And bar.tex:
>>>
>>
On 12/18/2012 9:20 AM, Marco Patzer wrote:
Hi,
the following two database examples produce different output due to
the white space between the field separator and the quotechar.
\usemodule [database]
\defineseparatedlist
[CSV]
[quotechar=",
before={\starttabulate[|l|l|]},
after=
Hi,
the following two database examples produce different output due to
the white space between the field separator and the quotechar.
\usemodule [database]
\defineseparatedlist
[CSV]
[quotechar=",
before={\starttabulate[|l|l|]},
after=\stoptabulate,
first=\NC,last=\NR,
left=,ri
On 23/10/12 21:19, Wolfgang Schuster wrote:
> Am 23.10.2012 um 20:54 schrieb Pablo Rodríguez :
>> [...]
>> But I would like to have different values for interlinear space and
>> between paragraphs.
>> [...]
>> But how can I set the interlinear space value for footnotes?
>
> \startsetups[setups:foo
Am 23.10.2012 um 20:54 schrieb Pablo Rodríguez :
> Hi there,
>
> I have the following settings for a document.
>
> \setupinterlinespace[line=3.2ex]
> \setupwhitespace[medium]
>
> But I would like to have diferent values for interlinear space and
> between paragraphs.
>
> strc-not.mkvi shows t
Hi there,
I have the following settings for a document.
\setupinterlinespace[line=3.2ex]
\setupwhitespace[medium]
But I would like to have diferent values for interlinear space and
between paragraphs.
strc-not.mkvi shows that the after option from \setupnotation does the
work with the space bet
no clue ... maybe an error in test.lua
>
> ... Have you seen the content of "Test.lua"? It just prints some text...
>
> When I downgraded Ctx to the previous installed version, it works...
>
> Lukas
>
>
> --
> Ing. Luk?? Proch?zka [mailto:l...@pontex.cz]
> Pontex
One issue is that the overlay overlaps the text space (reduces whitespace or
potentially overlaps letters). One could use a blank row with a black
background, but a row seems to have a minimum height of about 2mm. I
discovered the "boffset" key, which can be used with the overlay
hich is now used when omit the first argument of
\addressentry.
\usemodule[letter]
\setupletteroptions
[ bodyfont=calluna,
whitespace=line]
\defineaddressentry
[frodo]
[lastname={Beutlin},
firstname={Frodo},
address={Der Bühl\\Beutelsend/Hobbingen im Auenland},
1={Bilbo Beutlin},
2=
Am 20.09.2012 um 11:56 schrieb Marco Patzer :
> Hi,
>
> inside a TEXpage the tolerance and the whitespace settings are not
> applied. The whitespace can be set in a setup and the tolerance can
> be set directly with \spaceskip, but that seems a bit hackish.
>
> Is that in
Hi,
inside a TEXpage the tolerance and the whitespace settings are not
applied. The whitespace can be set in a setup and the tolerance can
be set directly with \spaceskip, but that seems a bit hackish.
Is that intended and is there a cleaner solution? Example:
\setuplayout [width=8cm
quot;^1
local _p_and= _p_spaces * P"and" * _p_spaces
function citator.get_author_list (rawaut)
if not stringfind(rawaut, "and") then return { rawaut } end
return split(rawaut, _p_and)
end
local get_author_list = citator.get_author_list
do
local wl = P{
s was with the default value of 2 lines as size for the
capital. If one indicates a greater number of lines, all of them but the
first
one are blank and the regular text continues after all that whitespace.
As I was not completely sure that my installation of ConTeXt was
unobjectable, I tried
u, that works, but the publisher decided to use glue binding
> to be able to put colored pages everywhere...
Sounds like they are meaning it ...
> Can you explain, what standardmakeup really does? I know it’s used
> in "free layout" pages.
In its natural state (like \startmakeup
Am 17.05.2012 um 17:46 schrieb Meer, H. van der:
> Macro \thinrules places vertical whitespace before the first of its lines. I
> would like to get rid of that one, but have no success in doint that.
> Usage is: \par\thinrules[..]\par
>
> Howto?
\starttext
a
\hrule
b
\strut
Macro \thinrules places vertical whitespace before the first of its lines. I
would like to get rid of that one, but have no success in doint that.
Usage is: \par\thinrules[..]\par
Howto?
H van der Meer
___
If
On 2012-04-22 17:16, Marco Pessotto wrote:
>
> Dear list,
>
> I use \(start|stop)lines[spaces=on] to typeset poetry, which seems the
> right thing to do to preserve eventual initial whitespace.
>
> Anyway, I encounter the following issues:
>
>
Dear list,
I use \(start|stop)lines[spaces=on] to typeset poetry, which seems the
right thing to do to preserve eventual initial whitespace.
Anyway, I encounter the following issues:
= cut here = %
\starttext
this is normal text.
\startlines[space=on]
this
Hi there,
I'm trying to add a whitespace before an xtable (just to be spaced as
any other paragraph).
I wanted to do that in the \setupxtable, before=\whitespace or
top=\whitespace don't seem to work.
Sorry, but which is the right option to do that?
Many thanks for your help,
Pabl
elax
\ifdim\ht\currentnoteins>\zeropoint
\endgraf
\ifvmode
\whitespace
\noteparameter\c!before
\fi
%\bgroup
%\setupalign[\noteparameter\c!align]%
\placenoterule % alleen in ..mode
%\par
%\egroup
+\ifvmod
goes right to the edge
of the page top or bottom without any whitespace.
Do you have to use textbackground (assuming, of course, that you are using
MkIV)? Regular backgrounds take care of top and bottom offsets:
\definebackground
[whatever]
[topoffset=1cm,
bottomoffset=1cm,
frame=on
of the page top or bottom without any whitespace.
Any ideas?
--
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com
signature.asc
Description: This is a digitally signed message part
e not checked why the extra space is being introduced, but what
Wolfgang meant was that
\setup[key=value]
is the same as
\setup
[
key=value,
]
but not the same as
\setup
[
key=value
]
Whitespace is significant in ConTeXt setups. The last style is equivalen
(2) How to define whitespacing?
>
>
> \starttext
>
> At the first itemization there should be no extra whitespace between the
> items. Whitespace and interlinespace should be the same: 0.4em. What can I do
> against the whitespace?
>
> […]
>
> And here I want to hav
no extra whitespace
between the items. Whitespace and interlinespace should be
the same: 0.4em. What can I do against the whitespace?
\setupwhitespace[0.4em]
\setupinterlinespace [0.4em]
\startitemize
\item aaa aaa aaa
aaa aaa
you need to do calculations yourself in order to be able to set the
> parameters correct ly.
>
> Check for the setuplayout command.
>
> \setuplayout
> [ backspace= left white+binding correction,
> width= text width which leaves enough whitespace at the right includ
he setuplayout command.
\setuplayout
[ backspace= left white+binding correction,
width= text width which leaves enough whitespace at the right including
some cut space,
topspace= top white including cut space,
height= text height including header and footer space, leaving en
ntained in a full page with lots of
surrounding whitespace. Note without textext doing framed's etc. there is no
problem. The problem arises when the pageheight and pagewidth come into play.
Hans van der Meer
below.
Thanks in advance.
Hans van der Meer
On 13 nov. 2011, at 14:57, Hans van der Meer wrote:
> I find that the placement of an equation number makes a difference on the
> amount of white after the equation. Should they both give the same amount of
> whitespace? Or is the differen
I find that the placement of an equation number makes a difference on the
amount of white after the equation. Should they both give the same amount of
whitespace? Or is the difference intentional? But then why?
I add a minimal example.
Hans van der Meer
% Test white after formula with and
Am 05.11.2011 um 16:12 schrieb Meer, H. van der:
> I find I get a fairly large whitespace after the formulas placed with:
> \placeformula\startformula <> \stopformula
> How can I reduce this? The wiki does not give a parameter description for
> \setupformulas. In the code I
I find I get a fairly large whitespace after the formulas placed with:
\placeformula\startformula <> \stopformula
How can I reduce this? The wiki does not give a parameter description for
\setupformulas. In the code I can only find some [distance=] parameter. But
using it with for e
Fixed.
> The display=yes option brings back the indentation, but it creates another
> problem: whitespace.
This is the purpose if the display option, it should either end the paragraph
or add a vertical skip which can be set with space before/
annotation module and the indenting
mechanism}
\stoptext
=
The display=yes option brings back the indentation, but it creates another
problem: whitespace.
Please advise, thnx in advance, and
Best wishes
Idris
--
Professor Idris Samawi Hamid, Editor-in-Chief
whitespace analysis determines what local
(nested) lexer to use .. at least that's what the basic lexing framework
does ... I'm still wondering if I should redo that part (I already
rewrote some of the lua code to be more efficien
not insert any whitespace.
It causes on the other hand, that the TOC entry is also hidden/gone. With the
second command the data are flushed and end up in the TOC.
Does it work without \placerawheaddata when you use “placehead=no” or
“placehead=empty” for section?
only the hidden does not
des the title completely and does not insert any
> whitespace. It causes on the other hand, that the TOC entry is also
> hidden/gone. With the second command the data are flushed and end up in the
> TOC.
Does it work without \placerawheaddata when you use “p
/white space inserted but still
keeping the entry in the TOC.
\setuphead
[section]
[placehead=hidden]
\setuptexttexts[{\placerawheaddata[section]}
The first setup hides the title completely and does not insert any whitespace.
It causes on the other hand, that the TOC entry is also hidden/gone
ed imho):
> some text.%
> \startmode[xyz]
>
> I think this is error prone as it is al too easy to forget the %. The
> situation here differs from the \doifmode-case. I tend to believe that the
> fact that the \startmode[] .. \stopmode construct invites one to separate the
&
Am 14.10.2011 um 00:56 schrieb Jan Heinen:
> With the change to [strut=no,offset=overlay] the result looks a litlebit
> better. Though there is still whitespace to the left and to the right.
>
> \definelayer[Kontaktdaten][x=50mm,y=150mm,width=30mm,height=40mm,state=start]
> %
With the change to [strut=no,offset=overlay] the result
looks a litlebit better. Though there is still whitespace to
the left and to the right.
\definelayer[Kontaktdaten][x=50mm,y=150mm,width=30mm,height=40mm,state=start]
% size is ignored!
\setupbackgrounds[paper][setups=ALayer,background
\startmode[xyz]
I think this is error prone as it is al too easy to forget the %. The situation
here differs from the \doifmode-case. I tend to believe that the fact that the
\startmode[] .. \stopmode construct invites one to separate the statements with
newlines (whitespace thus). Therefore I wo
"abc \doifmode{mode}{text} more text" can introduce extra
>>>> whitespace. I conclude therefore that there is no \ignorespaces at work
>>>> here. As a consequence the \doifmode does not completely disappear if mode
>>>> is not satisfied.
>>>&g
On 4 okt. 2011, at 20:44, Wolfgang Schuster wrote:
>
> Am 04.10.2011 um 20:37 schrieb Aditya Mahajan:
>
>> On Tue, 4 Oct 2011, Meer, H. van der wrote:
>>
>>> I find that "abc \doifmode{mode}{text} more text" can introduce extra
>>>
Am 04.10.2011 um 20:37 schrieb Aditya Mahajan:
> On Tue, 4 Oct 2011, Meer, H. van der wrote:
>
>> I find that "abc \doifmode{mode}{text} more text" can introduce extra
>> whitespace. I conclude therefore that there is no \ignorespaces at work
>> here. As a
On Tue, 4 Oct 2011, Meer, H. van der wrote:
I find that "abc \doifmode{mode}{text} more text" can introduce extra
whitespace. I conclude therefore that there is no \ignorespaces at work here. As a
consequence the \doifmode does not completely disappear if mode is not satisfie
Am 04.10.2011 um 20:19 schrieb Meer, H. van der:
> I find that "abc \doifmode{mode}{text} more text" can introduce extra
> whitespace. I conclude therefore that there is no \ignorespaces at work here.
> As a consequence the \doifmode does not completely disappear if mode
I find that "abc \doifmode{mode}{text} more text" can introduce extra
whitespace. I conclude therefore that there is no \ignorespaces at work here.
As a consequence the \doifmode does not completely disappear if mode is not
satisfied.
Is this intentional or should this behaviour
ge:
> >> >
> >> > http://wiki.contextgarden.net/Fonts_in_LuaTeX
> >> > and got the two fonts listed in the font database.
> >> >
> >> > I put the following in my MKIV context file:
> >> > ...
> >> > \u
use simplefonts to use Minion as the base font.
>> >> > I ran the various commands described in the Wiki page:
>> >> >
>> >> > http://wiki.contextgarden.net/Fonts_in_LuaTeX
>> >> > and got the two fonts listed in the font database.
>&
>> >
> >> > http://wiki.contextgarden.net/Fonts_in_LuaTeX
> >> > and got the two fonts listed in the font database.
> >> >
> >> > I put the following in my MKIV context file:
> >> > ...
> >> > \usemodule[
ot the two fonts listed in the font database.
>> >
>> > I put the following in my MKIV context file:
>> > ...
>> > \usemodule[simplefonts] % load the module
>> > \setmainfont[minionproregular] %
>> >
>> > %\whitespace[line]
>> >
>> > \uset
> \usemodule[simplefonts] % load the module
> > \setmainfont[minionproregular] %
> >
> > %\whitespace[line]
> >
> > \usetypescript[serif,sans][hanging][pure]
> > \setupalign[hanging]
> > \setupbodyfont[minionproregular,14pt]
>
> To
two fonts listed in the font database.
>> >
>> > I put the following in my MKIV context file:
>> > ...
>> > \usemodule[simplefonts] % load the module
>> > \setmainfont[minionproregular] %
>> >
>> > %\whitespace[line]
>>
t; \usemodule[simplefonts] % load the module
> > \setmainfont[minionproregular] %
> >
> > %\whitespace[line]
> >
> > \usetypescript[serif,sans][hanging][pure]
> > \setupalign[hanging]
> > \setupbodyfont[minionproregular,14pt]
> > ...
> > Now I ge
page:
>
> http://wiki.contextgarden.net/Fonts_in_LuaTeX
> and got the two fonts listed in the font database.
>
> I put the following in my MKIV context file:
> ...
> \usemodule[simplefonts] % load the module
> \setmainfont[minionproregular] %
>
> %\whitespace[line]
>
> \usety
301 - 400 of 811 matches
Mail list logo
