the \~langId switches do not work as expected (Origin: bugzilla #120367)

[doxygen]

status RESOLVED severity normal in component general for ---
Reported in version 1.5.3-SVN on platform Other
Assigned to: Dimitri van Heesch

On 2003-08-21 06:10:13 +0000, prikryl@skil.cz wrote:

Hi Dimitri,

Here is the example of the ~english and ~czech documented source for
which Doxygen does not produce expected results. The first function
comment was created by Miroslav Sommer, the second comment was created by
myself. The Doxyfile.cz (# Doxyfile 1.3.3-20030808) and Doxyfile.en
differs only in the language (English/Czech). Notice that the brief
comment for the first function contains both English and Czech texts. The
second problem can be observed for the exception part of the second
function. The English version still contains "~english". The Czech
version says the same as English plus the Czech string.

/*! \file test.h */

/**

• ~english
• \brief EN String representation of object at index \a index
• \param EN a index of object
• \exception EN Invalid index, must be greather than 0
• \return EN string
• ~czech
• \brief CZ Textovy popis objektu na indexu \a index
• \param a CZ index objektu
• \exception CZ Chybny index, musi byt vetsi nez 0
• \return CZ retezec
• ~
• \version 1.0
  */
  string toString(const int index);

/**

• \brief ~english EN String representation of object at index \a index

•    \~czech CZ Textovy popis objektu na indexu \a index
  

•    \~
  

• \param a ~english EN index of object ~czech index objektu ~
• \exception ~english EN Invalid index, must be greather than 0

•        \~czech CZ Chybny index, musi byt vetsi nez 0
  

•        \~
  

• \return ~english EN string ~czech CZ retezec ~
• \version 1.0
  */
  string toString2(const int index);

By the way, is it possible to attach zip with the example to the bug
report?

Regards,
Petr

On 2004-12-26 20:45:44 +0000, Dimitri van Heesch wrote:

This should work in the next release (sorry it took so long).

On 2005-01-01 11:56:06 +0000, Dimitri van Heesch wrote:

Please verify that this is fixed in release 1.4.0 and if so please close this bug.