|
From: Peter E. <pe...@ap...> - 2018-02-08 23:12:34
|
Internal would probably be fine. The request for a way to get this info is from Mozilla. - Peter E > On Feb 8, 2018, at 11:15 AM, Mark Davis ☕️ <ma...@ma...> wrote: > > The proposal looks fine to me. We could make it @internal initially, given that it is so close to the release, then refine (if necessary). > > Mark > > On Thu, Feb 8, 2018 at 8:06 PM, Markus Scherer <mar...@gm... <mailto:mar...@gm...>> wrote: > On Thu, Feb 8, 2018 at 10:26 AM, Peter Edberg <pe...@ap... <mailto:pe...@ap...>> wrote: > Dear ICU team & users, > > I would like to discuss the following API issues for ICU 61, and possibly agree on an API to solve them. > Please provide feedback by: next Wednesday, 2018-02-14 > > Next Wednesday is the ICU 61 feature freeze date. I think it's too late for an API proposal that takes some thought and discussion. > > New functions that take type+width make sense to me. > > A new enum, when we have several "width" enums across formatting classes already, may not be the right choice. > > markus > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot <http://sdm.link/slashdot> > _______________________________________________ > icu-design mailing list > icu...@li... <mailto:icu...@li...> > To Un/Subscribe: https://lists.sourceforge.net/lists/listinfo/icu-design <https://lists.sourceforge.net/lists/listinfo/icu-design> > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > icu-design mailing list > icu...@li... > To Un/Subscribe: https://lists.sourceforge.net/lists/listinfo/icu-design |