Last modified: 2014-07-11 18:08:29 UTC
Thinking about a contribution at Esperanto Wikibooks about facebook and facebook sample code I run into the following problem which affects every wiki with Esperanto language.
In order to store the source code for a page as
http://www.facebook.com/pages/Esperanta-bonveniga-giceto-pago/217219394947?v=app_62088208022 which is a general welcome facebook page listing many Esperanto topics one needs to preserve the Esperanto characters in the original form.
In Esperanto wikis the special Unicode Esperanto characters Ĉ Ĝ Ĥ Ĵ Ŝ Ŭ ĉ ĝ ĥ ĵ ŝ ŭ are changed to Cx Gx Hx Jx Sx Ux cx gx hx jx sx ux during editing. This is a very usefull feature. The problem is that it can *not* be deactivated.
In order to offer this function in a more general way at every installation I suggest the following.
a) Esperanto magical conversion should become a part of special:preferences. This would allow to use it at every installation including multilingual platforms as meta:, commons:, foundation wiki etc. without the need of gadgests as
[[commons:MediaWiki:Gadget-EoMagicalConversion.js]]. By default they should be enabeled if the language is Esperanto and disabeled otherwise.
b) For the main textareas as editing, writing emails, viewing sourcecode etc. a checkbox should be available to activate or deactivate it. The implementation might require two parameters in special:Preferences but this is a minor detail.
Please feel free to contact me for any questions.
Best regards [[user:gangleri]]
FYI: The code for the facebook page is available today at http://commons.wikimedia.org/w/index.php?curid=8688034 please edit the page copy the text and insert it at a project in Esperanto. make a preview, You will see that Esperanto characters are not preserved inside the text area box.
note: There are two kind of Esperanto magical conversion:
1) the tradidional one : changing Ch Gh Hh Jh Sh Uh ch gh hh jh sh uh to Ĉ Ĝ Ĥ Ĵ Ŝ Ŭ ĉ ĝ ĥ ĵ ŝ ŭ
2) the method used in MediaWiki so far : changing Cx Gx Hx Jx Sx Ux cx gx hx jx sx ux to Ĉ Ĝ Ĥ Ĵ Ŝ Ŭ ĉ ĝ ĥ ĵ ŝ ŭ
*nod* Probably the best thing would be to have a more modern system which can be used as a common basis for the EO conversion and for other languages which are making use of typing conversion systems -- there are several in use in the wild, especially for Indic scripts which have poor native OS support.
Doing it more on the client side would allow for finer control for the user (enable/disable in any text field) and probably would solve some of the difficulties where server-side form code forgets to properly convert outgoing or incoming text.
Our original implementation with server-side conversion was designed in the era where Netscape 4 was still in common usage; even with IE 6 as a minimum baseline we can do much better today.
(In reply to comment #2)
Thanks Brion! I agree that as many typing conversions should benefit. The general approach is not that simple if one want to cover all situations:
a) anonymous contributors with no preferences at all (maybe some information could be stored in session information)
b) registered users using various computers in different places
c) users with own equipment being able to use browser additions
Regards Reinhardt [[user:gangleri]]
There already is a js version, could be easily extended to feature on/of buttons etc.: MediaWiki:Gadget-EoMagicalConversion.js
I've implemented input method rules for Esperanto in the Narayam input method extension in r85504.
The client-side input method handles *all* text input fields, and doesn't rely on server-side processing remembering what type of field it's dealing with. Yay!
See also bug 3615.
Almost removed LanguageEo.php and replaced with a reference to Narayam, but the input method doesn't seem to be taking effect in some fields.
The search box, edit summary, etc are failing to engage the input method as of trunk r86742. Adding bug 28668 as a blocker for this bug.
Blocker bug was fixed while ago. Anything else prevent this from fixing?
Hi! I was absent since 2009. Anything new on this?
An additional questions: If a new solution is available what other sites could benefit from Mediawiki development using the required modules (witch ones). I rise this question because LibraryThing has an Esperanto since last week.
see discussion at: http://www.librarything.com/topic/134989