[tex-live] [xindy] Path screwed up after update

[Zdenek Wagner]

2009/3/26 Joachim Schrod <jschrod at acm.org>:
> Simon Spiegel writes:
>>
>> On 26.03.2009, at 10:46, Simon Spiegel wrote:
>>
>> > Hi,
>> >
>> > I just updated the new version of xindy via tlmgr, and now something
>> > seems to be screwed up with the paths. When running a xindy command
>> > I've used now for several years I get "Cannot locate xindy module for
>> > language german". This is on OSX with MacTeX/TeXLive and the newest
>> > update to xindy.
>>
>> Sorry, I already seem to have solved it. Do I see this correctly, that
>> the names of some language modules have changed? So far, I've used "-L
>> german-din", which doesn't exist aynmore, "-L german-din5007" does
>> though.
>
> No, that's an error then. The update should have allowed to specify
> both variants, din and din5007; and din is the documented and prefered
> name for that variant. I'll look into it.
>
The bug was introduced by me, I forgot the contents of the $variant
variable is terminated by a hyphen. This is a patch:

--- xindy.pl    2009-03-22 14:57:39.000000000 +0100
+++ /usr/local/texlive/2008/texmf/scripts/xindy/xindy.pl
2009-03-26 12:06:26.000000000 +0100
@@ -656,7 +656,7 @@
            if ( $2 && -d "$ld/$1" ) { # $2 is not set if the regex didn't match
                $language = $1;
                $variant = "$2-"  unless ( $2 eq 'iso' );
-               $variant eq 'din'  and  $variant = 'din5007';
+               $variant eq 'din-'  and  $variant = 'din5007-';
            }
        }
        # Let's guess the codepage. We take any that starts with


>> A question which is probably more LaTeX-related, but still: Is it
>> possible to have a pure Unicode/UTF8 workflow with LaTeX and xindy? I
>> currently use pdfLaTeX with \usepackage[utf8]{inputenc}. So I can
>> write stuff like umlauts directly into the LaTeX source. I notice
>> though, that the .idx file isn't unicode anymore, "Noël" becomes
>> "No{\"e}l" etc.
>
> pdfLaTeX uses the LaTeX Internal Character Representation (LICR) that
> is also output to the raw index file. That's the way it is implemented
> to get independence of any input encoding.
>
>> While this isn't really a problem, would it be possible to have UTF8
>> all the way?
>
> Without XeTeX, it is impossible. I have not used XeTeX with LaTeX up
> to now, so I don't know if they change LaTeX's internal encoding. If
> yes, the raw index files will have UTF8 characters.
>
> Best,
>        Joachim
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Joachim Schrod                  Email: jschrod at acm.org
> xindy maintainer                http://www.xindy.org/
> Roedermark, Germany
>
> ------------------------------------------------------------------------------
> ________________________________________________________________________
> xindy-discuss mailing list -- general xindy announcements and discussions
> Unsubscribe via https://lists.sourceforge.net/lists/listinfo/xindy-discuss
>



-- 
Zdeněk Wagner
http://hroch486.icpf.cas.cz/wagner/
http://icebearsoft.euweb.cz