Re: [greenstone-users] undefined classification problem

From Galya
DateSun, 27 Aug 2006 19:27:53 -0500
Subject Re: [greenstone-users] undefined classification problem
In-Reply-To (20060822055208-GA19720-matai-cs-waikato-ac-nz)
Hello again!
I have a similar question about translation to Russian and Hebrew.
If I'm using this line
classify Hierarchy -metadata dls.Subject -sort dls.Title -buttonname Type
it defines a text on About page, and I get rid of "undefined classification". However, a button Type in the nav. bar isn't translated to Russian and Hebrew.
if I'm using this line
classify Hierarchy -metadata dls.Subject -sort dls.Title -buttonname Types
the navigation bar button is translated, but I'm getting the same "undefined classification" on About page.
Could you help to solve this problem?
Thank you,
I translated this missing macro _labelTypes_   in
----- Original Message -----
From: "John R. McPherson" <>
To: "Katherine Don" <>
Sent: Tuesday, August 22, 2006 12:52 AM
Subject: Re: [greenstone-users] undefined classification problem

> On Tue, Aug 22, 2006 at 05:17:48PM +1200, Katherine Don wrote:
>> Hi Galya
>> If you change the buttonname args to Type and Creator, then it should do
>> what you want.
>> Otherwise you need to define macros:
>> _textTypesshort_
>> _textTypeslong_
>> and same for Authors
>> and possibly in
>> _texttextTypes_ {_labelTypes_}
>> and then in
>> _labelTypes_
> Hi,
> the new macro stuff isn't particularly well documented, so to clarify:
> 1. The _label$FOO_ macros are used for the classifier names in the
> navigation bar.
> 2. If you don't use the netscape4 compatibility stuff (which relies on
>  _text$FOO_ macros), you only need _label$FOO_.
> 3. You only need to define _label$FOO_ if you want the text that appears
>  in the navigation bar to be different to the name of the metadata field
>  you used. (One reason for this is to provide translations of a
>  metadata field name).
> And as Kath said above, for the help text on classifiers you need to
> define _text$FOOshort_ and _text$FOOlong_, in a macro file in a
> section starting with "package help" (where $FOO is your metadata field
> name).
> John