<i18n dev> RFR: 8323699: MessageFormat.toPattern() generates non-equivalent MessageFormat pattern [v2]
Archie Cobbs
acobbs at openjdk.org
Thu Jan 18 23:37:24 UTC 2024
On Thu, 18 Jan 2024 23:02:57 GMT, Justin Lu <jlu at openjdk.org> wrote:
> Sorry if I'm going over stuff you already know...
No apology needed, this stuff is obscure detail madness!
> So with this change, although calling `toPattern()` on `new MessageFormat("{0,choice,0.0#foo {1} {2} {3} }")` would return the String `"{0,choice,0.0#foo '{'1'}' '{'2'}' '{'3'}' }"` which **I** would think, formats differently, **in reality**, they format equivalently, so I think it is okay. I brought it up not necessarily as an issue, but just something to make apparent. Although I suppose something like this is up for interpretation, so perhaps its only wrong to me.
OK gotcha. I totally agree that what you think it should do makes a lot more sense that what it actually does!
-------------
PR Comment: https://git.openjdk.org/jdk/pull/17416#issuecomment-1899385354
More information about the i18n-dev
mailing list