Re: [NTG-context] Different behaviour of textcommand (setupcaption+startplacefigure)

2020-03-29 Thread Tomas Hala
Sun, Mar 29, 2020 ve 08:24:53PM +0200 Wolfgang Schuster napsal(a):
# Tomas Hala schrieb am 29.03.2020 um 19:55:
# >Hi all,
# >
# >I noticed the difference in behaviour of textcommand which depends
# >on the location: for top, bottom and page the \crlf (see MWE) is applied
# >while for the left and right not even if other values (\red, any-text)
# >are used as expecterd.
# >
# >How could I activate the textcommand=\crlf for location=right?
# >(The line break appears only the width of the figure becomes too small.)
# >
# >Tested with TL2019 and with version from Mar 6, 2020.
#
# 1. The cow figure is a PDF file.

Typo during cleaning the MWE, sorry.

# 2. Use the "spaceinbetween" key to add a break after the label + counter.

Unfortunately, spaceinbetween does not work with "right", too, I tried it 
before.

# 3. Captions use "width=fit" as default setting which produces a
# horizontal box for your side float which ignores the \crlf command,
# when you change the setting to "width=max" in combination with
# "align=middle" the title start on a new line.

Thank you for the explanation, now it is clear.
And for the piece of code, too.

Best wishes,

Tomáš

#
# \setupexternalfigures
#   [location=default]
#
# \setupcaption
#   [figure]
#   [spaceinbetween=none,
# width=max,
# align=middle]
#
# \starttext
#
# \startplacefigure[location=top,title=Cow]
#   \externalfigure[cow][height=4cm]
# \stopplacefigure
# \samplefile{knuth}
#
# \startplacefigure[location=right,title=Cow]
#   \externalfigure[cow][height=4cm]
# \stopplacefigure
# \samplefile{knuth}
#
# \stoptext
#
# Wolfgang

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Different behaviour of textcommand (setupcaption+startplacefigure)

2020-03-29 Thread Wolfgang Schuster

Tomas Hala schrieb am 29.03.2020 um 19:55:

Hi all,

I noticed the difference in behaviour of textcommand which depends
on the location: for top, bottom and page the \crlf (see MWE) is applied
while for the left and right not even if other values (\red, any-text)
are used as expecterd.

How could I activate the textcommand=\crlf for location=right?
(The line break appears only the width of the figure becomes too small.)

Tested with TL2019 and with version from Mar 6, 2020.


1. The cow figure is a PDF file.

2. Use the "spaceinbetween" key to add a break after the label + counter.

3. Captions use "width=fit" as default setting which produces a 
horizontal box for your side float which ignores the \crlf command, when 
you change the setting to "width=max" in combination with "align=middle" 
the title start on a new line.


\setupexternalfigures
  [location=default]

\setupcaption
  [figure]
  [spaceinbetween=none,
width=max,
align=middle]

\starttext

\startplacefigure[location=top,title=Cow]
  \externalfigure[cow][height=4cm]
\stopplacefigure
\samplefile{knuth}

\startplacefigure[location=right,title=Cow]
  \externalfigure[cow][height=4cm]
\stopplacefigure
\samplefile{knuth}

\stoptext

Wolfgang
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] Different behaviour of textcommand (setupcaption+startplacefigure)

2020-03-29 Thread Tomas Hala
Hi all, 

I noticed the difference in behaviour of textcommand which depends
on the location: for top, bottom and page the \crlf (see MWE) is applied
while for the left and right not even if other values (\red, any-text)
are used as expecterd.

How could I activate the textcommand=\crlf for location=right?
(The line break appears only the width of the figure becomes too small.)

Tested with TL2019 and with version from Mar 6, 2020.

Best wishes,

Tomáš


%% MWE:

\starttext

\setupcaption[figure][textcommand=\crlf]
\startplacefigure[location=top,title=Cow]
  \externalfigure[cow.jpg][height=4cm]
\stopplacefigure
\input knuth

\setupcaption[figure][textcommand=\crlf]
\startplacefigure[location=right,title=Cow]
  \externalfigure[cow.jpg][height=4cm]
\stopplacefigure
\input knuth

\stoptext
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


[NTG-context] Different behaviour

2010-03-21 Thread Alain Delmotte

Hi!

I did find a different behaviour for the same command.
In:
1] \starttext

2] \defineenumeration

3] [remark]

4] [way=bysection,location=top,

5]  text=Remark,

6]  inbetween=\blank,

7]  after=\blank]

8] \remark In the early medieval times Hasselt was a place of 
pilgrimage. %point 1


9] \subremark Nowadays the {\em Heilige Stede} is closed again. %point 2

10] \subremark Nowadays the {\em Heilige Stede} is closed again. %point 3

11]
12] Remarquer la possibilité d'avoir des sous-numéros.

13]
14] \remark In the early medieval times Hasselt was a place of 
pilgrimage. %point 4


15]
16] \subremark Nowadays the {\em Heilige Stede} is closed again. %point 5

17]
18] Aussi les \type{\startremark...\stopremark}.

19]
20] \remark In the early medieval times Hasselt was a place of 
pilgrimage. %point 6


21]
22] \subremark Nowadays the {\em Heilige Stede} is closed again. %point 7

23]
24] \subremark Nowadays the {\em Heilige Stede} is closed again. %point 8

25]
26] \stoptext

This works (no empry line before points 1, 2, 3; empty lines before the 
others)
If I suppress the line before any of the points 4, 5, 6, 7 or 8 I get an 
error Runaway argument for the line of point 8!


Suppressing *after*  point 3 or point 5 also gives an error.


In fact, it looks like there should be an empty line after the \remark 
or \subremark, but not for the first group!



(NB. I did add the line number to avoid misunderstanding going from a 
Windows CRLF to other CR or LF)



Alain



___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] Different behaviour Windows vs. Linux

2003-07-10 Thread Willi Egger

Hi Jens,
 
> shouldn't it be named cont-sys.tex?

Indeed :-}
Thanks
Willi

___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] Different behaviour Windows vs. Linux

2003-07-07 Thread Jens-Uwe Morawski
On Mon, 7 Jul 2003 20:03:04 +0200
"Willi Egger" <[EMAIL PROTECTED]> wrote:

> Hello everybody,
> 
> When I compile a MyWay (uses s-mag-*.tex) under Windows everything runs
> smoothly.
> When I compile the same file under Linux, where I got also a texlive7 tree
> installed, the \setupencoding[texnansi] is not read from the cont-sys.ini,

shouldn't it be named cont-sys.tex?

Jens
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context


[NTG-context] Different behaviour Windows vs. Linux

2003-07-07 Thread Willi Egger
Hello everybody,

When I compile a MyWay (uses s-mag-*.tex) under Windows everything runs
smoothly.
When I compile the same file under Linux, where I got also a texlive7 tree
installed, the \setupencoding[texnansi] is not read from the cont-sys.ini,
though the file contains this statement. - As a consequence Context fails
because it is looking for ec-uplr8a instead of texnansi-uplr8a.

For the time being I edited the s-mag-00.tex and replaced the
\usetypescript[palatino][\defaultencoding] by
\usetypescript[palatino][texnansi], which solves the hick.

Is this a specific Linux issue?

Cheers Willi


___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context