For those who work with trees on Ancestry.com, synchronized with Family Tree Maker 2012, there is a bug in FTM that splits the Place if it contains a forward slash ("/") as in this example, color-coded to highlight the split:
Ancestry.com place: Toronto (West/Ouest) (City/Cité) Ward/Quartier No 5, Toronto (west/ouest) (city/cité), Ontario, Canada
FTM2012 Residence description: Toronto (West/Ouest) (City/Cité) Ward/Quartier No 5, Toronto (west/ouest) (city
FTM2012 place: Cité), Ontario, Canada
The resulting Place is quite useless and not necessarily unique to, in the example cited, any one city. The GEDCOM directly from Ancestry maintains the place intact; it is only FTM2012 that breaks it.
On researching this issue, I have learned that the slash was used in FTM7-16 to delimit event description from event place in support of a mapping feature. But Ancestry.com databases can have places with slashes in which there is no intention to have them so parsed. Examples are Residence events generated from Canada Census databases for which there are English and French words used, e.g., east/est, west/ouest, City/cite.
I have reported this as a bug and would welcome any contrary or supporting opinions and advice on least effort workarounds to restore the places to their proper values.