New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Corrupt translations in doxygen_manual_1.8.1.1.pdf? (Origin: bugzilla #679533) #4785

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component documentation for ---
Reported in version 1.8.1.1 on platform Other
Assigned to: Dimitri van Heesch

On 2012-07-06 22:40:23 +0000, Craig wrote:

Code examples starting in section 3.1.1.1 appear to be corrupted.

Eg. instead of seeing:

Here is an example of the use of these comment blocks:

/*! A test class /
class Test
{
public:
/
* An enum type.
* The documentation block cannot be put after the enum!
*/
enum EnumType
{
int EVal1, /< enum value 1 */
int EVal2 /
< enum value 2 */
};
void member(); //!< a member function.

protected:
int value; /*!< an integer value */
};

I see something like this (spaces/line feeds didn't copy correctly):

Here is an example of the use of these comment blocks:

\textcolor{comment}{/*! A test class /}
\textcolor{keyword}{class }Test {
\textcolor{keyword}{public}:\textcolor{comment}{}
\textcolor{comment}{ \textcolor{comment}{ \textcolor{comment}{
/
* An enum type. } * The documentation */}
block cannot be put after the enum! }
\textcolor{comment}{/< enum value 1 */} \textcolor{comment}{/< enum value 2 /}
\textcolor{comment}{//!< a member function.}
\textcolor{comment}{/
!< an integer value */}
\textcolor{keyword}{enum} EnumType {
\textcolor{keywordtype}{int} EVal1,
\textcolor{keywordtype}{int} EVal2 };
\textcolor{keywordtype}{void} member(); \textcolor{comment}{}
\textcolor{keyword}{protected}: \textcolor{keywordtype}{int} value;
};

On 2012-07-08 18:42:16 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2012-07-12 15:41:59 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.1.2. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment