SG16 discussed the text related aspects of P0267R9 at our
teleconference held June26th, 2019. Meeting notes are available
We did not conduct any polls during the teleconference, but will
do so when we discuss this paper in SG16 at Cologne.
The relevant portions of the meeting notes are copied below for
- P0267R9 - A
Proposal to Add 2D Graphics Rendering and Display to C++:
- Tom, unsurprisingly, stated that the interface should use
std:u8string since it requires UTF-8 encoded
- Michael agreed and expressed dislike for the asumption of
UTF-8 in a
- Zach stated that the interfaces should be
and execution encoding.
- Steve pondered whether all current graphical display
systems are Unicode.
- Tom stated that the X window system is locale based.
- Zach suggested it would be least surprising to programmers
to use execution encoding. That way they can just
pass regular strings.
- Peter stated that, On UNIX systems, UTF-8 tends to be the
default, so things will work as is, but Windows
would be problematic.
- Zach observed that, without standard library support,
converting text from execution encoding to UTF-8 is hard.
- Peter suggested leaving it to the UI libraries to figure
- Zach responded that this is a UI library, so we need to
figure it out.
- Michael pondered whether we should add overloads for
- Zach suggested that we only need
- Hubert observed that the standard library is designed
- Tom asked Hubert to clarify, are you thinking these
interfaces should take a locale object?
- Hubert responded that, if you have strings that you don't
know the encoding for, then yes.
- JeanHeyd expressed a preference for just using
to avoid locale dependencies.
- Mark agreed that, perhaps, just
- Tom stated that, by the time 2D graphics is standardized,
we should be able to get good conversion routines in
the standard library or we will have failed miserably!
- Hubert observed that the paper is missing bidirectional
- Tom noticed that the paper doesn't say what happens with
ill-formed encoded input.
- Mark suggested discussing font names; these should
probably be bag-of-byte names. The paper defers to the HTML
- Zach noticed that the paper doesn't discuss normalization.
It would be nice if it called it out specifically.
- Tom asked if normalization matters.
- Zach responded that it does in some cases.
- JF suggested that we should make it possible to defer to
the CSS specification if we can't right now. We don't
want to do what we previously did in forking the Unicode
identifier specification from
- Mark noticed that some of the interfaces pass and return
by value where they probably shouldn't.
- JF pondered about overlap with SG13 and avoiding conflicts
in scheduling when meeting in Cologne.
- [Editor's note: SG13 and SG16 are meeting on separate