Add translations about phone-number-bundle HOT 3 CLOSED

After a quick bit of looking into this:

• The PhoneNumber constraint has a type property (designed for 'fax', 'mobile' etc) which is currently a placeholder. This won't work (I think) as it needs to be translated itself, so it looks like the message will have to be constructed here (with care taken to maintain BC). Suggested default support types are 'phone', 'mobile', 'fax' (note that these are just labelling rather than such granular validation).
• In #1 we added a friendly invalid message to the PhoneNumberType, but I'm wondering whether this should be removed and so the field uses the same message as other types (ie "This value is not valid") for values such as 'foo'.

Based on that, the only strings to translate look to be:

• This value is not a valid phone number.
• This value is not a valid mobile number.
• This value is not a valid fax number.

(Unless generic messages such as "Phone number" are dealt with for field labels etc. Does any public bundle do this kind of thing?)

from phone-number-bundle.

Thinking about this again, it's probably not a good idea to have a type property that doesn't actually do anything. Instead, using PhoneNumberUtil::getNumberType() should allow us to check what the number is (usually wanting to know mobile or fixed line).

This may prove difficult to translate.

from phone-number-bundle.

Fixed in #15

from phone-number-bundle.