Subject: Troubles with make/install for localized info
From: Vadim V. Zhytnikov
Date: Thu, 15 Dec 2005 07:32:46 +0300
Robert Dodier writes:
>>Unfortunately similar approach doesn't work
>>for .info. The main trouble is that there
>>is no standard scheme for localized .info
>>documentation placement. Usually info keeps all
>>.info files in one directory. So if we'll try
>>install maxima info's as follows
>>
>>/usr/share/info/maxima.info
>>/usr/share/info/es/maxima.info
>>/usr/share/info/pt/maxima.info
>>
>>then documentation in /es and /pt will not
>>be visible to info command.
>
>
> I am inclined to not attempt to solve the problem of making
> the info viewer program know where to find the translations.
>
> (1) Maxima runs just fine, with all capabilities, without any info viewer.
>
> (2) We can easily tweak Maxima to find the translations
> for the purpose of the "describe" command.
> (Just need to twiddle CL-INFO::*INFO-PATHS* and
> CL-INFO::*DEFAULT-INFO-FILES* if I recall correctly.)
>
> (3) I do understand some people use the info viewer to
> read the documentation. However I estimate there are
> many more people (I'm guessing at least 10 to 1 and
> maybe 100 to 1) who read the HTML.
>
> (4) There is a very easy workaround for people who do
> use the info viewer, which is to put the -f option on the
> info viewer command line, yes?
>
Yes, I understand all above and agree - making info command
happy is not our primary concern.
The _real_ trouble is - I don't understand how to force
automake install Spanish translation into /es subdirectory.
It seems that there is no regular way to do so.
"all info in one directory" is hardwired in automake
internals.
PS: In fact the more I use automake the less I like it.
Service it delivers don't worth restrictions it imposes.
--
Vadim V. Zhytnikov