{'fraction_non_alphanumeric': 0.015602836879432624, 'fraction_numerical': 0.0, 'mean_word_length': 6.06, '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}}
Controlled Language Support for Perkins Approved Clear English ( PACE )

We present an account of our approach to developing Controlled Language specifications and Controlled Language checking software for customized applications. A structured approach combines document flow analysis, corpus analysis, and negotiation with relevant stakeholders. Modular reuse of previous Controlled Language specifications is a key ingredient, allowing relatively simple tailoring of specifications for different functional text types at a level beyond that of terminology. The approach is illustrated using our experiences applying it to Perkins Approved Clear English (PACE) to produce a computational checking system.