On Wed, Jun 1, 2022, 19:53 Tom Honermann via SG16 <sg16@lists.isocpp.org> wrote:

The 2022 annual C++ Developer Survey just launched. I reached out to Herb to ask about submitting additional questions to be included in next year's survey. He let me know that suggestions can be submitted to him at any time. So, I'd like to solicit Unicode related questions that would help us get some data regarding what people are doing in the wild. What would you like to know?

Some sample questions are below, please reply with additional suggestions (or improvements to these).

  • What character encodings do you use for source files?
    ASCII, UTF-8, Windows 1252, EBCDIC, other.
  • Do you use characters not included in the C++ basic character set in identifiers in your source code?
  • What character encodings do you use for C++ character and string literals?
    Compiler default (Windows active code page (ACP)), ASCII, UTF-8, Windows 1252, EBCDIC, other.
  • What character encodings do you support for run-time environments?
    UTF-8, Windows ACP, EBCDIC, other.
  • Do you develop international applications that support multiple languages and locales? If so, what language support features do you use for translations?
    ICU, Windows resource DLLs, GNU gettext, other.
  • Which of the C++ character types do you use?
    char, wchar_t, char8_t, char16_t, char32_t.
  • What Unicode libraries do you use?
    ICU, BasisTech Rosette, Win32, iconv, other.

I think asking about std:: locale/ICU/iconv/Qt/system API as the localization framework is nice, as well as the question about whether their program is localized, but the other questions aren't super informative (because they corelate with which platform/toolchain/c++ version they use), and many people won't be able to answer them because not everyone is familiar with the domain. They are best answered through code search imo.

Even a simple question as "is your application localized" will correlate strongly with the kind of application people write.

But overall, a limited number of questions for the benefit of sg16 is a great idea.

This topic will be one of the agenda items for next week's telecon.


SG16 mailing list