<P> The characters for which this applies are: Ĉĉ, Ĝĝ, Ĥĥ, Ĵĵ, Ŝŝ, Ŭŭ . You may enter these directly in the edit box if you have the facilities to do so . However when you edit the page again you will see them encoded as Sx . This form is referred to as "x-sistemo" or "x-kodo". In order to preserve round - trip capability when one or more xs follow these characters or their non-accented forms (Cc, Gg, Hh, Jj, Ss, Uu), the number of xs in the edit box is double the number in the actual stored article text . </P> <P> For example, the interlanguage link ((en: Luxury car)) to en: Luxury car has to be entered in the edit box as ((en: Luxxury car)) on eo: . This has caused problems with interwiki update bots in the past . </P> <P> Some browsers are known to do nasty things to text in the edit box . Most commonly they convert it to an encoding native to the platform (whilst the NT line of Windows is internally UCS - 2LE--2 Byte subset of UTF - 16--it has a complete duplicate set of APIs in the Windows ANSI code page and many older apps tend to use these, especially for things like edit boxes). Then they let the user edit it using a standard edit control and convert it back . The result is that any characters that do not exist in the encoding used for editing get replaced with something that does (often a question mark though at least one browser has been reported to actually transliterate text!). </P> <P> Google Chrome and Chromium both have a cross-platform bug that prevents the use of font substitution . This means that even if the user has the correct typeface for a given script installed, it may not display correctly or at all . </P>

How do i key in a non ascii character