Justin Deoliveira a écrit : > * InternationlizedString > > Can we kill this? I don't see the point of modeling i18n directly in the > api since every application does i18n differently. It would be one thing > if this was a subclass of String, but its not. I know it extends > CharSequence but still... I dont really see any other java api's that do > this.
My understanding of Andrea's comment is that InternationalString was used in places where it should not, e.g. for programmatic names or identifiers. InternationalString is not expected to be used everywhere; only for strings targeted to user interfaces with no programmatic impact (e.g. often okay for HashMap values but not keys, etc.). InternationalString is a very simplified version of JSR 92: Localizable Text (http://www.jcp.org/en/jsr/detail?id=92), which is now withdrawn. So while there is few API dealing with this issue today, at least they were attempts from IBM. If a user needs to treat an InternationalString as a String, he can just invoke toString(), which is defined in the javadoc. But I don't expect this need to arise if InternationalString is not used as a programmatic name. I expect it to be used in context like string concatenation (e.g. "Search result for " + title) where String or InternationalString make no difference for the developper. Martin ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
