{'fraction_non_alphanumeric': 0.02037351443123939, 'fraction_numerical': 0.0, 'mean_word_length': 5.513812154696133, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
National language architecture

A fundamental concern for customers of software products worldwide is the lack of consistent, comprehensive national language support (NLS)' across operating system platforms and across high-level computer languages. This concern has been expressed both by application users who (rightly) feel inadequately supported by the product software and by developers who are frustrated at not being able to respond to customer requirements. The user wants to be able to interact with a product that works according to his language, culture and conventions. The software developer currently does not have the means or flexibility of providing this support cost-effectively; each application must provide its own resources and be reinvented for each target culture.This paper proposes a solution to this problem -- an architected set of interfaces and resources that will provide consistent, comprehensive, cost-effective support for national language. This solution will provide for migration from, and coexistence with, the current development environment. The architecture will also be extensible to permit user customization of preferences at run time.