Broken Index Behavior?
I put ConTeXt on a new server. It works fine except that it is not aggregating index results. I have isolated it to a single line, but i do not understand why it breaks indexing. Feedback from anybody would be immensely helpful. I have already spent way too much time figuring this out. %Minimal example: % ConTeXt ver: 2017.05.15 21:48 MKII fmt: 2017.8.17 int: english/english \enableregime[utf] \starttext \index{Aardvark}Aardvark \index{Baboon}Baboon \index{Camel}Camel \pagebreak \index{Baboon}Baboon \placeindex[compress=yes] \stoptext Outputs Index like this: A Aardvark 1 B Baboon 1 C Camel 1 B Baboon 2 and issues warning when compiling: references : duplicate reference [][Index:b] on page 2 However, if i remove this line, it works fine: \enableregime[utf] I need that line to be able to handle diacritics in the text however. I cannot upgrade to mkIV yet as there is a complex toolchain involved. Running this example with the same installation files and same input returns different results when run on my local workstation versus this new machine i am working on. It also works fine on the live.contextgarden.net tool. Can anyone think of a reason why adding "\enableregime[utf]" would break the index aggregator? File permissions? Missing tool? Something wrong with fonts? Some other context-sensitive misconfiguration? Any help would be appreciated. Thanks a bunch.
On Fri, Mar 2, 2018 at 2:28 AM, Brian Wedde
I put ConTeXt on a new server. It works fine except that it is not aggregating index results. I have isolated it to a single line, but i do not understand why it breaks indexing. Feedback from anybody would be immensely helpful. I have already spent way too much time figuring this out.
%Minimal example: % ConTeXt ver: 2017.05.15 21:48 MKII fmt: 2017.8.17 int: english/english \enableregime[utf] \starttext \index{Aardvark}Aardvark \index{Baboon}Baboon \index{Camel}Camel \pagebreak \index{Baboon}Baboon \placeindex[compress=yes] \stoptext
Outputs Index like this:
A Aardvark 1
B Baboon 1
C Camel 1
B Baboon 2
and issues warning when compiling: references : duplicate reference [][Index:b] on page 2
However, if i remove this line, it works fine: \enableregime[utf]
I need that line to be able to handle diacritics in the text however. I cannot upgrade to mkIV yet as there is a complex toolchain involved.
Running this example with the same installation files and same input returns different results when run on my local workstation versus this new machine i am working on. It also works fine on the live.contextgarden.net tool.
Can anyone think of a reason why adding "\enableregime[utf]" would break the index aggregator? File permissions? Missing tool? Something wrong with fonts? Some other context-sensitive misconfiguration?
Any help would be appreciated. Thanks a bunch. Hm this is what I see
1 Aardvark Baboon Camel 2 Baboon a Aardvark 1 b Baboon 1–2 c Camel 1 I will send off-list my files -- luigi
Thanks Luigi. I am getting the "correct" results on my local workstation as well. However, when working on an installation on a Amazon Linux EC2 instance, the index refuses to aggregate the results. This even happens if i copy my entire ConTeXt directory to the Amazon Linux machine verbatim. I have also tried the latest ConText version and get the same weird results. I am convinced that this has something to with the environment and not the installation itself, but I don't know where to look anymore. I am out of ideas. I have: - Disabled SELinux - Copied files from known working installation - Installed latest versions - chmod everything 777 Any ideas on where to look would still be appreciated. Thanks - brian
On Mon, Mar 5, 2018 at 10:30 PM, Brian Wedde
Thanks Luigi. I am getting the "correct" results on my local workstation as well. However, when working on an installation on a Amazon Linux EC2 instance, the index refuses to aggregate the results. This even happens if i copy my entire ConTeXt directory to the Amazon Linux machine verbatim. I have also tried the latest ConText version and get the same weird results. I am convinced that this has something to with the environment and not the installation itself, but I don't know where to look anymore. I am out of ideas. I have:
- Disabled SELinux - Copied files from known working installation - Installed latest versions - chmod everything 777
Any ideas on where to look would still be appreciated. No idea ... you can send me your files off-list (as I have done). Btw, I have used the texlive 2017.
-- luigi
participants (2)
-
Brian Wedde
-
luigi scarso