Bug 175859 [DataBinding] Use MessageFormat for validation hints
The default hints produced by String2IntegerPrimitiveValidator and its peers are not very pleasant. They print extremely long numbers, are missing spaces, etc. For I18n, these hints should be produced via MessageFormat patterns, rather than with a hard-coded structure. This would also allow clients to override the messages by providing replacement patterns in a fragment. Boris, are there any issues with using java.text.MessageFormat under Foundation profiles? Should an ICU equivalent be used instead?
bundles/org.eclipse.core.databinding/src/org/eclipse/core/databinding/conversion/StringToNumberConverter.java
private Class toType;
	/**
	 * NumberFormat instance to use for conversion. Access must be synchronized.
	 */
	private NumberFormat numberFormat;
	/**
	 * @param toType
	 */
	private StringToNumberConverter(NumberFormat numberFormat, Class toType) {
		super(String.class, toType);
		
		this.toType = toType;
		this.numberFormat = numberFormat;
	}
	/**
	 * 
	 * 
	 * @see org.eclipse.core.databinding.conversion.IConverter#convert(java.lang.Object)
	 */
	public Object convert(Object fromObject) {
		if (!(fromObject instanceof String)) {
			throw new IllegalArgumentException(
					"'fromObject' not instanceof String"); 
		}
		String source = (String) fromObject;
		if (!toType.isPrimitive() && source.trim().length() == 0) {