Re: [Boost-users] Interest in a Unicode library for Boost?

Zach Laine via Boost-announce <[email protected]> Wed, 30 Oct 2019 10:48:51 -0500
Newsgroups gmane.comp.lib.boost.announce
Message-ID <CALOpkJAJwK7ez=EpPrqCq3_vXGXr2MLmi6=009u78zx9-Xc9oA__38938.3328890958$1572450581$gmane$org@mail.gmail.com>
--===============2375632991605377753==
Content-Type: multipart/alternative; boundary="00000000000009633d059622a415"

--00000000000009633d059622a415
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Oct 30, 2019 at 7:59 AM Klaim - Jo=C3=ABl Lamotte <[email protected]=
m>
wrote:

>
>
> On Sat, 26 Oct 2019 at 03:11, Zach Laine via Boost-users <
> [email protected]> wrote:
>
>> About 14 months ago I posted the same thing.  There was significant work
>> that needed to be done to Boost.Text (the proposed library), and I was a
>> bit burned out.
>>
>> Now I've managed to make the necessary changes, and I feel the library i=
s
>> ready for review, if there is interest.
>>
>> This library, in part, is something I want to standardize.
>>
>> [snip]
>>
>>
>>
> (as a power user)
> I would be interested to have such library in Boost and already had plan
> to try Boost.Text in my next C++ project with text.
>
> I am following the discussions happening in SG16 and understand that ther=
e
> are some differences with the parts that will be proposed for
> standardisation (as ThePHD explains in his talk).
> Though honestly both approaches seems to solve my problems so I'm open to
> trying both. If boost.text is stable today, I'm happy to use it (at least
> to replace ICU and have a proper unicode text type).
>

Yes, JeanHeyd and I started with very different approaches, but we're
converging somewhat.

Zach

--00000000000009633d059622a415
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Oct 30, 2019 at 7:59 AM Klaim - J=
o=C3=ABl Lamotte &lt;<a href=3D"mailto:[email protected]">[email protected]=
</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><br></div><br>=
<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, 26=
 Oct 2019 at 03:11, Zach Laine via Boost-users &lt;<a href=3D"mailto:boost-=
[email protected]" target=3D"_blank">[email protected]</a>&gt=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div di=
r=3D"ltr">About 14 months ago I posted the same thing.=C2=A0 There was sign=
ificant work that needed to be done to Boost.Text (the proposed library), a=
nd I was a bit burned out.<div><br></div><div>Now I&#39;ve managed to make =
the necessary changes, and I feel the library is ready for review, if there=
 is interest.</div><div><br></div><div>This library, in part, is something =
I want to standardize.</div><div><br></div><div>[snip]</div><div><br></div>=
</div><br></blockquote><div><br>(as a power user)</div><div>I would be inte=
rested to have such library in Boost and already had plan to try Boost.Text=
 in my next C++ project with text.</div><div><br></div><div>I am following =
the discussions happening in SG16 and understand that there are some differ=
ences with the parts that will be proposed for standardisation (as ThePHD e=
xplains in his talk).</div><div>Though honestly both approaches seems to so=
lve my problems so I&#39;m open to trying both. If boost.text is stable tod=
ay, I&#39;m happy to use it (at least to replace ICU and have a proper unic=
ode text type).</div></div></div></blockquote><div><br></div><div>Yes, Jean=
Heyd and I started with very different approaches, but we&#39;re converging=
 somewhat.</div><div><br></div><div>Zach</div></div></div>

--00000000000009633d059622a415--

--===============2375632991605377753==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline