Re: new feature proposal: filter maps

>  it's still not clear to me how such a text-conf approach could cope with
>  these booleans and conditional statements... take e.g.
>  trCompoundReference() function:
>
>      /*! used as the title of the HTML page of a class/struct/union */
>      virtual QCString trCompoundReference(const char *clName,
>                                      ClassDef::CompoundType compType,
>                                      bool isTemplate)
>      {
>        QCString result=(QCString)clName;
>        switch(compType)
>        {
>          case ClassDef::Class:      result+=" Class"; break;
>          case ClassDef::Struct:     result+=" Struct"; break;
>          case ClassDef::Union:      result+=" Union"; break;
>          case ClassDef::Interface:  result+=" Interface"; break;
>          case ClassDef::Protocol:   result+=" Protocol"; break;
>          case ClassDef::Category:   result+=" Category"; break;
>          case ClassDef::Exception:  result+=" Exception"; break;
>        }
>        if (isTemplate) result+=" Template";
>        result+=" Reference";
>        return result;
>      }
>
>  how could you write it in a text-conf file?
You leave all these conditionals there in the class, just add
tranlations for Class, Struct, Union, ... and Template.
Number of translate words does not have to be the same as number of tr
functions.

Oleg

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/