Strange bug in interactive table of content...
A right parenthesis ')' shows up as black in the interactive table of contents (which otherwise displays as green). Here is a MWE: \setupcolors[state=start] \setupinteraction[state=start] \definecombinedlist[content][chapter] \setupcombinedlist[content][level=4, alternative=c] \setbreakpoints[compound] \starttext \completecontent \chapter{Noten bij de digitale (her)uitgave} \chapter{Noten bij de digitale (her)\-uitgave} \chapter{Tries: her)uit} \chapter{Tries: her)ui} \chapter{Tries: er)uit} \stoptext If I comment \setbreakpoint[compound] the bug does not show. It seems to matter what characters come before and after the right parenthesis for this bug to show up. To bypass the problem, one can use \- after the rparen, and then the bug does not show up, but I don't think anyone encountered this small and particular bug... Greetings, Rob Output in attachement.
On 01/30/2015 03:18 AM, Rob Heusdens wrote:
A right parenthesis ')' shows up as black in the interactive table of contents (which otherwise displays as green).
Here is a MWE:
\setupcolors[state=start] \setupinteraction[state=start] \definecombinedlist[content][chapter] \setupcombinedlist[content][level=4, alternative=c] \setbreakpoints[compound] \starttext \completecontent \chapter{Noten bij de digitale (her)uitgave} \chapter{Noten bij de digitale (her)\-uitgave} \chapter{Tries: her)uit} \chapter{Tries: her)ui} \chapter{Tries: er)uit} \stoptext [...] Output in attachement.
Hi Rob, using beta from 2015.01.26 11:39 displays all characters in green (tested in Fedora 20 with evince-3.10.3 and mupdf-1.6). If there was a bug, I guess it might have been fixed. I hope it helps, Pablo -- http://www.ousia.tk
On 01/30/2015 03:18 AM, Rob Heusdens wrote:
A right parenthesis ')' shows up as black in the interactive table of contents (which otherwise displays as green).
Here is a MWE:
\setupcolors[state=start] \setupinteraction[state=start] \definecombinedlist[content][chapter] \setupcombinedlist[content][level=4, alternative=c] \setbreakpoints[compound] \starttext \completecontent \chapter{Noten bij de digitale (her)uitgave} \chapter{Noten bij de digitale (her)\-uitgave} \chapter{Tries: her)uit} \chapter{Tries: her)ui} \chapter{Tries: er)uit} \stoptext [...] Output in attachement.
Hi Rob,
using beta from 2015.01.26 11:39 displays all characters in green (tested in Fedora 20 with evince-3.10.3 and mupdf-1.6).
If there was a bug, I guess it might have been fixed.
I hope it helps,
Pablo -- http://www.ousia.tk
I am using a recent version. mtx-context | ConTeXt Process Management 0.61 mtx-context | mtx-context | main context file: /home/ubuntu/context/tex/texmf-context/tex/context/base/context.mkiv mtx-context | current version: 2014.12.03 18:26 So, I should upgrade to the newest beta? greetings, Rob
On 01/30/2015 04:02 PM, Rob Heusdens wrote:
[...] I am using a recent version. [...] So, I should upgrade to the newest beta?
Using a beta from 2014.11.26 21:43 shows the bug you described. Upgrading to latest beta makes sense in this case. If you allow me an opinion, I try to keep ConTeXt updated (I have just updated it), so I can enjoy the latest features and report the possible issues I might face. Pablo -- http://www.ousia.tk
On 01/30/2015 04:02 PM, Rob Heusdens wrote:
[...] I am using a recent version. [...] So, I should upgrade to the newest beta?
Using a beta from 2014.11.26 21:43 shows the bug you described.
Upgrading to latest beta makes sense in this case.
If you allow me an opinion, I try to keep ConTeXt updated (I have just updated it), so I can enjoy the latest features and report the possible issues I might face.
Pablo -- http://www.ousia.tk
Hello Pablo, I can imagine people sticking to the latest stable release only instead of picking up the latest beta. I have a workaround, so it is not so important (and this kind of bug almost never shows up, I just accidently ran into it, and I was just amazed by the peculiarity of it). Just to be sure, how can I upgrade to latest beta? Greetings, Rob
On 01/30/2015 05:42 PM, Rob Heusdens wrote:
[...] Hello Pablo,
I can imagine people sticking to the latest stable release only instead of picking up the latest beta.
Hi Rob, don’t worry, with ConTeXt Standalone you can have them all ;-). Each ConTeXt Standalone installation is independent, so you can have the latest stable version and many beta releases. The only requirement is available storage. When I started using ConTeXt on a regular basis (I moved from a decade with LaTeX), I thought the stable release was the right thing to use. I had it from TeXLive. After a reply to a question in this mailing list, I thought it was sensible to install the latest beta version and keep it updated. In spite of the word, unstable versions are pretty stable. They are pretty bug free. As Hans says, don’t use it for critical work. But besides that, bugs are there to be reported ;-). You could always find a bug in an stable version. And (to the best of my knowledge) these bugs are only fixed in the next version: first in the unstable one.
I have a workaround, so it is not so important (and this kind of bug almost never shows up, I just accidently ran into it, and I was just amazed by the peculiarity of it).
If I were in your shoes, I would keep the unstable version updated. Again, with the latest unstable version you only have to deal with brand-new bugs (or at least with the active ones). If you allow me a personal opinion, ConTeXt is simply awesome. It helps a lot of us to create more–than–beautiful documents. Hans is the main hero behind it. I think a way to contribute back to ConTeXt is at least to report bugs. And to be able to report bugs, one should have the latest beta installed. [Just in case I haven’t expressed myself accurately, I’m not meaning you wasn’t doing the right thing. My personal opinion only tries to show the convenience of having (also) the latest beta installed.]
Just to be sure, how can I upgrade to latest beta?
Which OS do you use? As a general (OS-agnostic) advice, make a copy of the directory were you have ConTeXt Standalone installed. Rename it to "context-beta" (without the quotes) and update that ConTeXt version. If you are on Windows, I’m afraid I cannot help (I could guess how it could work, but I cannot check it). On Unix (Linux / MacOS X), you could use: cd /path/where/you/have/context-beta rsync -ptv rsync://contextgarden.net/minimals/setup/first-setup.sh . ./first-setup.sh --modules=all More info can be found at http://wiki.contextgarden.net/ConTeXt_Standalone. Just in case it helps (and don’t hesitate to ask, if it doesn’t), Pablo -- http://www.ousia.tk
participants (2)
-
Pablo Rodriguez -
Rob Heusdens