> <\body> The mathematical symbols in all come with a certain number of properties which correspond to their intended meaning. For instance, is aware that > is an infix operator, whereas ! is rather a postfix, and , a separator. has special symbols =2.71828\>, =3.14159\> and > for important mathematical constants, which display differently from the mere characters , > and , and which can be entered using the shortcuts >, > and >. We recommend to systematically use these shortcuts. Inversely, semantically distinct symbols may display in a similar way. For instance, the comma separator, as in >, is different from the decimal comma, as in 14159\>. Notice that the two symbols admit different spacing rules. Semantically distinct symbols which are rendered by the same glyph are called . Notice that our semantics is purely syntactic: for instance, the infix is commonly used for addition, but sometimes also for the concatenation of strings. Nevertheless, these two uses do not differ from a syntactical point of view, since the symbol remains a binary infix with the same precedence with respect to other symbols. The most confusing homoglyphs are the various invisible symbols supported by : <\itemize> The multiplication, entered by . Example: . Function application, entered by . Example: . An invisible separator, entered by >. Example: the matrix j>|)>>. An invisible addition, entered by >. Example: >. An invisible symbol, entered by >. Example: the increment +1>. An invisible bracket (mainly for internal use). A matching pair of invisible brackets is entered using . Again it is recommended that authors carefully enter these various invisible symbols when appropriate. It is particularly important to distinguish between multiplication and function application, since there is no 100% safe automatic way to make this distinction (we already mentioned the formulas > and > before). supports two quite general schemes for entering homoglyphs. On the one hand, we often rely on the standard variant system. For instance, > and > are obtained using > and >. When applicable, we also support the following convention: first type the character with a similar semantics and then type the character which corresponds to the rendering. This convention was already used above for the invisible homoglyphs, and often allows for shorter shortcuts. In table we have given the complete list of homoglyphs supported by . |||>|>||>|>|>||>|>|>>||j>=ai>>>|>|>>||>>|>|>>||+1>>|>|>||\|\x,P|\>>>|>|>|>|=>>|>|>|>|\\|x\0|}>>>|>|>|>||aa|\>>>|>|>|>|1001>>|>|>||>>|>|>||456>>|>|>||>|>|>||x\x>>|>|>|>>|\\>>|>|>|>>|+1>>|>|>|>|E:P|}>>>|>|>>|>>|>>|>|>>|>>|11=11>>|>|>|>|>|>|>|>|>=\\>>|>|>|>>|2=2>>|>|>|>>|x\\y>>|>>>>|Homoglyphs supported by .>