The Unified Modeling Language (UML) is the most commonly used software description language. Today, textual notations for UML aim for a compact representation that is suitable for developers. Many textual notations exist but their applicability in engineering teams varies because a standardized textual notation is missing. Evaluating notations in order to find a suitable one is cumbersome and guidelines found in surveys do not report on applicability. This survey identifies textual notations for UML that can be used instead of or in combination with graphical notations, e.g. by collaborating teams or in different contexts. Additionally, it rates the notation's applicability with respect to UML coverage, user editing experience, and applicability focused on engineering teams. Our results facilitate the otherwise unclear selection of a notation tailored for specific scenarios and enables trade-off decisions. We identified and characterized 21 known notations and 12 notations that were not covered in previous surveys. We used 20 categories to characterize the notations. Our findings show that a single notation does not cover more than 3 UML diagram types (mean 2.6), supports all surveyed state of the art editing features (only one notation supports all), and fits into existing tool chains.