Re: [NTG-context] Suboptimal German hyphenation
Am 29.09.22 um 06:10 schrieb Wolfgang Schuster via ntg-context: Max Chernoff via ntg-context schrieb am 29.09.2022 um 02:17: Babel/ngerman sets left/righthyphenmin to 2/2, but ConTeXt sets those to 3/3 for German. (The English default is 2/3). I don't speak German so I have no idea which is correct, but you can get the same behaviour in ConTeXt with: \mainlanguage[de] \lefthyphenmin=2 \righthyphenmin=2 You can use \setuplanguage to change the values. \setuplanguage [de] [ lefthyphenmin=2, righthyphenmin=2] Thank you, Leah, Max and Wolfgang! I changed that immediately in all of my ongoing projects, but I don’t think we should change the default after all these years. published: https://literatur.social/@fiee/109079837141552277 Hraban ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Suboptimal German hyphenation
Max Chernoff via ntg-context schrieb am 29.09.2022 um 02:17:
Hi Leah,
I was typesetting some German text on a narrow page when I discovered
the justification wasn't as good as expected. I think I tracked this
down to differences in hyphenation points, namely, ConTeXt has fewer:
\starttext
\language[de]
\showhyphens{Zusammenhang}
\showhyphens{anderswo}
\showhyphens{anderswoher}
\stoptext
This shows
languages > hyphenation > show: Zusam[-||]men[-||]hang
languages > hyphenation > show: anderswo
languages > hyphenation > show: anders[-||]wo[-||]her
Babel/ngerman sets left/righthyphenmin to 2/2, but ConTeXt sets those to
3/3 for German. (The English default is 2/3). I don't speak German so I
have no idea which is correct, but you can get the same behaviour in
ConTeXt with:
\mainlanguage[de]
\lefthyphenmin=2
\righthyphenmin=2
You can use \setuplanguage to change the values.
\setuplanguage
[de]
[ lefthyphenmin=2,
righthyphenmin=2]
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Suboptimal German hyphenation
Max Chernoff via ntg-context writes:
> Hi Leah,
>
>> I was typesetting some German text on a narrow page when I discovered
>> the justification wasn't as good as expected. I think I tracked this
>> down to differences in hyphenation points, namely, ConTeXt has fewer:
>>
>> \starttext
>> \language[de]
>> \showhyphens{Zusammenhang}
>> \showhyphens{anderswo}
>> \showhyphens{anderswoher}
>> \stoptext
>>
>> This shows
>> languages > hyphenation > show: Zusam[-||]men[-||]hang
>> languages > hyphenation > show: anderswo
>> languages > hyphenation > show: anders[-||]wo[-||]her
>
> Babel/ngerman sets left/righthyphenmin to 2/2, but ConTeXt sets those to
> 3/3 for German. (The English default is 2/3). I don't speak German so I
> have no idea which is correct, but you can get the same behaviour in
> ConTeXt with:
Perfect, thanks!
Many prefixes have two letters, so changing the default may be
reasonable. But there are more experienced German typographers on
this list who can chime in.
--
Leah Neukirchenhttps://leahneukirchen.org
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Suboptimal German hyphenation
Hi Leah,
> I was typesetting some German text on a narrow page when I discovered
> the justification wasn't as good as expected. I think I tracked this
> down to differences in hyphenation points, namely, ConTeXt has fewer:
>
> \starttext
> \language[de]
> \showhyphens{Zusammenhang}
> \showhyphens{anderswo}
> \showhyphens{anderswoher}
> \stoptext
>
> This shows
> languages > hyphenation > show: Zusam[-||]men[-||]hang
> languages > hyphenation > show: anderswo
> languages > hyphenation > show: anders[-||]wo[-||]her
Babel/ngerman sets left/righthyphenmin to 2/2, but ConTeXt sets those to
3/3 for German. (The English default is 2/3). I don't speak German so I
have no idea which is correct, but you can get the same behaviour in
ConTeXt with:
\mainlanguage[de]
\lefthyphenmin=2
\righthyphenmin=2
\starttext
\showhyphens{Zusammenhang}
\showhyphens{anderswo}
\showhyphens{anderswoher}
\stoptext
which gives:
languages > hyphenation > show: Zu[-||]sam[-||]men[-||]hang
languages > hyphenation > show: an[-||]ders[-||]wo
languages > hyphenation > show: an[-||]ders[-||]wo[-||]her
-- Max
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] LMTX incompatibility in \meaning breaks TikZ, other minor issues
Hans Hagen via ntg-context writes:
>> After a bunch of debugging, it turns out that LMTX breaks the TikZ
>> 'quotes'
>> library, which works using code ala:
>> \def\tikz@enable@node@quotes{%
>>\pgfkeyssetvalue{/handlers/first char syntax/the character
>> "}{\tikz@quote@parser}%
>>\let\tikz@quotes@as\tikz@node@quotes@as%
>> }
>> The last part of the /-key is derived from \meaning, but in LMTX,
>> \meaning" is "the character U+0022 'quotation mark'"
>> and thus the key cannot be found.
>> I have patched TikZ for now to match for this alternate string too.
>
> a bit weird way to test a key .. maybe you can compare to
>
> \edef\ThatQuote{\meaning/}
>
> using \ifx
>
>> But perhaps it would be better for compatibility to agree with the
>> original TeX \meaning strings for the 7-bit ASCII subset at least.
>
> too messy when want to parse
To follow up on this: I have upstreamed patches to tikz and tikz-cd to
use the dynamic output of \meaning instead of hardcoding.
I'm not sure who maintains the t-tikz module, but if it gets updated
at some point the fix should be in.
--
Leah Neukirchenhttps://leahneukirchen.org/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
[NTG-context] Suboptimal German hyphenation
Hi,
I was typesetting some German text on a narrow page when I discovered
the justification wasn't as good as expected. I think I tracked this
down to differences in hyphenation points, namely, ConTeXt has fewer:
\starttext
\language[de]
\showhyphens{Zusammenhang}
\showhyphens{anderswo}
\showhyphens{anderswoher}
\stoptext
This shows
languages > hyphenation > show: Zusam[-||]men[-||]hang
languages > hyphenation > show: anderswo
languages > hyphenation > show: anders[-||]wo[-||]her
Now with LaTeX and Babel:
\documentclass{article}
\usepackage[ngerman]{babel}
\begin{document}
\showhyphens{Zusammenhang}
\showhyphens{anderswo}
\showhyphens{anderswoher}
\end{document}
This shows
[] \TU/lmr/m/n/10 Zu-sam-men-hang
[] \TU/lmr/m/n/10 an-ders-wo
[] \TU/lmr/m/n/10 an-ders-wo-her
The LaTeX hyphenation points agree with the German Duden dictionary.
As none of the words use more than 7-bit ASCII, I think newer pattern
changes are not related.
Curiously, the same effect already appears with MKII and MKIV from
TeXLive 2014, the oldest I had around.
I'm also surprised 'anders-wo-her' gets hyphenated but 'anderswo' is
not hyphenated at all.
I could not reproduce a difference with English words so far.
Any ideas? As far as I understand, MKIV/LMTX should use the
de-hyph-1996 patterns which LuaLaTeX uses these days too, via
hyph-utf8.
Thanks,
--
Leah Neukirchenhttps://leahneukirchen.org/
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] About macro numberstriped ()
Am 28.09.22 um 15:29 schrieb Hans Hagen via ntg-context: On 9/28/2022 3:11 PM, Fabrice Couvreur via ntg-context wrote: PS : What is the exact meaning of the word "blobs" because my English is average ? in order to get 'lines' you need to fill the two opposing corners with "blobs of ink" Otherwise, a BLOB is a “binary large object”, e.g. if you save image data to a database. Hraban ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] strange issue with hyphens
Dear list,
I’m experiencing a weird issue with hyphenation:
\setuphyphenation
[method=traditional]
\starttext
\hyphenatedword{a-legibility-c}
\sethyphenationfeatures
[strict]
\hyphenatedword{a-legibility-c}
\stoptext
I need the setup hyphenation commands to get underscore hyphenation.
But how can I make that strict hyphenation features behave as standard
hyphenation ones?
I mean, that the first hyphen doesn’t get doubled and that hyphenation
is also enabled after the first hyphen.
I don’t know whether the strict hyphenation features are misbehaving
here or I am missing something very basic here.
Many thanks for your help,
Pablo
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] TOC colors and in-page anchors
On 9/28/22 12:20, Sylvain Hubert via ntg-context wrote:
> Thanks for the pointers, but unfortunately I cannot reproduce the second
> fix with either the system pdf viewer or the browser one.
Hi Sylvain,
it seems that ConTeXt is basically ignoring "focus=standard" in lists.
Compare both links here:
\setupinteraction[state=start,
color=darkred,
contrastcolor=darkred,
focus=standard]
\starttext
\completecontent
\section[a]{b}
\about[a]
\stoptext
And this is a regression. I think it was introduced in latest from
2022.07.06 21:42, since latest from 2022.05.11 11:36 has no issue with this.
Hans, could you see what preventing this from working as expected?
Many thanks for your help,
Pablo
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] Missing letters and numbers in printout
On 9/28/2022 5:10 PM, Pablo Rodriguez via ntg-context wrote: Well, that is probably too much to say (I mean, that "--luatex" generates more accurate PDF documents). depends on how one defines accurate The main issue would be pretending to use with LuaTeX some features available only in LuaMetaTeX. plenty (also font features) not in luatex indeed I agree with Hans that LuaMetaTeX is here to stay. He may correct me, but as far as I understand it, LuaMetaTeX is LuaTeX-2.0. 2.10 Hans - 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Missing letters and numbers in printout
On 9/28/22 15:30, Angel M Alganza via ntg-context wrote: > On Tue, Sep 27, 2022 at 04:03:06PM +0200, Pablo Rodriguez via > ntg-context wrote: >> [...] >> I think that this PDF document will be fine with your printer. > > It was. I printed it this morning without any problem. Thank you! Glad to read it helped, Ángel. I had the suspicion, because font embedding seems to be changed in LMTX. There have been minor issues in the past with this (I cannot recall whether I experienced one or two myself). > If compiling with --luatex option seem to have more chances to produce a > complete product, shouldn't it be convenient for this option to be the > default? Well, that is probably too much to say (I mean, that "--luatex" generates more accurate PDF documents). What you are experiencing might be a pretty extreme case. And you are taking for granted that the PDF interpreter from your printer is 100% accurate (which might not be the case). The PDF specification deals with font embedding (to the best of my knowledge) at https://opensource.adobe.com/dc-acrobat-sdk-docs/standards/pdfstandards/pdf/PDF32000_2008.pdf#nameddest=G8.1695688. Unless the code to be fixed (or even adapted) can be detected and improved, there is nothing to do here. > I would expect 'context file.tex' to work "out of the box" and > produce a correct and complete PDF output. Would it be possible to have > that changed? Or is there maybe any other potentially undesirable side > effect? The main issue would be pretending to use with LuaTeX some features available only in LuaMetaTeX. > Also, I guess that can be configured somehow so, what would need to be > changed to have 'context file.txt' to compile using luatex instead of > LuaMetaTeX? I agree with Hans that LuaMetaTeX is here to stay. He may correct me, but as far as I understand it, LuaMetaTeX is LuaTeX-2.0. I hope it might help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Missing letters and numbers in printout
On 9/28/2022 3:30 PM, Angel M Alganza via ntg-context wrote: On Tue, Sep 27, 2022 at 04:03:06PM +0200, Pablo Rodriguez via ntg-context wrote: In that case, run "context --luatex --generate" first and then "context --luatex a6lua.tex". This would give you a pure LuaTeX-compiled PDF document. I think that this PDF document will be fine with your printer. It was. I printed it this morning without any problem. Thank you! If compiling with --luatex option seem to have more chances to produce a complete product, shouldn't it be convenient for this option to be the default? I would expect 'context file.tex' to work "out of the box" and produce a correct and complete PDF output. Would it be possible to have that changed? Or is there maybe any other potentially undesirable side effect? Also, I guess that can be configured somehow so, what would need to be changed to have 'context file.txt' to compile using luatex instead of LuaMetaTeX? top line: % engine=luatex but lmtx is and will stay as default (btw, you don't run the latest greatest) Hans - 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Missing letters and numbers in printout
On Tue, Sep 27, 2022 at 04:03:06PM +0200, Pablo Rodriguez via ntg-context wrote: In that case, run "context --luatex --generate" first and then "context --luatex a6lua.tex". This would give you a pure LuaTeX-compiled PDF document. I think that this PDF document will be fine with your printer. It was. I printed it this morning without any problem. Thank you! If compiling with --luatex option seem to have more chances to produce a complete product, shouldn't it be convenient for this option to be the default? I would expect 'context file.tex' to work "out of the box" and produce a correct and complete PDF output. Would it be possible to have that changed? Or is there maybe any other potentially undesirable side effect? Also, I guess that can be configured somehow so, what would need to be changed to have 'context file.txt' to compile using luatex instead of LuaMetaTeX? Thank you! Cheers, Ángel ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] About macro numberstriped ()
On 9/28/2022 3:11 PM, Fabrice Couvreur via ntg-context wrote: Hi Hans, Thank you for this solution which is an approach that I did not know. Fabrice PS : What is the exact meaning of the word "blobs" because my English is average ? in order to get 'lines' you need to fill the two opposing corners with "blobs of ink" Hans (who's dutch is better than his english) - 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 / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] About macro numberstriped ()
Hi Hans,
Thank you for this solution which is an approach that I did not know.
Fabrice
PS : What is the exact meaning of the word "blobs" because my English is
average ?
Le mar. 27 sept. 2022 à 22:04, Hans Hagen via ntg-context <
ntg-context@ntg.nl> a écrit :
> On 9/27/2022 7:49 PM, Fabrice Couvreur via ntg-context wrote:
> > Hello,
> > I notice a strange behavior of the macro numberstriped ( ).
> > Thanks.
> > Fabrice
> >
> > \starttext
> > \switchtobodyfont[9pt]
> > \startMPcode
> >
> >path p, q, r, b ;
> >p := unitsquare xyscaled (4cm,4cm) ;
> >z[0] = (2cm,0cm) ;
> >z[1] = (2cm,4cm) ;
> >z[2] = (0cm,2cm) ;
> >q := llcorner p--z[0]--z[1]--z[2]--cycle ;
> >r := unitsquare xyscaled (1cm,1cm) shifted(0,3cm) ;
> >b := unitsquare xyscaled (3cm,3cm) shifted(1cm,0) ;
> >draw p ;
> >draw r withcolor red;
> >draw r numberstriped (.25,20,5) withcolor magenta ;
> >draw b numberstriped (.25,20,5) withcolor magenta ;
> >label.llft("D", p) ;
> >label.lrt("C", p) ;
> >label.ulft("A", p) ;
> >label.urt("B", p) ;
> >label.urt("P", lrcorner r) ;
> >label.lft("Q", llcorner r) ;
> >label.top("M", urcorner r) ;
> >
> >\stopMPcode
> > \stoptext
> you need to find a volunteer to make the pattern have the two corner blobs
>
> \starttext
>
> \startMPcode
> path p, q, r, b ;
> path p ; p := unitsquare xyscaled (4cm,4cm) ;
> draw p ;
> draw p
> withpattern image (
> draw (llcorner unitsquare -- urcorner unitsquare) scaled 5mm ;
> % how to get the corner dots
> )
> withpatternscale 1/16
> withpen pencircle scaled 1mm
> ;
> \stopMPcode
>
> \stoptext
>
>
> -
>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 /
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
>
> ___
>
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] TOC colors and in-page anchors
Thanks for the pointers, but unfortunately I cannot reproduce the second
fix with either the system pdf viewer or the browser one.
\usemodule[ipsum]
\setupinteraction[state=start,focus=standard]
\starttext
\completecontent
\section{s1}\ipsum
\section{s2}\ipsum
\section{s3}\ipsum
\section{s4}\ipsum
\section{s5}\ipsum
\section{s6}\ipsum
\stoptext
context version: 2022.09.11 20:44
The viewer is on 'Continuous Scoll' mode both before and after the click,
but clicking s4 still jumps to the beginning of page 2.
On Wed, 28 Sept 2022 at 16:43, Bruce Horrocks wrote:
>
>
> > On 28 Sep 2022, at 09:18, Sylvain Hubert via ntg-context <
> ntg-context@ntg.nl> wrote:
> >
> > Dear list,
> >
> > \usemodule[ipsum]
> > \setupinteraction[state=start]
> >
> > \starttext
> > \completecontent
> > \section{s1}\ipsum
> > \section{s2}\ipsum
> > \section{s3}\ipsum
> > \section{s4}\ipsum
> > \section{s5}\ipsum
> > \section{s6}\ipsum
> > \stoptext
> >
> > In the table of contents, s1 and s2 (at page 1) are rendered in red,
> while others in green.
> >
> > Moreover, when I click s4, it jumps to page 2 without locating the
> section precisely within the page.
> > This is not the case when using the latex hyperref package.
> >
> > Does anyone know how to make the colors uniform and the links precise?
> >
> > Any help is appreciated.
>
> The colour change is because those links are on the same page that you are
> jumping to. When you have more text in your document they will be
> consistent. You can override the colors with
> \setupinteraction[state=start,color=black] for example if you wish.
>
> You need focus=standard to jump direct but only when the viewer is in
> scrolling mode. It's explained on the Wiki.
>
>
> —
> Bruce Horrocks
> Hampshire, UK
>
>
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] TOC colors and in-page anchors
> On 28 Sep 2022, at 09:18, Sylvain Hubert via ntg-context
> wrote:
>
> Dear list,
>
> \usemodule[ipsum]
> \setupinteraction[state=start]
>
> \starttext
> \completecontent
> \section{s1}\ipsum
> \section{s2}\ipsum
> \section{s3}\ipsum
> \section{s4}\ipsum
> \section{s5}\ipsum
> \section{s6}\ipsum
> \stoptext
>
> In the table of contents, s1 and s2 (at page 1) are rendered in red, while
> others in green.
>
> Moreover, when I click s4, it jumps to page 2 without locating the section
> precisely within the page.
> This is not the case when using the latex hyperref package.
>
> Does anyone know how to make the colors uniform and the links precise?
>
> Any help is appreciated.
The colour change is because those links are on the same page that you are
jumping to. When you have more text in your document they will be consistent.
You can override the colors with \setupinteraction[state=start,color=black] for
example if you wish.
You need focus=standard to jump direct but only when the viewer is in scrolling
mode. It's explained on the Wiki.
—
Bruce Horrocks
Hampshire, UK
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
[NTG-context] TOC colors and in-page anchors
Dear list,
\usemodule[ipsum]
\setupinteraction[state=start]
\starttext
\completecontent
\section{s1}\ipsum
\section{s2}\ipsum
\section{s3}\ipsum
\section{s4}\ipsum
\section{s5}\ipsum
\section{s6}\ipsum
\stoptext
In the table of contents, s1 and s2 (at page 1) are rendered in red, while
others in green.
Moreover, when I click s4, it jumps to page 2 without locating the section
precisely within the page.
This is not the case when using the latex hyperref package.
Does anyone know how to make the colors uniform and the links precise?
Any help is appreciated.
Sylvain
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
