What considerations are there for encoding and character sets in address data?

What considerations are there for encoding and character sets in address data?

• A. Use ASCII only to ensure compatibility.
• B. Store data in ISO-8859-1 and ignore non-English characters.
• C. Use UTF-8, preserve diacritics where needed, handle normalization carefully, and ensure encoding safety in queries and displays.
• D. Convert all characters to lower-case and strip diacritics.

Answer: (C)

Handling encoding and character sets for address data requires supporting the full range of international characters while keeping data accurate across systems. Using UTF-8 provides broad Unicode coverage, so you can store names, street names, city names with diacritics, and scripts beyond Latin. Preserving diacritics where needed ensures correct representation and avoids misinterpretation. You also want to handle normalization: addresses can be stored in different canonical forms, so a consistent normalization approach makes comparisons and searches reliable. Encoding safety in queries and displays means consistently saving and retrieving data as UTF-8, and properly escaping or encoding when rendering to HTML or constructing queries to prevent corruption or security issues. The other approaches fall short because ASCII is too limited to represent many characters found in global addresses; ISO-8859-1 covers only Western European characters and would drop many diacritics and non-Latin characters; converting everything to lower-case and stripping diacritics loses important identity information and can alter the meaning of names.