* where to break a long header
@ 2021-06-05 5:59 Sandra Snan
2021-06-05 6:16 ` denis.maier
0 siblings, 1 reply; 7+ messages in thread
From: Sandra Snan @ 2021-06-05 5:59 UTC (permalink / raw)
To: ntg-context
I had an unsually long header and it didn't look great:
https://ellen.idiomdrottning.org/sateotc1.png
A crlf fixes it:
https://ellen.idiomdrottning.org/sateotc2.png
But then that shows up in the table of contents so that's not a good
solution. What is the best practice for this situation?
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: where to break a long header
2021-06-05 5:59 where to break a long header Sandra Snan
@ 2021-06-05 6:16 ` denis.maier
2021-06-05 6:24 ` Sandra Snan
2021-06-05 8:14 ` Wolfgang Schuster
0 siblings, 2 replies; 7+ messages in thread
From: denis.maier @ 2021-06-05 6:16 UTC (permalink / raw)
To: ntg-context
\startsection[title={A very \\ long title},list={A very long title}]
________________________________________
Von: ntg-context <ntg-context-bounces@ntg.nl> im Auftrag von Sandra Snan <sandra.snan@idiomdrottning.org>
Gesendet: Samstag, 5. Juni 2021 07:59:33
An: ntg-context@ntg.nl
Betreff: [NTG-context] where to break a long header
I had an unsually long header and it didn't look great:
https://ellen.idiomdrottning.org/sateotc1.png
A crlf fixes it:
https://ellen.idiomdrottning.org/sateotc2.png
But then that shows up in the table of contents so that's not a good
solution. What is the best practice for this situation?
___________________________________________________________________________________
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
___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: where to break a long header
2021-06-05 6:16 ` denis.maier
@ 2021-06-05 6:24 ` Sandra Snan
2021-06-05 8:14 ` Wolfgang Schuster
1 sibling, 0 replies; 7+ messages in thread
From: Sandra Snan @ 2021-06-05 6:24 UTC (permalink / raw)
To: denis.maier, ntg-context
Thank you so much! That was awesome!
That was the missing puzzle piece: the book is now perfect!
<denis.maier@ub.unibe.ch> writes:
> \startsection[title={A very \\ long title},list={A very long title}]
> ________________________________________
> Von: ntg-context <ntg-context-bounces@ntg.nl> im Auftrag von Sandra Snan <sandra.snan@idiomdrottning.org>
> Gesendet: Samstag, 5. Juni 2021 07:59:33
> An: ntg-context@ntg.nl
> Betreff: [NTG-context] where to break a long header
>
> I had an unsually long header and it didn't look great:
>
> https://ellen.idiomdrottning.org/sateotc1.png
>
> A crlf fixes it:
>
> https://ellen.idiomdrottning.org/sateotc2.png
>
> But then that shows up in the table of contents so that's not a good
> solution. What is the best practice for this situation?
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: where to break a long header
2021-06-05 6:16 ` denis.maier
2021-06-05 6:24 ` Sandra Snan
@ 2021-06-05 8:14 ` Wolfgang Schuster
2021-06-06 13:34 ` Steffen Wolfrum
1 sibling, 1 reply; 7+ messages in thread
From: Wolfgang Schuster @ 2021-06-05 8:14 UTC (permalink / raw)
To: mailing list for ConTeXt users
denis.maier@ub.unibe.ch schrieb am 05.06.2021 um 08:16:
> \startsection[title={A very \\ long title},list={A very long title}]
Be careful with spaces before and after \\. In the table of contents \\
is converted to a space and in the worst case you get three spaces
instead of one.
\starttext
\placecontent
\section{First section \\ with a line break}
\section{Second section\\ with a line break}
\section{Third section \\with a line break}
\section{Fourth section\\with a line break}
\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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: where to break a long header
2021-06-05 8:14 ` Wolfgang Schuster
@ 2021-06-06 13:34 ` Steffen Wolfrum
2021-06-06 20:02 ` Hans Hagen
0 siblings, 1 reply; 7+ messages in thread
From: Steffen Wolfrum @ 2021-06-06 13:34 UTC (permalink / raw)
To: mailing list for ConTeXt users
This minimal I ran with «ConTeXt ver: 2021.06.04 17:28 MKI» and got two PDF files:
One «test.pdf» as expected and one called «test-pdf-keep.pdf».
What's the reason behind this double feature?
Steffen
> Am 05.06.2021 um 10:14 schrieb Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>:
>
> denis.maier@ub.unibe.ch schrieb am 05.06.2021 um 08:16:
>> \startsection[title={A very \\ long title},list={A very long title}]
>
> Be careful with spaces before and after \\. In the table of contents \\ is converted to a space and in the worst case you get three spaces instead of one.
>
> \starttext
>
> \placecontent
>
> \section{First section \\ with a line break}
>
> \section{Second section\\ with a line break}
>
> \section{Third section \\with a line break}
>
> \section{Fourth section\\with a line break}
>
> \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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: where to break a long header
2021-06-06 13:34 ` Steffen Wolfrum
@ 2021-06-06 20:02 ` Hans Hagen
2021-06-07 11:19 ` Steffen Wolfrum
0 siblings, 1 reply; 7+ messages in thread
From: Hans Hagen @ 2021-06-06 20:02 UTC (permalink / raw)
To: mailing list for ConTeXt users, Steffen Wolfrum
On 6/6/2021 3:34 PM, Steffen Wolfrum wrote:
> This minimal I ran with «ConTeXt ver: 2021.06.04 17:28 MKI» and got two PDF files:
> One «test.pdf» as expected and one called «test-pdf-keep.pdf».
>
> What's the reason behind this double feature?
see thread of a few days ago
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: where to break a long header
2021-06-06 20:02 ` Hans Hagen
@ 2021-06-07 11:19 ` Steffen Wolfrum
0 siblings, 0 replies; 7+ messages in thread
From: Steffen Wolfrum @ 2021-06-07 11:19 UTC (permalink / raw)
To: Hans Hagen; +Cc: mailing list for ConTeXt users
> Am 06.06.2021 um 22:02 schrieb Hans Hagen <j.hagen@xs4all.nl>:
>
> On 6/6/2021 3:34 PM, Steffen Wolfrum wrote:
>> This minimal I ran with «ConTeXt ver: 2021.06.04 17:28 MKI» and got two PDF files:
>> One «test.pdf» as expected and one called «test-pdf-keep.pdf».
>> What's the reason behind this double feature?
> see thread of a few days ago
sure, just overlooked it (or rather my search didn't match).
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2021-06-07 11:19 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-05 5:59 where to break a long header Sandra Snan
2021-06-05 6:16 ` denis.maier
2021-06-05 6:24 ` Sandra Snan
2021-06-05 8:14 ` Wolfgang Schuster
2021-06-06 13:34 ` Steffen Wolfrum
2021-06-06 20:02 ` Hans Hagen
2021-06-07 11:19 ` Steffen Wolfrum
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).