On Tue, 27 Nov 2012 08:43:25 +0100, Procházka Lukáš Ing. - Pontex s. r. o.
wrote:
Is 'toppath:' prefix working?
... My observation so far:
'toppath' works with \component, so if one needs to include a file, it's better
to include it via:
\component file.tex
where 'topttath' works as well
Am 27.11.2012 22:39, schrieb ntg-context-requ...@ntg.nl:
(just run your docs with \setupalign[verytolerant,stretch] and you're
okay in most cases)
That is not possible, because I want to have very nice word-distances,
and I want the margin-runs to be there, to correct them myselve
manually. So
On 11/28/2012 12:39 AM, Mojca Miklavec wrote:
On Wed, Nov 28, 2012 at 12:20 AM, Martin Schröder wrote:
2012/11/27 Mojca Miklavec:
What exactly do you mean with a canonical way? The most reliable way
How about delivering a new version through tlcontrib?
Doable***, but a new beta is usually r
On Tue, 2012-11-27 at 08:06 +0100, Wolfgang Schuster wrote:
> Better define a complete set which includes also serif and sans.
> Afterwards you have to enable it with \setupbodyfont[…].
Hey Wolfgang. The reason why I hadn't done that is I didn't want to
overwrite the selected typeface I was using
On Wed, Nov 28, 2012 at 12:20 AM, Martin Schröder wrote:
> 2012/11/27 Mojca Miklavec:
>> What exactly do you mean with a canonical way? The most reliable way
>
> How about delivering a new version through tlcontrib?
Doable***, but a new beta is usually released several times per day
(and sometimes
2012/11/27 Mojca Miklavec :
> What exactly do you mean with a canonical way? The most reliable way
How about delivering a new version through tlcontrib?
Best
Martin
___
If your question is of interest to others as
On 11/27/2012 11:06 PM, Hans Hagen wrote:
>
> you probably need to copy mtxrun.lua to mtxrun in some bin path
Yes, that appears to be the culprit - after overwriting the "old" mtxrun
with the fresh copy, it seems to work.
On 11/27/2012 11:07 PM, Mojca Miklavec wrote:> What exactly do you mean
wi
On 11/27/2012 11:07 PM, Mojca Miklavec wrote:
On Tue, Nov 27, 2012 at 10:46 PM, Thomas A. Schmitz wrote:
Hi,
is there a canonical way to update texlive so it runs the latest context
beta?
What exactly do you mean with a canonical way? The most reliable way
could be creating a tar.xz package f
On 11/27/2012 10:58 PM, Wolfgang Schuster wrote:
Am 27.11.2012 um 22:43 schrieb Pablo Rodríguez :
On 27/11/12 22:34, Wolfgang Schuster wrote:
Am 27.11.2012 um 20:34 schrieb Pablo Rodríguez :
[...]
Probably my font is newer (from
http://ftp.gnu.org/gnu/freefont/freefont-ttf-20120503.zip).
I
On Tue, Nov 27, 2012 at 10:46 PM, Thomas A. Schmitz wrote:
> Hi,
>
> is there a canonical way to update texlive so it runs the latest context
> beta?
What exactly do you mean with a canonical way? The most reliable way
could be creating a tar.xz package from the beta and install that one,
but it w
On 11/27/2012 10:46 PM, Thomas A. Schmitz wrote:
Hi,
is there a canonical way to update texlive so it runs the latest context
beta? From time to time, I'd like to be sure that I can run texlive as
well. I tried unzipping the latest zip file in texlive/texmf-local,
running mtxrun --generate and c
Am 27.11.2012 um 22:43 schrieb Pablo Rodríguez :
> On 27/11/12 22:34, Wolfgang Schuster wrote:
>> Am 27.11.2012 um 20:34 schrieb Pablo Rodríguez :
>> [...]
>>> Probably my font is newer (from
>>> http://ftp.gnu.org/gnu/freefont/freefont-ttf-20120503.zip).
>>>
>>> I think there is no file clash,
On 11/27/2012 8:34 PM, Pablo Rodríguez wrote:
On 27/11/12 18:56, Hans Hagen wrote:
On 11/27/2012 6:36 PM, Pablo Rodríguez wrote:
I see lots of kerns in:
\starttext
\startTEXpage[offset=10pt]
\definedfont[file:freeserif.ttf*default] \showfontkerns \input ward
\stopTE
Hi,
is there a canonical way to update texlive so it runs the latest context
beta? From time to time, I'd like to be sure that I can run texlive as
well. I tried unzipping the latest zip file in texlive/texmf-local,
running mtxrun --generate and context --make, but I get
texmf-local/scripts/conte
On 27/11/12 22:34, Wolfgang Schuster wrote:
> Am 27.11.2012 um 20:34 schrieb Pablo Rodríguez :
> [...]
>> Probably my font is newer (from
>> http://ftp.gnu.org/gnu/freefont/freefont-ttf-20120503.zip).
>>
>> I think there is no file clash, since ConTeXt standalone doesn't provide the
>> font
>
> T
On 11/27/2012 8:34 PM, Pablo Rodríguez wrote:
> Probably my font is newer (from
http://ftp.gnu.org/gnu/freefont/freefont-ttf-20120503.zip).
i got it from:
http://www.fonts2u.com/
At least on my ConTeXt installation, OpenType features aren't enabled by
default.
hard to believe
Hans
-
Am 27.11.2012 um 20:34 schrieb Pablo Rodríguez :
> On 27/11/12 18:56, Hans Hagen wrote:
>> On 11/27/2012 6:36 PM, Pablo Rodríguez wrote:
>> I see lots of kerns in:
>>
>> \starttext
>> \startTEXpage[offset=10pt]
>> \definedfont[file:freeserif.ttf*default] \show
On 11/27/2012 8:22 PM, "H. Özoguz" wrote:
Am 27.11.2012 18:37, schrieb ntg-context-requ...@ntg.nl:
blue: natural width is larger than hsize
green: natural width is smaller than hsize
magenta: natural width is smaller than hsize (raggedright)
cyan: natural width is smaller than hsize (raggedleft)
On 27/11/12 18:56, Hans Hagen wrote:
> On 11/27/2012 6:36 PM, Pablo Rodríguez wrote:
> I see lots of kerns in:
>
> \starttext
>\startTEXpage[offset=10pt]
>\definedfont[file:freeserif.ttf*default] \showfontkerns \input
> ward
>\stopTEXpage
>>>
Am 27.11.2012 18:37, schrieb ntg-context-requ...@ntg.nl:
blue: natural width is larger than hsize
green: natural width is smaller than hsize
magenta: natural width is smaller than hsize (raggedright)
cyan: natural width is smaller than hsize (raggedleft)
yellow: natural width is smaller than hsiz
On 11/27/2012 6:36 PM, Pablo Rodríguez wrote:
On 27/11/12 18:04, Hans Hagen wrote:
I see lots of kerns in:
\starttext
\startTEXpage[offset=10pt]
\definedfont[file:freeserif.ttf*default] \showfontkerns \input ward
\stopTEXpage
\stoptext
Well, I don't see any kern.
at
On Tue, Nov 27, 2012 at 6:46 PM, Pablo Rodríguez wrote:
> On 27/11/12 18:42, luigi scarso wrote:
>> On Tue, Nov 27, 2012 at 6:36 PM, Pablo Rodríguez wrote:
>>> \starttext
>> \startTEXpage[offset=10pt]
>> \definedfont[file:freeserif.ttf*default] \showfontkerns \input
>
On 27/11/12 18:42, luigi scarso wrote:
> On Tue, Nov 27, 2012 at 6:36 PM, Pablo Rodríguez wrote:
>> \starttext
> \startTEXpage[offset=10pt]
> \definedfont[file:freeserif.ttf*default] \showfontkerns \input
> ward
> \stopTEXpage
> \stoptext
> this is m
On Tue, Nov 27, 2012 at 6:36 PM, Pablo Rodríguez wrote:
> \starttext
\startTEXpage[offset=10pt]
\definedfont[file:freeserif.ttf*default] \showfontkerns \input
ward
\stopTEXpage
\stoptext
>>>
this is mine
--
luigi
test-3.pdf
Description: Adobe PDF
On 27/11/12 18:04, Hans Hagen wrote:
>>> I see lots of kerns in:
>>>
>>> \starttext
>>> \startTEXpage[offset=10pt]
>>> \definedfont[file:freeserif.ttf*default] \showfontkerns \input
>>> ward
>>> \stopTEXpage
>>> \stoptext
>>
>> Well, I don't see any kern.
>
> attached
Mine
On 27/11/12 00:11, Wolfgang Schuster wrote:
> [...]
> Is there a difference between the two lines?
>
> \usemodule[simplefonts]
> \setmainfont[FreeSerif]
> \starttext
> \showfontkerns
> dadedidodufafefifofufrflftlalelilolutatetitotu\par
> {\definedfont[file:serif*default]dadedidodufafefifofufrflftl
On 26/11/12 23:46, Hans Hagen wrote:
> [...]
> Sure, kern tables are used and are quite valid in open type as well
> (open type includes truetype).
>
> I see lots of kerns in:
>
> \starttext
> \startTEXpage[offset=10pt]
> \definedfont[file:freeserif.ttf*default] \showfontkerns \inp
On 11/27/2012 11:19 AM, Sietse Brouwer wrote:
* The log, like Luigi mentions, reports the source location of
overfull hboxes. This might help you at least a bit in finding the
output page.
Overfull \hbox (15.80962pt too wide) in paragraph at lines 1--25
\3>modern-designsize-12pt-rm-tf-0--0 par-a
Am 27.11.2012 um 12:06 schrieb H. Özoguz :
> Hi there,
>
> today many questions :)
>
> Look at this:
>
> \starttext
> \completecontent
> \section[
> title={A very long title\par with a formatting in it}
> ]
> \stoptext
>
> I have a case, where I want to have a line-break (\par) in the title i
Hi there,
today many questions :)
Look at this:
\starttext
\completecontent
\section[
title={A very long title\par with a formatting in it}
]
\stoptext
I have a case, where I want to have a line-break (\par) in the title in
the text (to avoid hyphenation) - but not in the index of cont
Hans wrote:
> it's more the reverse ... some flag give more info when --all is given i.e.
> --list triggers an action
Oh, then my text would be misleading. How about using this as the help text?
--all show all found instances
+ --all show all found instances (comb
Huseyin wrote:
>> Is there a command like "\showallmarginruns", which gives something like
>> this: "Margin runs on p. 34,67,101,145,204,298" - it may use somehow the
>> blocks of \version[temporary], that would be perfect for me.
>>
>> Could I make clear, what I am looking for (sorry for my leck o
Am 27.11.2012 10:36, schrieb ntg-context-requ...@ntg.nl:
A better solution is to provide a shorter text with the ?marking? key from
\startsection.
Thanks Wolfgang and Luigi, I did not know that, that is of course the
easiest and best solution!
___
Am 27.11.2012 um 10:36 schrieb luigi scarso :
> On Tue, Nov 27, 2012 at 10:24 AM, Wolfgang Schuster
> wrote:
>>
>> Am 27.11.2012 um 10:11 schrieb luigi scarso :
>>
>>> On Tue, Nov 27, 2012 at 10:04 AM, "H. Özoguz" wrote:
\setupheadertexts
[] [{\getmarking[section]}]
On Tue, Nov 27, 2012 at 10:24 AM, Wolfgang Schuster
wrote:
>
> Am 27.11.2012 um 10:11 schrieb luigi scarso :
>
>> On Tue, Nov 27, 2012 at 10:04 AM, "H. Özoguz" wrote:
>>> \setupheadertexts
>>>
>>> [] [{\getmarking[section]}]
>>>
>>> [][]
>>>
>>>
>>> \starttext
>>>
>>> \section{This is a very long
... I'd need to refer to a file from within a file, not in via '--path'
option...
My case is more complicated - a file is included from more other files in
various directory levels.
BTW: I was also thinking about \processedfile
(http://wiki.contextgarden.net/Command/processedfile) and about s
Am 27.11.2012 um 10:11 schrieb luigi scarso :
> On Tue, Nov 27, 2012 at 10:04 AM, "H. Özoguz" wrote:
>> \setupheadertexts
>>
>> [] [{\getmarking[section]}]
>>
>> [][]
>>
>>
>> \starttext
>>
>> \section{This is a very long section title, and so, clearly, it does not fit
>> in one line, defin
On Tue, Nov 27, 2012 at 10:04 AM, "H. Özoguz" wrote:
> \setupheadertexts
>
> [] [{\getmarking[section]}]
>
> [][]
>
>
> \starttext
>
> \section{This is a very long section title, and so, clearly, it does not fit
> in one line, definitely not, absolutely no change. Without line break not
> possible
How to allow line break in headers, to achieve not margined header-texts?
\setupheadertexts
[] [{\getmarking[section]}]
[][]
\starttext
\section{This is a very long section title, and so, clearly, it does not
fit in one line, definitely not, absolutely no change. Without line
On 11/27/2012 8:43 AM, Procházka Lukáš Ing. - Pontex s. r. o. wrote:
Hello,
there was a discussion about 'toppath' or 'pathrelativetome'.
Is 'toppath:' prefix working?
Or what other way is to refer to the path of the current file (i.e. the
file I'm referring from)?
The following code doesn't
40 matches
Mail list logo
