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

TCL: Umlauts wrong or no character (Origin: bugzilla #662286) #4443

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2011-10-20 12:15:30 +0000, John Wayne wrote:

Created attachment 199516
Config and TCL-file

In many descriptions the umlauts aren't correct.
Only in file (brief and details) and namespace (details) the umlauts are ok.

On 2011-10-21 14:44:55 +0000, John Wayne wrote:

When I have more than one umlauts in the file Description, for every next umlauts disappears one of the last character at the end of the detail description.

On 2011-12-29 21:25:04 +0000, wrote:

Created attachment 204330
tcl scanner implementation

Good catch. After using QCString inside it should now work.
I also added parsing for some tcl commands (if,for,foreach,while)

The new scanner recognize only ## not followed by a third #
as starting point of doxygen comments (see bug # 662289)

On 2011-12-29 23:08:27 +0000, Dimitri van Heesch wrote:

Thanks, I'll include the patch in the next subversion update.

On 2012-01-02 22:36:13 +0000, wrote:

Created attachment 204475
tcl scanner implementation

Fixed wrong usage of procedures in global namespace.

On 2012-01-03 08:30:38 +0000, Dimitri van Heesch wrote:

Ok, I'll include it.

Note that you can also attach a patch (using svn diff file, or diff -u instead of the complete source file. A patch is more compact and makes it clearer what has changed.

On 2012-02-25 15:37:33 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.0. 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