Alan - can you confirm that you are referring to the family of party:getxxxxxAddress() functions.

I can see two ways to achieve what you want:

1) [as you suggest] providing functions that get the parts of the address; and
2) provide an address formatting facility

I suspect that the second is the better approach because it gets past the problem of providing address component functions for each of the address types (ie correspondence, billing, reminder, practice, etc). It would also 'fix' the display on the Customers|Information screen which displays the description - which is derived from the expression "concat(party:getBillingAddress(.),' - ',party:getHomeTelephone(.))"

There is already support in messages.properties for different decimal, time, date etc formats.  It would be logical to add an address format facility that would achieve what you want.

Something along the lines of

address.format   address city state code

or in your case:
address.format   address city, state code

Note that https://www.informatica.com/au/products/data-quality/data-as-a-service/a... suggests that the proper US format is to omit the comma.

Commas aside, the above website makes it clear that there are also international variations on the ordering of the address components - for example Germany uses
address code city  (with no state).

Tim A - I suspect that we need to add this to the list of internationalisation support improvements.

Regards, Tim G