Activity for Juergen Spitzmueller
-
Juergen Spitzmueller modified a comment on ticket #5
I think what needs to be done is to add a module no-page-ranges.xdy which holds (define-location-class "arabic-page-numbers" ("arabic-numbers") :min-range-length 100000) (define-location-class "roman-page-numbers" ("roman-numbers-lowercase") :min-range-length 100000) (define-location-class "Roman-page-numbers" ("roman-numbers-uppercase") :min-range-length 100000) (define-location-class "alpha-page-numbers" ("alpha") :min-range-length 100000) (define-location-class "Alpha-page-numbers" ("ALPHA") :min-range-length...
-
I think what needs to be done is to add a module no-page-ranges.xdy which holds (define-location-class "arabic-page-numbers" ("arabic-numbers") :min-range-length 100000) and then in texindy: - unshift (@modules, 'page-ranges') unless $no_ranges; + unshift (@modules, ($no_ranges ? 'no-page-ranges' : 'page-ranges')); This module would probably also help to solve https://github.com/jschrod/xindy.ctan/issues/3
-
I'd say "Symbols" is the most common header used for this (see also TLC2)
-
Is this related to https://github.com/jschrod/xindy.ctan/issues/4?
-
The only minor nuisance is that the markup is doubled, i.e. \EmpIn{\EmpIn{1}--\EmpIn{3}}, A way around this is (markup-range :sep "\EmpIn{--}" :attr "EmpIn") which yields \EmpIn{1}\EmpIn{--}\EmpIn{3}. I've pondered about removing the inner markup when there is a range, but this requires markup-range of the given attr to be defined, which might break old definitions.
-
This can be closed. LyX sets up everything automatically.
-
This can be closed. Texindy works out of the box with LyX.
-
Joachim, after another 9 years (and more than 15 years after I filed this report!) I finally sat down and got my own hands dirty. The attached patch implements the :attr option to markup-range and thus fixes the problem reported here via (markup-range :open "\EmpIn{" :close "}" :sep "--" :attr "EmpIn") The only minor nuisance is that the markup is doubled, i.e. \EmpIn{\EmpIn{1}--\EmpIn{3}}, but apart from being slightly ugly, this is only a problem for toggling macros such as \emph. I'd be very happy...
-
I am withdrawing this. Proper language -> xindy mapping will be implemented in LyX itself instead.
-
PR at https://github.com/jschrod/xindy.ctan/pull/6
-
Note that \see[also] entries are not linked either with their target with makeindex/hyperref, so this patch gets both on par.
-
xindy dataloss with hyperref (\hyperindexformat)
-
Text analysis is a nice feature, but texstudio's word count feature in the pdf viewer is orthogonal, since it counts the real words in the output (including bibtex generated bibliography, expanded macros, etc.). So I agree with the OP that a word count feature similar to texstudio's would be very useful.
1