Date: Thu, 2 Jun 2022 12:02:29 -0400
On 6/1/22 5:25 PM, Corentin Jabot wrote:
>
>
> On Wed, Jun 1, 2022, 19:53 Tom Honermann via SG16
> <sg16_at_[hidden]> wrote:
>
> The 2022 annual C++ Developer Survey
> <https://isocpp.org/blog/2022/05/2022-annual-cpp-developer-survey-lite>
> 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.
Perhaps an "I don't know what this means" response option would be
informative for some of the cases.
> They are best answered through code search imo.
One of the benefits of this survey is that it gives us some insight into
what is done with closed source projects.
Perhaps another useful question would be:
* Are the projects that you work on open source, closed source, or a
mix of both?
Open source only, closed source only, mixed.
>
> Even a simple question as "is your application localized" will
> correlate strongly with the kind of application people write.
Maybe, but it would be good to have data about that. Localization may be
performed client or server side.
Tom.
>
> 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.
>
> Tom.
>
> --
> SG16 mailing list
> SG16_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>
>
>
> On Wed, Jun 1, 2022, 19:53 Tom Honermann via SG16
> <sg16_at_[hidden]> wrote:
>
> The 2022 annual C++ Developer Survey
> <https://isocpp.org/blog/2022/05/2022-annual-cpp-developer-survey-lite>
> 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.
Perhaps an "I don't know what this means" response option would be
informative for some of the cases.
> They are best answered through code search imo.
One of the benefits of this survey is that it gives us some insight into
what is done with closed source projects.
Perhaps another useful question would be:
* Are the projects that you work on open source, closed source, or a
mix of both?
Open source only, closed source only, mixed.
>
> Even a simple question as "is your application localized" will
> correlate strongly with the kind of application people write.
Maybe, but it would be good to have data about that. Localization may be
performed client or server side.
Tom.
>
> 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.
>
> Tom.
>
> --
> SG16 mailing list
> SG16_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>
Received on 2022-06-02 16:02:34