[loc-en-dev] MessageFormat question

Yoshito Umaoka y.umaoka at gmail.com
Thu Aug 11 13:40:41 PDT 2011


I chatted with Naoto about OpenJDK activities.

We think we should probably close the Locale Enhancement Group and drive 
i18n related work through i18n group for Java 8 and beyond. I think such 
things should be included in the scope (and we have some people who know 
the old Taligent code and design).

I want to discuss about this in the teleconference next Monday.

-Yoshito

On 8/11/2011 2:50 AM, Masayoshi Okutsu wrote:
> BTW, as I asked at the last locale enhancements teleconference, are 
> there any volunteers who can work on fixing this kind of bugs (mainly 
> carried over from Taligent code)? It's very time consuming to read 
> source code, write small tests to confirm behavior, write/correct 
> spec, and get API doc change approval. We still have many...
>
> Thanks,
> Masayoshi
>
> On 8/10/2011 11:15 PM, Mark Davis ☕ wrote:
>> Could well be...
>>
>> Mark
>> /— Il meglio è l’inimico del bene —/
>>
>>
>> On Tue, Aug 9, 2011 at 23:44, Masayoshi Okutsu 
>> <masayoshi.okutsu at oracle.com <mailto:masayoshi.okutsu at oracle.com>> wrote:
>>
>>     I understand the intention. But looks like both spec and
>>     implementation are broken...
>>
>>     Masayoshi
>>
>>
>>     On 8/9/2011 11:00 PM, Mark Davis ☕ wrote:
>>>     I don't remember what the implementation ended up as, but we
>>>     carried the original intent over from the Taligent code, which
>>>     was to allow alignment to different fields as I described.
>>>
>>>     Mark
>>>     /— Il meglio è l’inimico del bene —/
>>>
>>>
>>>     On Mon, Aug 8, 2011 at 22:05, Masayoshi Okutsu
>>>     <masayoshi.okutsu at oracle.com
>>>     <mailto:masayoshi.okutsu at oracle.com>> wrote:
>>>
>>>         Thanks. But the implementation seems to be different. (I'm
>>>         talking about JDK, not ICU4J.) MessageFormat.format takes
>>>         only MessageFormat.Field.ARGUMENT. Specifying
>>>         NumberFormat.Field.DECIMAL_SEPARATOR has no effect.
>>>
>>>         FieldPosition had been added to JDK in 1.1 before
>>>         Format.Field support was added in 1.4 for Swing. I wondered
>>>         what the original intention of the spec was, especially with
>>>         a FieldPosition constructed with FieldPosition(int). The
>>>         other two constructors were added in 1.4.
>>>
>>>         Masayoshi
>>>
>>>
>>>         On 8/9/2011 9:50 AM, Mark Davis ☕ wrote:
>>>>         It is for lining up columns.
>>>>
>>>>         For example, suppose you have a column in a spreadsheet
>>>>         with formatted numbers. If you pass in
>>>>         http://download.oracle.com/javase/6/docs/api/java/text/NumberFormat.Field.html#DECIMAL_SEPARATOR
>>>>         you can find out the start/end position of the decimal
>>>>         separator, no matter what language the numbers are
>>>>         formatted in, and align them. In practice, that one field
>>>>         is probably the only really useful one.
>>>>
>>>>         Mark
>>>>         /— Il meglio è l’inimico del bene —/
>>>>
>>>>
>>>>         On Mon, Aug 8, 2011 at 01:40, Masayoshi Okutsu
>>>>         <masayoshi.okutsu at oracle.com
>>>>         <mailto:masayoshi.okutsu at oracle.com>> wrote:
>>>>
>>>>             I wonder if someone on this mailing list has some idea
>>>>             on my question below.
>>>>
>>>>             MessageFormat.format takes a FieldPosition defined as
>>>>             follows:
>>>>
>>>>             pos - On input: an alignment field, if desired. On
>>>>             output: the offsets of the alignment field.
>>>>
>>>>             What's the intention of this spec? What's the alignment
>>>>             field?
>>>>
>>>>             Thanks in advance,
>>>>             Masayoshi
>>>>
>>>>
>>>
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/locale-enhancement-dev/attachments/20110811/9faa9f44/attachment.html 


More information about the locale-enhancement-dev mailing list