Difference between revisions of "Express Entry:Global Best Practices"
Jump to navigation
Jump to search
m (Admin moved page Global Express Entry:Best Practices to Express Entry:Global Best Practices without leaving a redirect) |
|||
Line 1: | Line 1: | ||
[[ | [[Express Entry:Reference|← Express Entry Reference]] | ||
{{CustomTOC}} | {{CustomTOC}} | ||
==Encoding with Internet Explorer== | ==Encoding with Internet Explorer== | ||
Line 20: | Line 11: | ||
[[Category:Best Practices]] | [[Category:Best Practices]] | ||
[[Category: | [[Category:Express Entry]] |
Revision as of 01:10, 4 March 2015
Encoding with Internet Explorer
Internet Explorer does not UTF-8 encode characters with accents and other diacritics (such as à to %c3%a0) when sending them, so to query the service with Internet Explorer, one must manually enter their encodings.
Returning a Parsed Address
In Global Express Entry a parsed version, according to the standards of each country, of the input is returned when there is no reference data match. This may lead to some confusion as to whether the address is in the reference data. If your response address is the same as the input address, but in a different form, you may be getting a parsed version back, which means your address was not in the reference data.