Re: JDK-8042131: Proposal of Mapped-values formatter for non-IsoChronology

2018-06-15 Thread naoto . sato
It does seem to be a good change. I will take a look and sponsor it. Naoto On 6/15/18 7:38 AM, Roger Riggs wrote: Hi, A good suggestion to reconsider, I re-opened the issue. I have not looked closely to see if/where the spec needs to be changed. Thanks, Roger On 6/15/18 5:30 AM, Stephen

Re: JDK-8042131: Proposal of Mapped-values formatter for non-IsoChronology

2018-06-15 Thread Roger Riggs
Hi, A good suggestion to reconsider, I re-opened the issue. I have not looked closely to see if/where the spec needs to be changed. Thanks, Roger On 6/15/18 5:30 AM, Stephen Colebourne wrote: From the looks of it, this is a perfectly reasonable enhancement. Sadly I can't sponsor it as I'm

Re: JDK-8042131: Proposal of Mapped-values formatter for non-IsoChronology

2018-06-15 Thread Stephen Colebourne
>From the looks of it, this is a perfectly reasonable enhancement. Sadly I can't sponsor it as I'm not a committer. Stephen On 15 June 2018 at 10:10, Toshio 5 Nakamura wrote: > > Hello core-libs and i18n folks, > > We'd like to request to reconsider JDK-8042131, > "DateTimeFormatterBuilder

JDK-8042131: Proposal of Mapped-values formatter for non-IsoChronology

2018-06-15 Thread Toshio 5 Nakamura
Hello core-libs and i18n folks, We'd like to request to reconsider JDK-8042131, "DateTimeFormatterBuilder Mapped-values do not work for JapaneseDate". The report was posted by our team long time ago, and was closed as not an issue. At that time, the feature was for only IsoChronology. Now, I