Re: [Doxygen-develop] new feature proposal: filter maps

[Francesco M. <f18...@ya...>]

Hi,

Oleg Batrashev ha scritto:
>>  do I miss something?
> I think yes, you do ;) I still push my solution which is close to XML one.
> 
> In translation file you could have one default section and specialized
> sections fot C, Fortran, etc which override default section strings
> (or use XML analogue)
> ------
>...
> ------
> 
> You will still have one Translator class but there are 2 possibilities
> 1) You create array of strings for every section. You leave booleans,
> string arguments and conditional statements as they are
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?

Francesco