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)

When storing address data, you need an encoding that can represent all the characters people might use, across languages and scripts. The best approach is to use UTF-8, which covers the entire Unicode set, so names and places with diacritics or non-Latin characters can be stored accurately. Preserving diacritics where needed is important for correctness and official records; stripping them or altering case can change meaning or cause lookup and matching problems.

Normalization matters because the same letter can appear in different forms (precomposed versus composed with combining marks). Using a consistent normalization form, such as NFC, helps ensure that lookups, comparisons, and displays behave predictably across systems.

Encoding safety in queries and displays means the data and the way you interact with it (input, storage, and rendering) must all agree on UTF-8. Use parameterized queries and proper escaping, and ensure every layer of the stack—frontend, backend, and database—handles UTF-8 consistently. This prevents corruption, mojibake, or misinterpretation of characters when users search or view addresses.

Choosing ASCII-only or ISO-8859-1 limits can exclude valid characters found in many addresses, leading to data loss or inaccurate records. Also, converting everything to lower-case and stripping diacritics loses meaningful information and can break sorting, matching, and official documentation.