Skip to content
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

Add support for multi-byte characters in Doxygen comments #11910

Open
browntarik opened this issue Jan 31, 2024 · 1 comment
Open

Add support for multi-byte characters in Doxygen comments #11910

browntarik opened this issue Jan 31, 2024 · 1 comment
Labels
bug Language Service Visual Studio Inherited from Visual Studio world ready An issue relating string character encodings, localization translations, etc.
Projects
Milestone

Comments

@browntarik
Copy link
Contributor

browntarik commented Jan 31, 2024

Doxygen comments should render the below input:

/// @param P\uAB701, P\uAB992 D\uAB9D3\uAB7D00

@browntarik browntarik created this issue from a note in 1.20 (Triage) Jan 31, 2024
@browntarik browntarik added Language Service Visual Studio Inherited from Visual Studio bug labels Jan 31, 2024
@sean-mcmanus sean-mcmanus added the world ready An issue relating string character encodings, localization translations, etc. label Feb 1, 2024
@browntarik browntarik moved this from Triage to In progress in 1.20 Mar 6, 2024
@browntarik browntarik moved this from In progress to To do in 1.20 Mar 16, 2024
@browntarik browntarik moved this from To do to Triage in 1.20 Mar 19, 2024
@browntarik browntarik removed this from Triage in 1.20 Apr 29, 2024
@browntarik browntarik added this to Triage in 1.21 via automation Apr 29, 2024
@bobbrow bobbrow added this to the On Deck milestone Jun 17, 2024
@Colengms
Copy link
Collaborator

Colengms commented Jul 10, 2024

Is there documentation to back this up? I'm not able to find anything in Doxygen specs that suggests these should be interpreted in any way other than exactly as they are. The \u syntax is specific to C++ string literals, not comments. Instead of encoding multi-byte the characters this way, I don't believe there is any reason they can't be specified directly, provided the source file's encoding (i.e. UTF-8) supports encoding them.

Maybe someone is asking that we interpret this text the same way some other particular documentation generator does, unrelated to the spec? If so, this would seem to be a feature request / enhancement, and not a bug. If there is more to the story, it'd be good to include that in the issue. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Language Service Visual Studio Inherited from Visual Studio world ready An issue relating string character encodings, localization translations, etc.
Projects
Status: Triage
1.21
Triage
Development

No branches or pull requests

4 participants