cx gx hx jx sx ux now work!
The X-System now works! :D It doesn't convert on the fly, but it does accept cx, gx, hx, jx, sx, ux instead of ĉ, ĝ, ĥ, ĵ, ŝ, ŭ as alternative spellings. Thanks a_david!
La X-sistemo nun funkcias! :D Ĝi ne konvertas literojn dum vi tajpas, sed ĝi ja akceptas cx, gx, hx, jx, sx, ux anstataŭ ĉ, ĝ, ĥ, ĵ, ŝ, ŭ kiel alternativaj literumoj. Dankon al a_david!
Yeah, I'm so happy to see the x system in place! I've been using it for years because most computers don't have an easy why to type Esperanto letters readily installed. Over the last week, I've been writing the characters without the special hats on the letters and would always get the "spelling error notice" which is annoying when you know how to spell it, you just can't be bothered to click the right letter (very time consuming!) or your keyboard isn't set up properly.
The x system is a good way for me to take notice that a special letter is used in a place and is a way for me to let the Duolingo program know that I know and am not just making a bunch of errors because I don't know the difference between the sounds and letters.
A lot of people say that the x system is ugly, I would agree but after a while I got used to it. For me it makes Esperanto look more exotic and there's nothing wrong with that in my opinion.
I made a Firefox extension that allows the X-system for Duolingo answers, but converts on-the-fly as you type, which means the text you write is both easy to type and standard to read.
If you would like that feature, you can install the extension from here: https://people.mozilla.org/~sstangl/esperanto-x-system-enabler.xpi
Source code to the extension is available by renaming the file from .xpi to .zip.
This is great. For those of us who can't install an Esperanto-only keyboard, or who are stuck using International keyboards that require complex key sequences to produce diacritics, the x-method is the way to go.
Regarding the debate surrounding the x- and h-methods, I find that I prefer the x-method. Because the letter "x" doesn't exist in Esperanto, this makes it really fast and easy to identify letters that ought to have diacritics. When I read Esperanto written with the h-method, I find that it slows my reading and confuses my comprehension of the message because I second guess if that added "h" is a letter or a diacritic.
Would be possible to have š and č being recognized as ĉ and ŝ, respectively? I find it funny that I have on my keyboard two letters in the Czech alphabet (and all the alphabet derived from it, afaik) that sound exactly as the two sounds Zamenhof decided to use, look nearly the same, yet they are not recognized by duolingo.
@Junesun, @amuzulo kaj aliaj instigantoj de tiu ĉi esperanto-rubriko en duolingvo: ĉu eblas atentigi la responsulojn de la retejo uzi alian tiparon kiu entenus la ĉapelajn simbolojn elskatole?
Mi vidas ke ili aspektas malbele sine de la ceteraj literoj. Tio ŝuldiĝas al la fakto ke la tiparo uzata de la retejo ne entenas ilin, do la retumilo anstataŭas ilin ĉerpante ilin el defaŭlta sistema tiparo. Tial la aspekto inter la ĉapelitaj literoj kaj la ceteraj literoj ne kongruas.
On my end, input using the X-system works both in a web browser and on a web connected Apple device, but the X-system doesn't seem to be recognized by an offline Apple device.
See https://c2.staticflickr.com/6/5717/22145358585_282c620b31_b.jpg for a (cruddy but hopefully legible) screenshot. It shows that "Li aux sxi laboras" is not recognized as a valid translation of "He or she works.", even though the inputted text is the X-system text that directly corresponds to the provided canonical translation. Again, this doesn't happen if there is web connectivity; this only happens when the Apple device is offline.
When the first letter of the expected answer is the uppercase of ĉ, ĝ, ĥ, ĵ or ŝ, and one uses the corresponding x-version, the answer is flagged as incorrect. For example, "Sxtrumpoj ne havas butonojn" is flagged as incorrect when the expected answer is "Ŝtrumpoj ne havas butonojn".
P.S. I know that this post is 5 years old, but I felt it was more appropriate to write here instead of opening a new post.